E-commerce replatforming: migrate data, URLs and operations without treating launch as a file transfer

Map six migration workstreams before cutover

1. Inventory source data

   List products, variants, media, customers, orders, reviews, coupons, content, redirects and custom/extension data; mark retain, transform, archive or exclude.

2. Define field and identity mapping

   Map IDs/SKUs, product handles, variants, customer identifiers and order history so imports can be reconciled rather than trusted by row count alone.

3. Map URLs and search dependencies

   Preserve stable URLs where practical; otherwise create intentional old-to-new redirects and test important destinations before and after cutover.

4. Rebuild integrations and settings

   Payments, shipping, tax, email, analytics, inventory and fulfilment connections need environment-specific configuration and acceptance.

5. Plan delta and freeze behavior

   Decide how orders, customers and inventory created during the migration window are frozen, replayed or reconciled.

6. Accept the new store

   Test purchase, refund/cancel, fulfilment, email, inventory, admin roles, redirects, analytics and rollback/recovery evidence.

Migration sequence matters because records reference one another

WooCommerce migration documentation explicitly separates users/customers, products, reviews, coupons, orders and subscriptions and notes sequencing to preserve relationships. Shopify's migration guidance similarly treats data import as only one step before shipping, taxes, payments, test orders, domain and SEO/redirect work.

URLs are a launch dependency, not a cleanup task

Shopify notes that platform URL structures can differ and recommends creating redirects for old links; Google Search migration guidance likewise treats URL mapping and redirects as part of a controlled site move. The migration register should therefore include high-value product/category/content URLs before the domain or routing changes.