Shopify Migration Checklist: Data, SEO & Launch

A practical Shopify migration checklist covering data inventory, URL redirects, integrations, analytics, launch rehearsal, reconciliation, and downloadable templates.

A Shopify migration succeeds when customers can buy, the team can operate, and existing URLs still lead somewhere useful after the switch. Moving products is only one part of that job.

This checklist covers the decisions that should exist before launch: what moves, how it maps, what gets rebuilt, which URLs redirect, how totals are reconciled, and who makes the go-or-no-go call.

If you are still estimating the project, read the Shopify migration cost guide alongside this checklist.

Download the working templates

Use these as a starting point and add fields that matter to your operation:

The files contain example rows to show the expected structure. Replace those rows with your own systems and counts.

1. Define the migration boundary

Write down what “migration complete” means before choosing an importer, theme, or app stack.

Name the source store, target Shopify store, staging environment, and responsible owners.
List the countries, languages, currencies, customer types, and sales channels in scope.
Decide which historical data must remain usable in Shopify and what can be archived securely elsewhere.
Separate launch requirements from improvements that can happen after launch.
Record blackout periods, campaign dates, seasonal peaks, and contract deadlines.
Agree on measurable launch criteria and reasons to delay.

This step controls scope. “Migrate everything” is not a useful requirement until every category of “everything” has an owner and a destination.

2. Build the source inventory

Export counts before transforming data. You will use them later to prove that the final import is complete.

Commerce data

Products, variants, options, collections, categories, tags, and vendors
Prices, compare-at prices, costs, inventory, locations, and SKUs
Product media, files, alt text, and external video references
Metafields, custom attributes, bundles, gift cards, and subscriptions
Customers, addresses, consent status, tags, and account state
Orders, refunds, cancellations, discounts, taxes, and fulfillment history

Content and search data

Pages, blog posts, authors, categories, and publication dates
Page titles, meta descriptions, headings, canonicals, and structured content
Current URLs, query patterns, redirects, and high-value landing pages
Navigation, breadcrumbs, internal links, downloadable files, and forms
Image URLs, filenames, dimensions, and meaningful alt text

Operational dependencies

Payments, fraud rules, tax, shipping, returns, and fulfillment
ERP, PIM, WMS, POS, accounting, support, CRM, and email platforms
Reviews, loyalty, subscriptions, wishlists, search, and recommendations
Analytics, advertising pixels, consent, feeds, and affiliate tracking
Scheduled jobs, webhooks, manual exports, and spreadsheet workflows

The migration inventory template gives each item a source, destination, owner, method, validation rule, and risk level.

3. Map the target data model

Do not start the full import until representative products have been mapped into Shopify and reviewed by the people who maintain them.

Map every source field to a Shopify field, metafield, metaobject, app, or archive.
Define product-option and variant rules, including source combinations Shopify should not receive.
Decide how categories become collections and how collection rules will be maintained.
Normalize handles, SKUs, tags, vendors, measurement units, and enumerated values.
Record transformations such as HTML cleanup, date conversion, or attribute splitting.
Define how missing values and duplicates will be handled.
Test representative simple, complex, out-of-stock, discontinued, and international products.

The target model should make future merchandising easier. Recreating every source-platform workaround inside Shopify preserves the old problem.

4. Plan the storefront and content rebuild

A platform migration is also a publishing-system change. Confirm what the team can edit after launch, not only what customers can see.

Inventory every required template and reusable section.
Map source components to Shopify sections, blocks, and structured fields.
Preserve proven navigation and buying paths unless evidence supports a change.
Rebuild forms, validation, error states, search, filters, account paths, and empty states.
Test the theme with real long titles, missing images, many variants, sale pricing, and translated content.
Confirm responsive behavior, keyboard access, focus states, contrast, and motion preferences.
Document who owns each content area after handover.

Changing platform, information architecture, brand design, copy, and product model in one release multiplies the variables. Stage non-essential redesign work when the migration risk is already high.

5. Protect URLs and organic search

Create the redirect map from the source URL inventory—not from memory after launch.

Export all indexable URLs from the source CMS, sitemap, analytics, search-performance tools, and a site crawl.
Assign every valuable old URL a relevant target URL or an explicit removal decision.
Prefer one direct permanent redirect over chains.
Preserve useful page intent instead of redirecting every removed URL to the homepage.
Update internal links, navigation, canonicals, hreflang, structured data, and campaign destinations.
Preserve page titles, descriptions, headings, and on-page copy where they still serve the same intent.
Prepare a custom 404 page and a process for resolving unexpected misses.
Record source traffic and search baselines before launch.

