Most migrations do not go wrong because of one big mistake. They go wrong because of a dozen small things nobody wrote down: a redirect that was missed, an integration nobody reconnected, a set of URLs that quietly 404 after launch.
A migration is a sequenced project. The brands that come through it cleanly are the ones working from a checklist instead of memory.
This Shopify migration checklist covers what to move and verify before, during, and after the migration, whatever ecommerce platform you are coming from.
Quick Answer
A Shopify migration checklist should cover six areas: data, content, URLs and SEO, integrations, storefront functionality, and launch. Before switching, inventory the data and content that need to move, map old URLs to their closest new equivalents, reconnect and test critical integrations, QA the new storefront, and run a monitored cutover. The goal is not simply to get the new Shopify store live. It is to preserve the data, search visibility, tracking, and operational systems the existing business depends on.
Before You Start: Scope and Prep
The work before the migration starts is what keeps the project on rails. Get these in place first:
- Inventory the current store: products, variants, customers, historical orders, content pages, and blog posts
- List every integration and app currently connected, including what each one does and who owns it
- Export or crawl the current URL structure before anything changes
- Record your current analytics and organic-search baseline so you can compare performance after launch
- Identify the data that must be preserved versus legacy data that can be archived
- Agree on scope, responsibilities, timeline, and launch criteria before development begins
Data to Migrate
Confirm which data needs to move and how each type will be validated:
- Products, variants, SKUs, images, prices, and inventory
- Collections and category logic
- Customer records and saved addresses
- Historical orders needed for support, returns, reporting, or customer history
- Blog posts, content pages, and associated media
- Tags, metafields, custom attributes, and operational data
- Gift cards, store credit, or other platform-specific records where applicable
Existing customer passwords cannot be imported. Shopify accounts are passwordless by default, so customers sign in with a one-time code rather than a saved password, and any legacy accounts you import will need customers to activate them on the new store. Plan the customer account activation and first-login experience before launch so returning customers are not locked out.
Historical orders also deserve their own migration plan rather than being treated like ordinary customer data. Shopify recommends importing products first, then customers, then historical orders, so that when order history is imported the underlying product and customer records already exist and can be associated correctly.
SEO and Redirects
This is where a technically successful platform move can become an organic-search problem. Before launch:
- Inventory every indexable, linked, or traffic-driving URL on the current store
- Map each old URL to the closest equivalent Shopify URL
- Create permanent 301 redirects where a relevant replacement exists
- Avoid redirect chains. Point each old URL directly to its final Shopify destination rather than through a series of intermediate redirects
- Allow genuinely retired content with no appropriate replacement to return a proper 404 rather than redirecting unrelated URLs to the homepage
- Preserve important title elements, headings, on-page copy, and useful meta descriptions
- Review canonical tags across products, collections, content pages, and other duplicate-prone templates
- Revalidate relevant structured data, particularly Product, Breadcrumb, Organization, and other applicable structured data
- If the store serves multiple countries or languages, preserve or reimplement hreflang annotations so the correct regional URLs are served after launch
- Preserve valuable image alt text and important media assets
- Update internal links so the new store points directly to the new URLs instead of routing users through redirects
- Check the new store for accidental noindex directives, crawl blocks, broken links, and orphaned pages
For the full process, see our guide to Shopify migration SEO.
Integrations and Functionality
A store is more than its catalog. Every system connected to the current store needs a migration decision.
- Reinstall and validate GA4, Google Tag Manager, Meta Pixel, Shopify pixels and customer events, and other measurement systems, and confirm the underlying purchase and behavior events actually fire
- Reconnect email and SMS platforms and test the automations that depend on ecommerce events
- Map each important app or plugin to a Shopify app, native Shopify capability, or custom implementation
- Reconnect reviews, subscriptions, loyalty, bundles, upsell, and customer-account functionality
- Reconnect ERP, 3PL, WMS, fulfillment, or inventory systems and test the complete order lifecycle
- Verify payment providers, taxes, shipping logic, discounts, and markets
- Confirm consent management and tracking behavior still work as intended
Do not assume an integration works because the app is installed. Test the actual events and workflows the business depends on.
Storefront and Design
A migration is also an opportunity to stop carrying old storefront problems onto the new platform. Before launch, verify:
- Product pages, collection pages, search, filters and sorting, navigation, cart, and account flows
- Mobile usability across the highest-traffic templates
- Page performance on representative products, collections, and content pages
- Merchandising rules and collection logic
- Trust signals, reviews, subscriptions, bundles, and other conversion-critical components
- Accessibility and browser behavior across the storefront
Pre-Launch QA
Nothing should go live until the new storefront has been tested while the existing store remains available.
- Spot-check migrated products, customers, orders, and content against the source data
- Test checkout from product page through successful order confirmation
- Place a test order end to end and verify it reaches the systems that depend on it: fulfillment or 3PL, ERP, inventory, email/SMS, and analytics
- Test discounts, payment methods, taxes, and shipping scenarios
- Test representative URLs from the redirect map
- Crawl the new storefront for broken internal links, canonical errors, crawl restrictions, and unexpected 404s
- Validate analytics and pixels with debug or test traffic without contaminating production reporting
- Run a launch-blocker checklist
- Freeze nonessential content changes before the final data sync and cutover
Launch and Post-Launch
The cutover is a watched event, not a fire-and-forget. On and after launch:
- Make the domain or DNS cutover on a planned schedule where required
- Confirm the production storefront, checkout, and account flows work
- Verify redirects in production
- Submit the new Shopify sitemap in Google Search Console
- Monitor Search Console for crawl and indexing problems
- Update important external links you control, including partner links, social profiles, ad destinations, and email footers, to point directly to the new Shopify URLs
- Track organic traffic and important rankings against the pre-migration baseline
- Watch analytics, purchase events, email/SMS events, ERP feeds, and fulfillment workflows
- Keep a backup or accessible copy of the old store's data until the migration has been fully validated
- Keep permanent redirects in place for as long as possible. Google recommends keeping migration redirects for at least a year, and keeping them indefinitely makes sense for important legacy URLs that still attract links or traffic
Some temporary search volatility can happen while search engines recrawl and process changed URLs. What matters is catching technical problems quickly and separating normal reprocessing from an actual migration error.
Common Shopify Migration Mistakes
Most failed migrations repeat the same avoidable errors. Watch for these:
- Launching before the redirect map is complete and tested
- Redirecting every old URL to the homepage instead of to its closest equivalent
- Forgetting blog posts, content pages, and other non-product URLs in the redirect plan
- Assuming an app or integration is configured correctly just because it is installed
- Losing analytics continuity and purchase events, so post-launch reporting cannot be compared to before
- Launching with leftover noindex directives or crawl blocks from the staging environment
- Changing URLs, content, design, and domain all at once, which makes it impossible to isolate what caused a ranking change
- Removing redirects too soon, before search engines have fully processed the move
- Not recording a pre-migration baseline, so there is nothing to measure recovery against
What Comes Next
This checklist is the operating structure behind a Shopify migration: preserve the data, protect the URL relationships, reconnect the systems, validate the storefront, and watch the launch. At Liquid Lemon, our Shopify migration services bring those pieces together with the storefront build as one scoped project. If budget is the next question, our guide to Shopify migration cost explains the variables that actually change the quote.
Coming from a specific platform? See our guides to Magento to Shopify Plus migration, BigCommerce to Shopify migration, WooCommerce to Shopify migration, and Volusion to Shopify migration. To see the storefronts we build, take a look at our work.
Send us your current store and we will turn this checklist into a scoped migration plan for your catalog, integrations, URLs, and storefront.
Start Your Sprint now with Liquid Lemon.
Written by Andrew Zam, Co-founder of Liquid Lemon, a Shopify / Shopify Plus design + development studio for DTC brands.
