Move products, customers, orders, content, redirects, analytics, and operations with evidence, owners, and rollback controls.
We reviewed the official sources linked on this page and translated them into operating controls that can be assigned, observed, and dated. We separate source-backed requirements from our planning interpretation, avoid claiming access to a reader's account, and turn changing provider or regulatory details into verification steps rather than fixed promises.
Use the guide with representative business data and keep an exception log. When a control fails, record the affected product or workflow, evidence, owner, correction, retest date, and remaining limitation. A guide is not complete because every box is checked; it is complete when another person can inspect the evidence and reproduce the decision.
Review failed and conditional controls at a named checkpoint before launch. Decide whether the issue blocks release, needs a compensating procedure, or can be accepted for a documented period. Record the approval owner, reason, expiration date, and monitoring signal. Reopen the decision when a provider changes its plan, an integration changes ownership, order volume crosses the modeled range, or the team can no longer reproduce the evidence.
Inventory systems and preserve source data
List the catalog, customers, consent records, orders, refunds, gift cards, content, media, domains, redirects, analytics, payment settings, tax and shipping rules, apps, automations, and financial records. Export source data before changing it and document the format, count, date, and owner. Shopify's official migration guidance recommends bringing products first, followed by customers and historical orders. Its export documentation also notes that product CSV files do not contain the image files themselves, so preserve source access while images are transferred.
Map URLs before rebuilding navigation
Create a one-to-one map for valuable old URLs, including products, collections, guides, policies, and campaign landing pages. Redirect an old page to the closest relevant new page, not automatically to the homepage. Google Search Central recommends preparing the destination, mapping old URLs to new URLs, configuring redirects, and monitoring the move. Update internal links, canonical URLs, sitemaps, structured data, and campaign destinations, then crawl both the redirect list and the new site.
Reconcile representative records
Test a sample that includes every difficult case: variants, archived products, sale prices, unavailable inventory, customer consent states, discounts, tax, shipping, partial refunds, and historical orders. Compare source count, destination count, skipped records, transformed fields, and known exceptions. Place new test orders and verify payments, inventory, notifications, fulfillment, refunds, analytics, and reporting. Do not delete the source system simply because the homepage is live.
Control launch and post-move monitoring
Lower DNS time to live in advance, schedule a content and configuration freeze, identify rollback triggers, and keep the prior store read-only. After switching, monitor server errors, missing pages, redirect loops, sitemap processing, index coverage, checkout errors, order totals, payment reconciliation, and customer support. Submit the new sitemap through Search Console and inspect priority URLs. Preserve logs and exports until business, finance, and search checks have passed for an agreed period.
Completion controls
- Source exports counted and stored
- Priority URL map reviewed
- Representative records reconciled
- Checkout and refund retested
- Rollback trigger documented
- Search and business monitoring assigned
Put the guide to work
Official sources
Sources support the operating controls described above. Provider requirements and public rules can change; verify the current source before acting.