Use the redirect map template to track the old URL, new URL, reason, priority, status, and verification result.

6. Replace integrations deliberately

For every plugin, app, script, and external platform, choose one outcome: keep, replace, rebuild, consolidate, or retire.

Document the business job, data direction, trigger, frequency, and owner.
Confirm the target integration handles the same important edge cases.
Identify duplicate ownership—for example, inventory being edited in both ERP and Shopify.
Test authentication, permissions, retries, error reporting, and rate-limit behavior.
Verify downstream emails, documents, fulfillment updates, refunds, and customer-service views.
Turn off obsolete source jobs only after the target flow is proven.

An integration list is not complete if it contains only app names. The team needs to know what each integration does when it works and how they notice when it fails.

7. Run test migrations and reconcile totals

One successful import is not a rehearsal. Run repeatable test passes and record their results.

Time the export, transformation, import, indexing, and verification steps.
Log rejected rows, warnings, duplicates, and manual corrections.
Compare source and target counts by status—not only grand totals.
Sample important fields and relationships, including media, variants, customers, and orders.
Test products with known edge cases.
Repeat the process after fixing mappings to confirm that it is reproducible.

At minimum, reconcile:

Record type	Compare by	Useful checks
Products	Active, draft, archived	Handles, titles, vendors, collections, media
Variants	Product and availability	SKU, options, price, inventory policy
Customers	Account and consent state	Email, addresses, tags, marketing consent
Orders	Date, financial, and fulfillment state	Totals, discounts, tax, refunds, customer link
Content	Type and publication state	URL, title, body, metadata, images
Redirects	Priority and response	Correct target, single hop, no redirect loop

Record the evidence in the reconciliation template.

8. Validate the complete buying and operating journey

Test as different customers and team roles, on real devices and supported browsers.

Browse, search, filter, view a product, add to cart, and complete checkout.
Test discounts, gift cards, taxes, shipping, payment failure, and order confirmation.
Test account creation, sign-in, password recovery, addresses, and order views.
Verify inventory updates, fulfillment, cancellation, refund, and return workflows.
Confirm emails, analytics events, advertising pixels, consent choices, and reporting.
Test customer support, warehouse, merchandising, and finance tasks with the people who perform them.
Check site speed and layout stability using representative pages and production-like third-party scripts.

A technically correct import can still fail the business if the warehouse cannot fulfill or the marketing team cannot publish.

9. Rehearse the cutover

The first time the team follows the launch sequence should not be launch day.

Define the content and data freeze, final delta, expected downtime, and communication plan.
Put every action in order with an owner, duration, dependency, and verification step.
Lower DNS time-to-live early enough if a DNS change is part of the launch.
Prepare redirect import, domain changes, certificates, email-domain checks, and third-party allowlists.
Define rollback conditions and the last safe point to use them.
Run the sequence in a test environment and update the timings.
Hold a go-or-no-go review with business and technical owners.

The launch-day runbook is a copyable starting point.

10. Monitor after launch

Migration work continues after the storefront is live.

Place and fulfill real low-value test orders using the agreed payment paths.
Monitor checkout, payments, errors, integrations, inventory, and customer-service contacts.
Crawl the live site for broken links, missing metadata, accidental noindex rules, and redirect problems.
Verify the sitemap and important URLs in search-performance tools.
Compare traffic, landing pages, crawl behavior, conversion, and revenue with the recorded baseline.
Review 404s and unexpected redirects daily during the launch window.
Keep a decision log and assign every issue an owner and severity.
Schedule a post-launch review after urgent defects have settled.

The minimum launch decision

Do not launch because the calendar says so. Launch when the named owners agree that:

Critical buying and operating journeys pass.
Required data is reconciled within documented tolerances.
High-value URLs have verified destinations.
Critical integrations are working and observable.
The team understands the cutover and rollback plan.
Known defects have owners and acceptable business impact.

If you need help turning this list into a project-specific plan, the Shopify Migration Readiness Review produces the inventory, dependency map, redirect risk review, sequence, and written scope before a full migration begins.

The Shopify Migration Checklist: Data, Redirects, SEO and Launch