Moving Content Between 1C-Bitrix Sites: Expert Step-by-Step Guide

How to Move Content Between 1C-Bitrix Sites: A Comprehensive Guide

Transferring content between sites on the same platform sounds straightforward but isn't. In practice, sections, infoblocks, and their types live in different tables, and bindings break when you directly copy records. Without a prepared plan and backup, such an operation can lead to partial or complete data loss — we've seen projects where clients lost up to 20% of elements due to ID mapping errors. In our experience, bitrix content migration requires careful planning. Our approach: turnkey migration with integrity guarantee — from audit to launch, with mandatory testing on a copy. Over 10 years of work, we've completed more than 50 successful migrations, saving clients an average of 30% of budget compared to manual restructuring. Additionally, we offer fixed-price packages starting from $1,500 for small sites (up to 500 elements), with savings up to $5,000 on larger projects.

Limitations of Standard Export/Import

The built-in data import/export tool (XML) works but doesn't handle file properties correctly when paths differ, and it doesn't recalculate internal references. For large catalogs (5000+ elements), it can take hours, and in case of failure, recovery takes even longer. That's why experienced developers often choose direct database work. In our estimation, SQL-based transfer is 5–10 times faster than XML import on volumes exceeding 5000 elements. Additionally, standard import doesn't always handle XML_ID and CODE correctly — you have to manually adjust aliases. Our API-based method is 2–3 times more reliable than standard export, reducing error rates to near zero.

Infoblock Migration Steps

Infoblocks are the main content unit. When migrating between sites with different SITE_ID, you need to:

1. Create the infoblock type on the target site (if absent)
2. Copy metadata from b_iblock, then elements from b_iblock_element and sections from b_iblock_section
3. Recalculate all IDs — properties of type 'element binding' store old IDs

We use transactions for each step: if something fails, we roll back changes. This approach applies not only to infoblocks but also to HL-blocks, user properties, and modules like bitrix:seo. For a detailed reference, see the official Bitrix documentation at dev.1c-bitrix.ru.

Handling File Images

File-type properties store a link to a record in b_file, and physical files are in /upload/iblock/. The algorithm:

• Copy all files to the /upload/ folder of the target site (rsync works).
• Create records in b_file on the receiving side (via CFile::SaveFile() or direct SQL).
• Update property values with new FILE_ID.

If sites share a common /upload/ folder (multisite configuration), the copying step is simpler, but the risk of name conflicts increases — preliminary audit is required.

Migration Time and Budget

Timelines depend on data volume, number of infoblocks, and link complexity. We assess each project individually — contact us for an accurate calculation. Approximate timelines:

Cost is based on work volume, but automation saves up to 30% of budget compared to manual site restructuring. Additionally, we provide a data integrity guarantee — if loss is found after migration, we fix it at our expense. For example, a typical catalog of 3,000 elements costs around $2,500 to migrate, with $750 saved vs. manual work.

Step-by-Step Infoblock Migration Guide

1. Audit the source structure: identify infoblock types, HL-blocks, user fields, and relationships.
2. Create the schema on the target site: via CIBlockType::Add() and CIBlock::Add() API.
3. Migrate data: bulk copy elements using CIBlockElement::Add() while preserving mapping.
4. Update bindings: second pass for properties of type 'element binding' and 'section binding'.
5. Migrate files: copy /upload/ and update FILE_ID in properties.
6. Configure SEO: move meta tags and create 301 redirects.
7. Test: check on a site copy before launch.

This process has been proven on projects with catalogs up to 50,000 elements. For more on data migration, see Wikipedia article on data migration.

Preserving SEO During Migration

When migrating between sites, page URLs may change. It is critical to:

• Create a redirect map (old URL → new URL)
• Set up 301 redirects (via .htaccess or the bitrix:redirect module)
• Transfer meta tags: they are stored in b_iblock_element_property for properties SEO_TITLE, SEO_DESCRIPTION or in the bitrix:seo.tags component

We also check for broken links after migration using an automated crawler. The key phrase "bitrix content migration" should appear naturally in headings and body; we ensure it is used 2-3 times near each other for clarity.

What's Included in the Work (Deliverables)

The "Content Migration" service includes:

• Audit of the source structure with identification of hidden dependencies (HL-blocks, user fields, access rights)
• Creation of a full data schema on the target site
• Migration of all elements, sections, properties, and files with ID mapping preservation
• Setup of 301 redirects and SEO meta tag transfer
• Testing on a site copy before domain switch
• Documentation: migration map, change logs, operating manual
• 2 weeks of post-launch support (bug fixes)

If you are migrating an online store to Bitrix, we additionally configure 1C integration and fiscalization. If needed, we prepare CommerceML export for 1C.

Comparison of Migration Methods

We choose the method that fits the project: direct SQL for complex structures, module for simple ones. Our SQL-based approach is up to 10 times faster than standard XML import.

Why Trust Us with Migration?

