A product CSV is not a complete plan for migrating a store. WooCommerce may show the correct names and prices, while the old Bitrix URLs stop working, variations become separate product pages, and menu links remain outdated. These parts need to be accepted separately.
Start with a table that links each real product to its stable identifier and public URLs in both systems. Neither changing the CMS nor importing the catalog guarantees that search rankings will be preserved. The team's task is to migrate the data and routes reproducibly, then monitor search results separately.
What to include in the plan before exporting
Define the scope: products, offers, categories, images, SEO fields, and public URLs. Orders, users, payments, and inventory integrations are separate parts of a migration; do not treat the built-in product importer as a migration of the entire store.
In Bitrix, record the IDs of the product and offer information blocks, the SKU properties in use, and the actual URL patterns. Do not treat XML_ID as a universal SKU: on a particular site, it may serve as an external exchange key. Agree with the developer on which key will preserve product matching during subsequent updates.
Save the original export and the list of available public URLs before changing routes. It is much harder to reconstruct the mappings from memory after the old catalog has been removed. For a product in multiple categories, record all paths that were actually used and the chosen primary URL.
Sample mapping table
Imagine a ventilation catalog being migrated from Bitrix to WooCommerce. This is a fictional example. The product with SKU FAN-10 has one primary old URL and an additional URL from another category. In the new system, it has been assigned one primary URL.
| Key | Old Bitrix URL | New WooCommerce URL | Action |
|---|---|---|---|
| FAN-10 | /catalog/fans/fan-10/ | /product/fan-10/ | Redirect to the product page |
| FAN-10 | /catalog/sale/fan-10/ | /product/fan-10/ | Redirect to the same product page |
| Category fans | /catalog/fans/ | /product-category/fans/ | Redirect to the category |
| Deleted OLD-2 | /catalog/fans/old-2/ | Not selected | Decision required |
The WooCommerce paths here are illustrative: check the active permalink structure on your store. Do not approve a table where the new URL is only assumed. Open it after the test import and confirm that it displays the intended product.
Do not automatically redirect OLD-2 to the homepage. First decide whether there is a suitable replacement or whether the page is actually being removed. An unknown destination must remain an explicit open question until launch, not become an unnoticed rule that redirects everything to the catalog.
How to transform data for WooCommerce
The two CMSs have different schemas. The developer should transform the source fields into columns supported by the importer in use, rather than simply renaming the export file to CSV. The capabilities of the built-in tool and the scope of product migration are described in the WooCommerce migration guide.
Agree on the mapping for name, SKU, description, category, price, stock, and image. For a variable product, transform Bitrix offers into WooCommerce parents and variations separately. An offer name and a similar product name do not establish this relationship. It is covered in more detail in the CSV instructions for variations.
SEO fields from the installed plugin need to be mapped separately. Do not assume that a regular Description column will migrate the meta description: these are different data. Confirm which field stores the required text in the target system and how the importer supports it.
Check images before the bulk upload: whether the files are accessible at their source URLs, which image will become the primary image, and which will be included in the gallery. Include captions and alt text in the data table as well. Do not treat the appearance of a thumbnail as confirmation that all media has been migrated.
How to run a test import
Select a small set of different items: a simple product, a product with multiple offers, a product in two categories, and an item with a nonstandard SKU. Prepare a copy of the target store and import only this sample. After importing, compare the data in the editor and on the storefront.
For each product, confirm the stable SKU, categories, description, price, stock, images, and public URL. For variations, check the attribute selection and corresponding price. Record issues by field: “Size M is missing from the parent” is more useful than “The import is not working properly.”
Then test updating the same sample again. It should update existing products using the agreed keys. If new product pages appear, the migration is not ready for regular synchronization. The process for this check is described in the article on updating WooCommerce by SKU.
How to migrate old URLs
After confirming the new URLs, the developer creates redirects based on the table. The new CMS does not know on its own which product matched an old Bitrix path. A general pattern is appropriate only where the mapping is genuinely unambiguous; all other URLs need specific mappings.
Yandex's recommendations for changing site structure recommend checking that new pages are accessible, updating the sitemap, and confirming that the HTML does not prevent the required indexing. These are separate actions to take after configuring redirects, not an automatic result of importing the catalog.
Check an old product URL, a category URL, and an additional product path. Record the initial response code and the final URL. The destination page must have the correct product, the primary canonical, and a consistent robots rule. A chain of several redirects requires a separate review: it may conceal rules left over from the old site.
What to check during launch
Set the time of the final export and the rules for catalog changes before the switch. If managers continue changing prices in Bitrix, a test import from a week ago is not an up-to-date WooCommerce baseline. The team must agree which changes to import again and how to confirm completeness.
After switching the domain, check the new URLs on the real public host. Make sure there is no leftover test noindex, no links to the copy's URL, and no canonical pointing to the development domain. Data from a local build does not replace the published response.
Review the menu, breadcrumbs, store search, recommendations, and sitemap. They should point to the new primary URLs. Redirects preserve old external links, but internal navigation should be updated. Also check the product page on a phone: variation selection and navigation must remain available.
How to accept the migration and document limitations
Attach the source exports, field transformation rules, URL table, and test products to the task. Assign an owner for the import and an owner for the routes. Specify concrete results for the data, variation selection, repeat updates, and old links in the acceptance criteria.
For the sample, the work is complete when both old FAN-10 links lead to the new product page, the category leads to the corresponding category, and the fate of OLD-2 has been agreed and checked. Record unverified parts of the catalog separately, with their scope and reason, rather than declaring the entire migration verified based on four rows.
Published pages can also be checked with a technical site audit. Monitor search impressions and indexing after launch, taking crawl dates into account. The migration report should confirm completed actions and working URLs; a promise that rankings in Google or Yandex will remain unchanged does not replace any of these checks.