Shopify Migration Checklist: Complete 12-Step Pre-Launch Playbook

Key Insights
• A migration checklist only works if it is platform-agnostic and sequenced. Skipping the order costs more than skipping a step.
• Data mapping and redirects are where most migrations fail, not the parts merchants worry about most.
• Testing on staging before launch catches most launch-day failures before customers do.
• Post-launch monitoring is part of the checklist, not an afterthought once the store goes live.

A Shopify migration checklist exists because migrations do not fail at the big, obvious step. They fail at the step nobody wrote down: a redirect that was never mapped, a customer record that did not carry over a password, an app that silently stopped syncing on launch day. This playbook lays out twelve steps in the order they actually need to happen, from the first audit to the weeks after go-live, so the store that launches is the store you planned, not the store you improvised.

None of the twelve steps below are optional, but they are not all equally risky either. Data mapping and redirects cause the most launch-day damage when skipped, because their failures are invisible until a customer or a search engine hits them directly. Keep that in mind as a priority filter if a deadline forces you to compress the timeline: compress testing time before you compress mapping time, and never compress the redirect step at all.

Twelve steps sounds like a lot until you see what each one replaces: hours of guesswork, a support inbox full of the same three complaints, and a launch day spent finding out what broke instead of confirming what worked. Use this as a working checklist, not a reading list. Each step below is something you check off, not something you skim.

What Should Be on a Shopify Migration Checklist?

A migration checklist needs to cover four categories, in this order: what you are moving (data), where people will land (redirects and URLs), what still needs to work (apps and connected tools), and what you confirm before anyone sees it (testing). Skip a category and the store might still launch. It will not launch clean. A checklist organized by category, rather than as one long undifferentiated list, also makes it easier to hand off pieces of the work to different people without losing track of what depends on what.

The 12-Step Pre-Launch Playbook

Step 1: Audit Your Current Store

Before anything moves, know what you are moving. Catalog size, product variants, active apps, payment gateways, subscription products, and current URL structure all factor into scope and timeline. A store with 200 simple products migrates differently than one with 5,000 SKUs and a subscription model. This audit is what turns a vague migration into a scoped project with a real timeline. Write the findings down as a document, not a mental note; the next eleven steps all reference back to it.

Step 2: Choose Your Migration Method

Manual CSV export and import works for small, simple catalogs. Automated migration apps handle medium-sized stores with standard data. API-driven transfer suits large or complex catalogs but needs developer involvement. Agency-led migration covers full-store moves with redirects, subscriptions, and third-party connections included. Match the method to the catalog, not the other way around; choosing a manual export for a 4,000-SKU catalog usually costs more time than it saves in fees.

Step 3: Set Up Your Shopify Environment

Build in a development store or password-protected environment, never on your live domain. Configure your theme, install core apps, and set your Shopify plan before any data moves. A clean environment prevents the migration from inheriting configuration mistakes you will need to unwind later.

Step 4: Map Your Data Fields

Products, variants, customers, and orders rarely map one-to-one between platforms. A field that holds one value in your current system might need to split across two Shopify fields, or the reverse. Map this before import, not during it. Fixing a mapping error after thousands of products have imported costs far more than catching it in a spreadsheet first, and a second full import run risks creating duplicate records you then have to clean up manually.

Step 5: Migrate Product and Catalog Data

Move products, variants, images, and collections according to the mapping from Step 4. Spot-check a sample across your catalog’s range, not just the first ten products, before considering this step complete. For a closer look at the data side of this process specifically, see Shopify data migration.

Step 6: Migrate Customer and Order History

Customer accounts typically will not carry over passwords due to encryption differences between platforms; plan a password-reset email for launch day. Order history should migrate as historical records, not active orders, so your fulfillment workflow starts clean on the new platform.

Step 7: Build Your Redirect Map

Every old URL that has ever ranked, been linked to, or been bookmarked needs a 301 redirect to its Shopify equivalent. This is the single highest-leverage step for protecting search rankings and preventing broken links from ads, backlinks, and bookmarks. Pull the list from your analytics and your XML sitemap, not from memory; the pages merchants forget are usually the ones with the most inbound links.

Step 8: Preserve SEO Metadata

Title tags, meta descriptions, alt text, and structured data should transfer with the content they describe, not get rebuilt from scratch. Losing metadata during migration is one of the most common causes of a post-launch ranking dip that had nothing to do with the platform switch itself.

Step 9: Reconnect Apps and Connected Tools