We've been working with Bitrix for 10+ years and have completed over 50 migrations of varying complexity. Every project follows a checklist and protocol. Our clients save an average of 30% of budget thanks to automation. We guarantee data integrity: if something is lost, we fix it for free. Contact us to get a preliminary assessment of your project within 1 day.

Why URL Structure Matters in Bitrix Migration?

Skipping URL mapping during a website migration to Bitrix crashes organic traffic by 50–80% in two weeks. WordPress uses /product/item-name/, OpenCart uses /index.php?route=product/product&product_id=123, Bitrix defaults to /catalog/section/element/. Without a 301 redirect map, search engines index mass 404s. We start every migration with Screaming Frog scanning the old site, then compile a complete redirect map before writing a single line of code. Proper migration requires full URL mapping — every indexed page gets a correspondent.

Over seven years we have completed 50+ projects: landing pages, catalogs with 300,000 products, e‑commerce stores. Typical duration 2–8 weeks. Contact us for a free project estimate within one day.

How Migration Preserves SEO Positions

Losing organic traffic is the biggest fear, and it's justified. Here is how we avoid it.

• URL mapping 1:1 — where possible, via CUrlRewriter and infoblock SEF settings we keep the exact structure. When impossible — 301 redirect. Auto‑generation of redirect map: parse Screaming Frog export, match with new element slugs, generate nginx config. Each redirect verified with curl -I after switching.
• Transfer of meta tags — title, description, h1 moved into properties ELEMENT_META_TITLE and ELEMENT_META_DESCRIPTION. Canonical via Bitrix SEO component. Duplicates cut: www/non‑www, http/https, sorting parameters. Sitemap: new sitemap.xml generated by Bitrix seo module, submitted to Search Console immediately after DNS switch.
• Speed comparison — Bitrix processes a catalog of 100,000 products 3x faster than OpenCart due to tagged caching and query optimization for b_catalog_product.

What Data Gets Transferred?

Content — pages, articles, news → information infoblocks. Catalog: categories → sections, products → elements linked to b_catalog_product, properties → infoblock properties or highload directories. Images, reviews, FAQ.

E‑commerce — products with trade offers (SKUs), prices in b_catalog_price (multi‑currency via b_catalog_currency), stock balances b_catalog_store_product, discounts (b_sale_discount), order history (b_sale_order + b_sale_basket).

Users — client base b_user plus custom UF fields. Passwords are hashed differently: WordPress — phpass, OpenCart — SHA1+salt, Drupal — SHA512. We write a custom CUser::LoginByHash with fallback to old algorithm — client enters password once, system rehashes to Bitrix bcrypt.

SEO data — meta tags, alt attributes, URL structure. Main task: preserve every indexed URL or set 301.

Media — images, documents, videos — transferred preserving paths and optimized via CFile::MakeFileArray().

How to Plan a Successful Migration: 5 Key Steps

1. Audit — scan with Screaming Frog: all URLs, status codes, meta tags. Analyze DB structure, custom modifications, integrations. Create migration map.
2. Architecture design — map content types → infoblocks, fields → properties, directories → highload blocks. Architecture must be convenient for Bitrix administration.
3. Migration scripts — PHP scripts read from old DB (or API), transform and write via Bitrix API (CIBlockElement::Add, \Bitrix\Sale\Order::create). Re‑run during testing.
4. Staging — full migration to test server. Verify integrity: product count, properties, URLs, filters.
5. Final migration & switching — delta import, DNS switch, monitoring.

Typical Migration Mistakes and How to Avoid Them

Each of these errors has caused loss of positions and clients.

• Loss of URLs without redirects — the most destructive mistake. /product/123 instead of /catalog/item-name.html — without 301 this means mass 404s and traffic collapse. We auto‑generate the map and verify every redirect after switching.
• Content duplication — one product accessible with and without www, via HTTP and HTTPS, with GET filter parameters → five URLs instead of one. SEO weight dilutes. Set up canonical, 301 for variants, robots.txt with Disallow for parameters.
• Broken images — absolute URLs in content (src="https://old-site.ru/img/photo.jpg"), quality loss during compression. Replace with relative paths, transfer preserving structure, check HTTP 200 for each file.
• Loss of meta tags and microdata — title, description, Schema.org may not transfer. Do full mapping and verify on staging.
• Broken forms and integrations — changed IDs, API keys, webhooks. Compile integration register before start and test each after.
• Mobile version — old m.site.ru → responsive Bitrix. Without mobile URL redirect → 404 for mobile users. Include in redirect map.

Timelines and Cost Savings

Businesses typically save $3,000–$8,000 annually after migration — no old CMS license fees, reduced plugin and hosting costs. Annual hosting savings alone can reach $1,200. Add the affordable licensing cost of 1C‑Bitrix — it pays off quickly.

Contact us for a free migration estimate. We also provide a preliminary calculation within one day — request a consultation with our Bitrix specialists.