Shopify migration checklist: preserve products and URLs

Plan a Shopify migration around product mapping, customer identity, orders, redirects, operational cut-over and reconciliation after launch.

Dark catalogue structures, a shopping bag and parcels on a fulfilment track.

A Shopify migration moves more than a catalogue. Product identifiers, URLs, customer expectations, fulfilment processes and reporting all depend on the existing store. Begin with an inventory of what must move, what remains in an archive and what can be retired. Define a successful cut-over in business terms: customers can buy the correct products, operators can fulfil orders and important old URLs reach appropriate destinations.

Map data before importing it

Export representative products with variants, options, images, inventory locations and tax-related configuration. Agree how source fields map to the destination and identify unsupported or ambiguous values. Keep stable mapping records between old and new identifiers. Separate customer profiles from authentication: do not promise that existing passwords or every historical object can be transferred unchanged. Verify current platform and migration-tool capabilities for the exact source system.

Build a URL migration register

Collect important URLs from the old site, analytics, sitemaps and known backlinks where available. Map each useful page to its closest relevant destination. Avoid sending every removed product to the homepage. Test redirect behaviour, canonical tags, internal links and language alternatives. Make sure the new sitemap contains the intended final URLs. Keep the old mapping available after launch so support and engineering can investigate missing destinations.

Rehearse the operational cut-over

Import a sample and validate variants, images, prices, inventory and collection membership with the merchandising team.
Place test orders covering relevant payment, shipping, tax and fulfilment scenarios.
Define the final synchronisation window and how orders arriving during the transition are handled.
Reconcile record counts and selected values, and document exceptions that require manual correction.

Watch business outcomes after launch

Keep responsibility clear for failed orders, missing redirects, inventory discrepancies and customer account questions. Compare the new store with the signed-off migration sample rather than relying only on a successful import message. Preserve a recoverable source export with appropriate access and retention. A rollback may be complicated once new orders exist, so identify the point where forward correction is safer than switching back. Finish by closing the exception register and transferring the ongoing operating instructions to the people who manage the shop.

Frequently asked questions

Can every historical order be moved?

Do not assume so. Check the current platform, tool and source-system capabilities, then agree what will be imported or archived.

Will customers keep their passwords?

Password migration is platform-dependent. Validate the supported account transition and communicate any required reset.

Should all old URLs redirect?

Map valuable pages to relevant replacements; handle genuinely removed content deliberately rather than redirecting everything to one page.

When should inventory be synchronised?

Agree a final cut-over procedure and treatment of changes during the migration window.

How do we know the import succeeded?

Reconcile counts, relationships and business-critical values, then test purchasing and fulfilment with representative records.

Bring the scope. We will help make it buildable.

Share the user journey, integrations and launch constraints. We can clarify the scope and prepare an estimate with assumptions and exclusions.

Explore the delivery scope →