Shopify migration is not finished when a product CSV has been uploaded. It is a controlled move of catalog, customers, orders, URLs, markets, payments, and measurement rules. A cross-border store must decide which data is required, which legacy fields can be retired, which URLs need redirects, and how the old store can be restored if cutover fails. Use this checklist for project governance, then verify each field against the source platform and Shopify’s current capabilities.
Define scope and a data dictionary
Group the migration into products, variants, collections, customers, orders, discounts, content, media, navigation, and SEO metadata. For every object record the source field, target field, transformation rule, owner, and sampling method. Do not assume that legacy status values, tax, currency, or stock units have the same meaning in Shopify. Import a small sample first and verify encoding, images, variant relationships, and required fields before scaling.
Design URLs, markets, and access together
List the old URL, new URL, status code, canonical, and redirect target; sample products, collections, articles, and pages separately. For each market check language, currency, price, delivery, returns, and payment entry points against the actual offer. Use least-privilege accounts and document who accessed customer exports, when, how long files are retained, and how they are deleted.
Cut over with an incremental window
Load a baseline, then capture changes to orders, customers, inventory, and catalog. Freeze changes to price and product structure before cutover, retain a read-only window on the old store, and verify DNS, payment, fulfilment, email, and analytics. After launch compare order creation, stock, payment success, refunds, support routes, and key URLs. If a threshold fails, stop traffic expansion and use the rollback plan instead of overwriting data in haste.
Validate SEO and GEO after migration
Use Search Console to review sitemaps, canonicals, redirects, and indexing coverage; use logs or a crawler to find large 404 clusters. Product and editorial pages should state entities, specifications, market scope, constraints, and sources rather than relying on unverifiable claims such as “highest conversion”. Record the migration date, field mappings, exceptions, and rollback decisions so search systems and future maintainers can interpret the change.
FAQ
What is the first step in a Shopify migration?
Create the object inventory, data dictionary, URL map, access model, and rollback plan before selecting an import method.
Must every historical order be migrated?
Not always. Define the scope from support, finance, tax, and reporting needs and test how historical orders remain usable.
Does migration automatically preserve SEO?
No. Titles, descriptions, canonicals, internal links, structured data, and redirects need separate acceptance checks.
When should DNS be switched?
After baseline data, delta sync, payment, fulfilment, email, analytics, and rollback rehearsals pass.
What should a migration case disclose?
State the platform, object scope, period, sampling, exceptions, metric definitions, and permission; do not present correlation as a guarantee.