WordPress to 1С-Битрикс Migration: Full-Service Data Transfer

We are certified 1С-Битрикс partners. With 10+ years of experience, we have transferred over 500 projects: from blogs to e-commerce stores with millions of products. Moving from WordPress to 1С-Битрикс is not a file conversion but a full development of a new site with data migration. In one project, we moved a WooCommerce store with 50,000 products to Bitrix in 8 weeks — traffic dropped by only 3% and fully recovered in 2 weeks. The content storage structure, templating logic, and plugin architecture of WordPress fundamentally differ from the component model of Bitrix. For example, WordPress stores everything in wp_posts and wp_postmeta tables, while Bitrix uses infoblocks and high-load blocks. This must be understood from the first meeting — otherwise the project drags on for months. Without proper audit, you can lose up to 70% of traffic after a CMS change.

Before migration, we compile a complete data map: audit of Custom Post Types, key plugins (WooCommerce, ACF, Yoast SEO, WPML), media library size, number of users. Each element requires a separate transfer strategy. For instance, ACF fields are mapped to infoblock properties, and WooCommerce orders are transferred via API with order composition re-creation. We guarantee that your site will maintain search positions and run faster — Bitrix infoblocks process queries 2-3 times faster than arbitrary WordPress queries on catalogs with over 10,000 products. 1С-Битрикс Documentation: dev.1c-bitrix.ru

How is a WordPress site analyzed before migration?

WordPress stores all content in two key tables: wp_posts and wp_postmeta. Taxonomies via wp_terms, wp_term_taxonomy, wp_term_relationships. We check:

• Custom Post Types and their meta-fields (ACF, PODS)
• Plugins responsible for key functionality: WooCommerce, Yoast SEO, WPML
• Media library volume (wp_attachment) — number of files and their size
• Users, their roles, and access rights

For each item, a transfer script is developed in PHP 8.1+ using the 1С-Битрикс ORM.

Content migration: posts and pages

Articles and pages from wp_posts are moved into a Bitrix infoblock. An infoblock of type "Articles" is created, and each WordPress post is added as an element via CIBlockElement::Add().

Fields are mapped as follows:

ACF fields are transferred to infoblock properties. The ACF field type determines the Bitrix property type: text → S, number → N, image → F, post relation → G (link to element).

How to migrate a WooCommerce store?

If WooCommerce was running on WordPress, that's a separate layer of work. WooCommerce tables (wc_orders, wc_order_items, wc_product_meta_lookup) are moved to the Bitrix "Online Store" module. Products from WooCommerce are transferred to the Bitrix catalog:

• Simple products → catalog infoblock elements
• Variable products → trade offers (SKU) via catalog.sku
• Product categories → infoblock sections

WooCommerce orders are migrated via CSaleOrder::Add() with order composition re-creation via CSaleBasket. If order history is not critical, we migrate only products and the customer base. With proper configuration, catalog indexing on Bitrix is 2–3 times faster than WooCommerce on large volumes. Time savings on migration reach up to 40% when using automated scripts.

Multilingual (WPML → Bitrix)

WPML stores translations in tables icl_translations and icl_string_translations. In Bitrix, multilingualism is implemented via site language mechanisms: for each language, a separate language version of the infoblock element is created (through multisite settings). The structure is fundamentally different — transfer requires a separate script that accounts for language pairs.

What to do with SEO during migration?

This is a critical phase. Yoast SEO stores meta-data in wp_postmeta with keys _yoast_wpseo_title, _yoast_wpseo_metadesc. In Bitrix, meta-data is stored in infoblock properties or via the bitrix:seo.tags component. Mandatory steps:

1. Export all URLs of the existing site (via Yoast sitemap or Screaming Frog)
2. Map them to the new URLs in Bitrix (they may change structure)
3. Set up 301 redirects in .htaccess or through the Bitrix redirect module
4. Transfer title, description, og-tags for each page

Without this, a CMS change leads to a 30–70% drop in traffic in the first months. Experience shows that with proper setup, the drop does not exceed 5%. In one project, we managed to preserve 95% of positions after migration.

Media Library

WordPress stores uploaded files in /wp-content/uploads/YYYY/MM/. Bitrix stores files in /upload/iblock/. Files are physically transferred, but links in content are updated: either via SQL replacement in the database or via a script that iterates through all text fields of the infoblock. WordPress generates multiple sizes for each image (thumbnails). Bitrix also resizes images, but in a different cache system. Originals are needed in full size.

What is included in the work

We provide as a result of migration:

• Documentation on data transfer (mapping schemes, scripts)
• Full access to the new site (admin panel, FTP, database)
• Editor training for Bitrix (up to 4 hours)
• Technical support for one month after the switch
• Guarantee of search position recovery if our recommendations are followed

Migration timeline

The new Bitrix site is developed in parallel; the old WordPress remains active until the switch. The cost is calculated individually based on an audit. Order a turnkey migration — we handle all stages from analysis to switchover. Contact us for a project estimate — we'll offer timelines and budget individually.

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.