The Complete Ecommerce Migration Checklist (2026): Platform, Apps, SEO, Data

Ecommerce migrations fail in predictable ways. The most expensive failures are not platform bugs; they are the assets that quietly do not make the jump. Review content with verified-purchase status. Loyalty point balances. Subscription contracts mid-cycle. SEO equity tied to URLs that quietly 404 the day after launch. Customer accounts that exist in the old auth system but not the new one.

This checklist organizes a full ecommerce migration into the five buckets that determine whether the new store launches well or bleeds revenue for six months. It is platform-agnostic. The same buckets apply whether you are moving from Magento to Shopify, BigCommerce to Shopify Plus, WooCommerce to Shopify, or replatforming inside Shopify between themes or store generations.

The five buckets

Every migration has the same five buckets. Sequencing matters: data and SEO need lead time, apps and design can run in parallel, and post-launch verification cannot start until cutover is live.

1. Platform and theme: the visible build
2. Apps and integrations: the stack on top of the platform
3. Data migration: products, customers, orders, reviews, UGC, loyalty
4. SEO and redirects: URL structure, sitemap, schema, redirects
5. Post-launch verification: what to test once traffic is live

Plan all five before you write the first line of theme code. Migrations that start with theme work and discover the data and SEO buckets late are the ones that overrun.

Bucket 1: Platform and theme

Before the build:

• Document current platform's customizations: every checkout extension, every theme modification, every custom Liquid section, every script.
• Inventory the design system: components, color tokens, typography, spacing.
• List all checkout flows (guest, registered, subscription, B2B, multi-currency) and whether each carries forward.
• Decide on the new theme strategy: stock theme with customization, premium theme, or custom build. Custom builds need 4-8 extra weeks.
• Lock the design before development. Mid-build design changes are the largest schedule risk.

During the build:

• Build product pages, collection pages, cart, and checkout first. Everything else is secondary.
• Build mobile-first. 70%+ of ecommerce traffic is mobile.
• Implement core analytics events (page view, add to cart, checkout started, purchase) before launch, not after.
• Stand up a staging environment with a production-grade product catalog from week one.

Bucket 2: Apps and integrations

Apps are where migrations quietly break. Common failure modes: review apps that lose verified-purchase status during import; loyalty apps that lose point balances; subscription apps that lose mid-cycle contracts.

For each existing app, decide:

• Migrate the data and keep the app if the app supports the new platform
• Migrate the data to a different app if changing platforms means changing apps
• Drop the app if you can live without it on the new platform

Apps that always need migration planning:

• Reviews: Yotpo, Loox, Judge.me, Junip, Stamped all support CSV export including photos and metadata. Import to the new app before launch so verified-purchase mapping persists. Late imports often lose verification status. See our migration guides for app-specific paths.
• Loyalty: Smile, LoyaltyLion, Yotpo Loyalty: export point balances and tier status before migration. Most loyalty apps support direct migration between vendors.
• Subscriptions: Recharge, Skio, Bold Subscriptions: subscription contracts must migrate with billing cycle preserved. This is the single most error-prone migration. Plan 2-4 weeks of parallel run.
• Email and SMS: Klaviyo, Postscript, Attentive: subscriber lists, consent records, flow definitions all need to move. Consent records are legally sensitive; preserve opt-in timestamps.
• CRO and analytics: Hotjar, Microsoft Clarity, GA4: tracking IDs need to update on the new store. Set up before launch to avoid analytics gaps. Post-migration is also a good time to reassess your Shopify CRO tool stack, as migrations often reveal gaps in the existing setup.

Bucket 3: Data migration

Data migration is the bucket where errors are most expensive because they often are not visible until weeks after launch.

The data checklist:

• Products: including variants, metafields, custom fields, images at original resolution
• Collections: including smart collection rules, sort order, hand-curated selections
• Customers: including password hashes (if compatible), addresses, marketing consent, tags
• Order history: for customer-account display, returns processing, and analytics continuity
• Reviews and ratings: including photos, videos, verified-purchase status, response history
• UGC: Instagram feeds, customer photo galleries, video reviews
• Discount codes: active codes, expiration rules, usage limits
• Gift cards: outstanding balances must transfer exactly
• Inventory: current stock levels, location splits for multi-warehouse, low-stock thresholds
• Metafields: custom product data, often invisible until a section fails to render

Test data migration on a sandbox first. A full migration dry-run two weeks before launch catches 80% of issues that would otherwise hit production.

Bucket 4: SEO and redirects

This is the bucket that determines whether organic traffic survives the migration. Done well, traffic dips 5-15% for 2-6 weeks then recovers. Done poorly, traffic drops 40-60% and may take 6-12 months to rebuild.

The SEO checklist:

• URL mapping: every URL that earns traffic or has backlinks needs a 301 to its new equivalent
• Old sitemap audit: pull the current sitemap and Google Search Console performance data, prioritize redirects by traffic
• Meta tags: title tags, meta descriptions, OG tags must transfer
• Schema markup: Product, Review, AggregateRating, Breadcrumb, Organization all need to render correctly on the new store
• Internal links: collection-to-product, product-to-product, blog cross-links should rebuild
• Image alt text: preserve from the old store; don't lose alt text during product re-creation
• Hreflang: multi-region stores need hreflang tags rebuilt
• robots.txt and crawl directives: verify the new store is crawlable on launch day
• Page speed: Core Web Vitals on the new build should match or beat the old build

Submit the new sitemap to Google Search Console within 48 hours of launch. Monitor coverage reports daily for the first 2 weeks.

Bucket 5: Post-launch verification

Cutover is not the finish line. The first 14 days post-launch determine whether the migration succeeded.

Verify in this order:

• Day 0: checkout works on every payment method, every shipping method, every currency
• Day 1: organic traffic is stable in Google Search Console; no major coverage errors
• Day 3: returning customers can log in, see order history, redeem stored credit
• Day 7: review collection emails are firing; new reviews are saving correctly
• Day 14: subscription renewals are processing without errors; loyalty point accrual is working

Common post-launch issues:

• Email flows triggered on old events that no longer exist
• Mobile cart abandoning on a payment method that worked in staging
• Reviews not displaying because schema is malformed
• Search results returning wrong products because the search index hasn't fully rebuilt

The compounding asset most migrations lose

Reviews are the asset most migrations underweight. A store with 5,000 reviews migrating to a new platform without preserving verified-purchase status keeps the review count but loses 30-50% of the conversion lift, because verified reviews are weighted more heavily by Google and trusted more by shoppers.

Migrating reviews properly (preserving photos, video, response history, and verified-purchase mapping) is a 1-2 day project that protects the largest conversion asset most ecommerce stores have built. Skipping it to "import later" is the most common avoidable migration mistake.

If reviews are a major conversion driver for your store today, plan the review migration in week one of the project, not the last week before launch. The data migration is fast; the verification, schema validation, and display optimization on the new platform is what takes time, and what determines whether the conversion lift from your existing reviews compounds on the new store or has to be rebuilt from scratch.