Payment gateways, email marketing, CRM, subscription tools, and multi-channel listings all need to be reconnected and tested individually on the new platform. A connected app that worked on your old platform does not migrate with the data; it has to be rebuilt, and its configuration settings, tax rules, shipping rules, and discount logic rarely transfer along with it.

Step 10: Test Everything on Staging

Run test orders across desktop and mobile, confirm checkout and payment processing, and check every redirect built in Step 7. This is the step most likely to get compressed under a deadline, and the one most likely to catch a launch-day failure before a customer does. Have someone outside the project run the tests; the person who built the store already knows how to avoid its rough edges.

Step 11: Set a Launch Window and Go Live

Choose a low-traffic window, notify your team, and have a rollback plan even if you do not expect to need it. Launch is a single event; the migration is not finished when it happens.

Step 12: Monitor the First Weeks

Watch analytics, crawl errors, redirect performance, and customer support tickets daily for the first two weeks, then weekly through the first month. Migration issues do not always surface on day one. They surface when search engines re-crawl and when customers hit an edge case your testing missed.

Mistakes That Blow Up a Migration

• Skipping the audit and guessing at scope, which blows the timeline before migration even starts and leaves no real baseline to measure the finished migration against.
• Building redirects after launch instead of before, leaving a gap where every visitor and every crawler hits a broken page.
• Migrating on the live production domain instead of a staging environment, which risks customer-facing errors during the build itself.
• Treating app reconnection as a five-minute task instead of a full connection test, which is exactly how a broken payment gateway gets discovered by a customer instead of a tester.
• Launching without a documented rollback plan, so a serious issue on launch day becomes a live crisis instead of a contained one.
• Assuming a small catalog automatically means a small migration project, when a handful of complex subscription products can take longer to move than a thousand simple ones correctly.

SEO risk deserves its own closer look beyond this checklist. For what specifically protects rankings during a platform switch, see Shopify SEO migration.

How Long Does a Shopify Migration Take?

Timeline depends on catalog size and method more than platform. A small store with a few hundred products and standard needs typically completes in two to four weeks, including testing. A large or complex catalog with subscriptions, several connected apps, or a full custom rebuild can run eight to twelve weeks. If you are migrating specifically from WooCommerce, our dedicated WooCommerce to Shopify migration checklist covers platform-specific data quirks this general playbook does not. The steps above do not compress at the same rate the calendar does. Steps skipped to hit a deadline are the ones that resurface as post-launch fires.

Ready to migrate without guessing at the order? Our Shopify migration services run this exact checklist against your store, scoped to your catalog and connected apps, from audit to post-launch monitoring. Talk to our team about your migration.

Pro Tip 💡

 Run your migration checklist twice: once as a plan before you start, and once as a live audit the week after launch. The pre-migration version tells you what to do. The post-launch version tells you what actually happened, and the two rarely match exactly.

Frequently Asked Questions

What Should Be on a Shopify Migration Checklist?

A complete Shopify migration checklist covers four categories: data (products, customers, orders), URLs (redirects and SEO metadata), functionality (apps and connected tools), and verification (staging tests and post-launch monitoring). Missing any one category is what turns a routine migration into a launch-day scramble.

How Long Does a Shopify Migration Take?

Small, simple stores typically migrate in two to four weeks. Larger or more complex stores, especially those with subscriptions or several connected apps, can take eight to twelve weeks. Method and catalog size affect timeline more than the platform itself, so a realistic estimate should come from the audit in Step 1, not from a generic industry number.

Will I Lose My SEO Rankings During Migration?

Not from the migration itself. Ranking loss during migration almost always traces back to missing redirects, dropped metadata, or removed content, not to switching platforms. A documented redirect map and metadata preservation plan address most of the risk, and some fluctuation in the weeks after launch is normal while search engines recrawl the new site.

Can I Migrate to Shopify Without a Developer?

Small, simple catalogs can migrate using Shopify’s native import tools or a migration app without developer involvement. Larger catalogs, custom fields, subscription products, or complex redirect maps typically need developer or agency support to avoid data errors that are expensive to fix after the fact.

What Data Should I Prioritize Migrating First?

Products and their variants should move first, since every other system- orders, customer accounts, apps- depends on the catalog being accurate. Customer and order history follow, then redirects and metadata get built against the finished catalog structure. Trying to build redirects against an unfinished catalog usually means redoing that work later.

How Do I Know My Migration Checklist Is Complete?

A checklist is complete when every redirect has been tested, every connected app has processed a real test transaction, and someone outside the project has placed a live order without hitting an error. Completing every step on paper is not the same as confirming the store works end to end.