When migrating an ecommerce platform, preserve products and variants, customer–order relationships, open transactions and important URLs. A successful upload is insufficient; verify account access, orders and redirects through realistic scenarios.
Inventory data according to its role
Inventory products, variants, customers, historical and open orders, images and URLs separately. Verify that the migration method supports each group; a product CSV is not a full-store backup.
WooCommerce's official product-transfer documentation describes its built-in CSV tool for product data. Do not assume a tool with that scope also covers the entire store history. Verify the data types and custom fields supported by the chosen method.
Preserve relationships as well as fields
Map SKUs and internal identifiers, then test variant-to-parent and order-to-customer relationships. Matching record totals do not prove those relationships survived correctly.
Imagine products importing successfully while colour options attach to the wrong parent. The total product count could look correct even though buyers can order an incorrect combination. This hypothetical error explains why counts need to be supplemented with relationship and customer-journey tests.
Give each data group its own acceptance criteria
Import a small sample containing exceptions: a variant, discount, cancellation and multiple addresses. Give every data group a customer-facing acceptance test beyond counting rows.
| Data group | Relationship to preserve | Acceptance check |
|---|---|---|
| Products and variants | Codes, options, prices and images | Can the correct variant be purchased? |
| Categories and content | Product grouping and explanations | Do navigation and filters remain logical? |
| Customers | Identity, access and history | Does the correct person see the correct records? |
| Orders | Lines, totals and statuses | Can operations continue open work? |
| Existing URLs | Relevant new destinations | Does an old link reach the right content? |
| Integrations | Source and destination identifiers | Do stock, orders and cancellations flow correctly? |
Plan customer access and transition communication separately
Verify password and account-access portability on the target platform. Decide where open orders finish, when the final data difference is imported and what customers will be told.
Decide where open orders will be completed. If two systems show different statuses, support can provide contradictory information. Document the final data update, the source of new orders and the cancellation process at the point of transition.
Test representative exceptions before acceptance
Map old URLs to relevant replacements instead of sending everything to the homepage. Add permanent redirects, internal links, canonical, sitemap and a real order test to launch acceptance.
Assign post-launch issue ownership and establish access to older records. Sales, support and marketing should be able to follow the same underlying facts after migration. Opening the new design should not substitute for operational acceptance.