Most Shopify migration checklists you'll find online treat the cutover like the finish line. It isn't. The finish line is 30 days later, when your SEO has either held up or cratered, your customers have either logged back in or churned, and your support team has either survived the call spike or quit.

We work with 2,100+ Shopify stores on the phone-support layer. That means we watch what happens after the migration goes live, on the customer end. Spoiler: every store sees a 2-4x call-volume spike for the first two weeks. Password resets, "where's my account?", "are these the same products as before?". The migration didn't break. The aftermath did.

This checklist is the operator's version. 47 steps across four phases, with real costs, real timelines, and the post-launch reality nobody else writes about. According to a McKinsey study cited by ecommerce platform Brainvire, up to 20-30% of customer data is lost in poorly executed migrations. So we're going to be careful.

Hear what AI support calls sound like for your store. Just paste your Shopify URL and get sample calls in under 20 seconds, no email required. Listen to demo calls for my store.

What actually moves when you migrate to Shopify

Before the checklist, get clear on what transfers and what doesn't. Most migration disasters happen because someone assumed data would move that didn't.

Here's the honest breakdown:

Two of these will hurt the most. The variant cap (Shopify maxes out at 3 product options) catches Magento and WooCommerce stores with complex SKUs. And the password reset, which we'll talk about a lot, is the single biggest driver of post-launch support volume.

If you're migrating from a major platform, Shopify's own help center has good starting points (the WooCommerce migration guide is solid). For deeper SEO planning, our Shopify SEO guide covers the rankings-preservation side of the move.

Phase 1: Pre-migration planning (10 steps)

This phase is roughly 30% of the total project time. Skip it and you'll spend three times that fixing things later.

1. Define why you're migrating and pick success metrics. Are you moving for speed, app ecosystem, or admin simplicity? Pick three numbers you'll measure 90 days post-launch (organic traffic, conversion rate, support volume). You can't manage what you don't track.

2. Audit your current store. Build a spreadsheet of every product, every collection, every blog post, every page. Include URL, SKU count, image count, and SEO meta. This is your migration manifest.

3. Take an SEO baseline snapshot. Pull your top 100 keyword rankings, your monthly organic traffic, your top 50 landing pages by clicks. Screenshot it. You'll need this to measure damage (or wins) post-launch.

4. Build your URL map. Spreadsheet, two columns: old URL on left, new Shopify URL on right. Every product, every collection, every blog post, every landing page. This is non-negotiable. Skipping URL mapping is the single biggest cause of post-migration SEO collapse.

5. Inventory your apps and integrations. Every app on your current platform needs a Shopify equivalent or a manual workaround. Include the customer-support layer (help desk, phone, returns, reviews). Phone support is the layer that breaks first post-launch, so Ringly.io is worth pre-installing if you don't have AI phone coverage yet.

6. Back everything up. Full export from your current platform. Products, customers, orders, reviews, blog content, all of it. Twice. Store the second copy somewhere not connected to your current platform.

7. Pick a migration method. Four options:

• Manual CSV (free, slow, fine for under 500 SKUs)
• Shopify's Store Migration app (free, early access, supports major platforms)
• Third-party apps like Matrixify ($20-$200/mo), LitExtension ($200-$400+ per project), or Cart2Cart ($150-$350 per project)
• Agency-led ($2K-$50K+ depending on complexity)

8. Document custom features that won't migrate. Custom checkout logic, gift-card balances, loyalty points, subscription billing. Each one needs a rebuild plan or a workaround app. Flag everything now, not later.

9. Build a realistic project timeline. Simple stores (under 500 SKUs, no custom dev): 2-4 weeks. Medium (500-5K SKUs): 4-8 weeks. Shopify Plus with custom development: 8-16 weeks. Enterprise migrations from Salesforce or Magento with 50K+ SKUs: 3-4 months. According to data from Xgen Tech, most successful US migrations run on an 8-16 week timeline.

10. Pick your launch window. Avoid peak season (no BFCM migrations, ever). Tuesday-Thursday morning is the safest cutover slot. Notify your team, freeze marketing campaigns for 48 hours either side, and tell your fulfillment partners.

Phase 2: Migration execution (15 steps)

Sequence matters here. Get the order wrong and you'll be importing things twice.

Rule of order: products before collections, customers before orders, URLs before redirects. Stick to it.

11. Set up your Shopify store and pick a plan. Don't pick Plus unless you genuinely need it. The standard plans handle most stores up to $5M-$10M GMV. Plus makes sense at $1M+/mo or for B2B features.

12. Configure currencies, taxes, payment gateways, and shipping zones. Do this before you import a single product. Tax logic affects how products display pricing.

13. Clean your product data before import. Standardize SKUs, fix duplicate variants, compress images, write missing meta descriptions. Cleaning during import is harder than cleaning before. As ecommerce expert Ben Salomon puts it: "Migration is not just a platform switch; it is a data integrity project."

14. Import products. CSV via Shopify admin or app of choice. Verify random samples after import. If you've got more than 3 variant options per product (common with apparel and skincare), you'll need to flatten them. There's no workaround.

15. Build collections. Manual or via app. Shopify uses smart collections (auto-rules) and manual collections (hand-picked). Pick the right type per collection.

16. Import customer records. Email, name, phone, addresses. Remember: no passwords. You'll communicate this to customers in step 25.

17. Import order history. Shopify doesn't natively support order imports. Use Matrixify (best for bulk) or LitExtension. Order history matters for customer-support lookups: customers will call asking about pre-migration orders for months. If you skip this, see our guide on WISMO calls for what happens.

18. Rebuild your blog and content pages. Posts can be imported, but URLs change. Map every blog URL in your spreadsheet (step 4).

19. Install your replacement apps. This is where the customer-support stack matters. Help desk (Gorgias or Zendesk), reviews (Judge.me, Loox, or Yotpo), email/SMS (Klaviyo), and phone (Ringly for AI coverage). Installing the customer-service-for-Shopify stack before launch is cheaper than scrambling after.

20. Configure your domain and DNS. Point your custom domain to Shopify. Keep TTLs low (300 seconds) in the days leading up to launch so DNS changes propagate fast.

21. Implement 301 redirects from your URL map. Every old URL needs a 301 to a new URL. Use Shopify's bulk URL redirect tool, or apps like Easy Redirects for thousands of rules. Test 50 random ones manually before launch.

22. Set up SEO basics. Meta titles, meta descriptions, image alt text, structured data for products. The 80/20 here: meta on top 100 revenue pages, alt text on hero images.

23. Configure analytics. GA4, Google Tag Manager, Meta pixel, TikTok pixel, anything else. Cross-check that events fire correctly on test orders.

24. Set up email authentication (SPF, DKIM, DMARC). This is the step that nobody warns you about. Without proper email authentication, your password reset emails will land in spam. We've seen stores where 30%+ of reset emails never reached the customer because DKIM wasn't set. Test with mail-tester.com before launch.

25. Build your customer-communication email. Draft the email that goes out launch day. Tell customers about the migration, why their old password won't work, and how to reset. Send via Klaviyo with personalized magic links if you can. The agency Vervaunt has good guidance on customer reactivation, they recommend a 3-touch sequence (day 1, day 7, day 14) with incentive escalation.

Phase 3: Pre-launch testing (8 steps)

Before you point your domain at Shopify, run this protocol. Every store skips one of these. Don't be that store.

26. Test the full checkout flow with real cards. Three test purchases minimum: domestic, international, and on mobile. Verify tax, shipping, payment confirmation email, and order admin entry all work.

27. Verify 301 redirects. Crawl your old URLs with Screaming Frog or Ahrefs. Every URL should return 301 to 200 (one hop, no redirect chains). Fix any 404s before launch.

28. Test on mobile, desktop, and tablet. Run the full customer journey on iOS Safari, Android Chrome, Desktop Chrome, and Desktop Safari. Mobile is where checkout breaks most.

29. Verify analytics fires correctly. Make a test purchase. Check that the purchase event lands in GA4, Meta, and any other tracking. If it doesn't fire, you'll be flying blind for the first week post-launch.

30. Test password reset email deliverability. Send a password reset to a fresh Gmail, Outlook, and Yahoo address. If any land in spam, fix SPF/DKIM/DMARC before launching. This single test prevents half the post-launch support calls.

31. Confirm payment, tax, and shipping logic. Edge cases: free shipping thresholds, international tax, B2B discounts, gift cards. Test each one.

32. Run load and performance tests. Tools like K6 or Loader.io. Simulate 10x your typical concurrent visitors. Plus stores should test for BFCM-level peaks.

33. Soft launch with invite-only access. Optional but highly recommended for stores doing over $1M/mo. Open the new site to staff and a small customer cohort for 48 hours before public launch. Catch the last 5% of bugs before they hit revenue.

If you want a deeper look at the testing layer, our guide on ecommerce conversion rate optimization covers checkout-flow testing in detail.

The first 14 days post-launch: what actually happens

This is the section every other migration guide skips. So pay attention.

The morning after you flip DNS, three things happen at once:

Call volume spikes 2-4x. Customers who never call your store start calling. Why? Because the email they got about resetting passwords got buried, or didn't arrive, or they ignored it. Now they're locked out and they want help.

The #1 question becomes "I can't log in." Vervaunt, a Shopify Plus agency, documents this as the top reactivation friction point. They estimate proactive email comms can cut it by 60%, but not eliminate it. The other 40% are calling you.

The #2 question becomes "Where is my order?" Customers whose pre-migration orders didn't import, or imported with different order numbers, suddenly can't find them in their account. They call. See our deep-dive on the WISMO call problem.

The #3 question becomes "Are these the same products?" If reviews didn't migrate, your product pages look bare. Customers who bought before see a stripped-down version of the page and call to confirm.

What to do about it:

If you're on Shopify, this is exactly the scenario Seth was built for. Ringly.io handles password-reset questions, order lookups (with full pre-migration order history if you imported it), and product confirmations without escalating to a human. Seth resolves 73% of these calls automatically. Setup takes about three minutes, no code. Start your free trial.

Beyond AI phone coverage, three things help:

• Front-load your customer communication. Don't send the reset email on launch day. Send a "hey, we're moving" email two weeks before, then the reactivation email on launch day, then a follow-up at day 7. Vervaunt's three-touch sequence works.
• Pre-deploy your phone-support layer. Whether AI or human, get coverage in place before the spike. Trying to staff up mid-spike is impossible.
• Watch your help-desk tags closely. Tag every ticket by reason (password, order lookup, product question, other) so you know what to fix in the product flow.

Our broader guide to AI phone agents for Shopify gets into how the AI agent flow works for these specific scenarios.

Phase 4: The 30-day stabilization checklist (14 steps)

Once you've survived launch week, the work shifts from cutover to recovery and optimization. Here's the 30-day list.

34. Submit your new XML sitemap to Google Search Console. Same domain or new, submit it day one. Helps Google rediscover your URL structure.

35. Submit a change-of-address (if you changed domains). Critical for preserving authority. The change-of-address tool is in Search Console under "Settings".

36. Monitor 404s weekly in GSC. Sort by impressions. Anything getting traffic should redirect to a relevant new URL. Don't 301 everything to homepage. That's a known SEO anti-pattern.

37. Audit redirect chains. Every redirect should be one hop. URL A to URL C, never A to B to C. Tools like Screaming Frog catch chains in five minutes.

38. Monitor support volume and tag every ticket. Tag by reason. If "I can't log in" is 40% of tickets, your reactivation email isn't working. If "Where's my order?" is 30%, your order import had gaps.

39. Watch conversion rate against pre-migration baseline. Conversion will dip 5-15% post-migration on average. That's normal. Anything beyond 15% means something is broken (usually checkout-related).

40. Audit page-load speeds. Run PageSpeed Insights on top 20 revenue pages. Compare to pre-migration. Slow images, unoptimized themes, and app bloat are the usual culprits.

41. Update broken internal links. Run a site crawl, fix any internal links pointing to old URLs. Internal 404s look amateur and confuse search engines.

42. Re-collect reviews on top products. Email customers who bought between 30-90 days ago and ask them to leave a review on the new site. Loox and Judge.me have automated follow-up flows for this.

43. Reconcile analytics. Pre-launch baseline vs. first 30 days. Look for tracking gaps, double-counted conversions, or attribution shifts.

44. Import loyalty point balances. Your loyalty app vendor handles this; coordinate with them. Don't let loyal customers find zero points on launch day.

45. Run a customer-feedback NPS or short survey. "What was confusing about the new site?" Free, fast, surfaces the issues you missed.

46. Hold a post-launch retro. Internal meeting at day 30. What broke, what worked, what surprised. Document for the next migration.

47. Recheck SEO 60 and 90 days post-launch. Rankings typically recover within 4-8 weeks with proper redirects, per LitExtension's SEO migration analysis. If they haven't recovered by day 60, audit redirects again.

Real costs and real timelines

Here's what migrations actually cost and how long they actually take. Numbers from across agencies and migration platforms in 2026.

The hidden costs nobody warns you about:

• SEO recovery time (10-20% temporary traffic dip is normal, recovery 4-8 weeks)
• Customer support spike in the first 14 days post-launch
• Lost orders during cutover (1-3 hours of downtime, even with careful DNS)
• App reconfiguration time (every app needs to be re-set up; budget 8-16 hours)
• Add-on fees on migration apps (SEO URL migration, 301 redirects, priority support, these can double the quote)

One Tinker analysis found that 83% of data migration projects fail or exceed their budget and timeline, so plan for variance.

Migration apps compared (quick reference)

Not every store needs an agency. Most don't. Here's the quick app comparison.

Capterra reviewers rate LitExtension 4.7/5 for tech support and supported platforms, but flag that support isn't 24/7. Matrixify has a 4.9/5 average on the Shopify App Store with the most-cited gripe being a steep learning curve. Cart2Cart reviews on Trustpilot are mixed. Successful migrations praise the automation, but a notable cluster of 1-star reviews report failed jobs and refund disputes.

If you're picking between them: Matrixify if you've got someone technical and a big catalog. LitExtension if you want hand-holding. Cart2Cart if speed matters more than guarantees. For best AI tools for Shopify more broadly, we've covered the operational layer separately.

Apps to install before you launch

Skip this and you'll be rebuilding your operational layer mid-spike. The customer-support stack is the one that breaks first.

• Phone support: Ringly.io for AI phone coverage. Three-minute setup, 73% resolution, Shopify-native. With the post-migration call spike incoming, this is the layer to pre-install. See 24/7 ecommerce phone support for the operational case.
• Help desk: Gorgias or Zendesk for ticket and email management. Native Shopify integrations.
• Reviews: Judge.me, Loox, or Yotpo. Pick one before launch. Switching later costs more.
• Email and SMS: Klaviyo. Use for the reactivation email sequence.
• Returns: Loop or Returnly. Cuts return-related support calls 40-60%.

If you want a deeper read on the support layer specifically, our breakdown of Shopify call center setup covers the phone-volume math.

Try Ringly.io free for 14 days and get Seth answering migration-related calls in under three minutes.

Frequently asked questions

How long does a Shopify migration take? Most simple migrations take 2-4 weeks. Medium stores with 500-5K SKUs take 4-8 weeks. Shopify Plus migrations average 8-16 weeks, and enterprise projects with 50K+ SKUs can run 3-6 months.

Will I lose my Google rankings? With proper 301 redirects from your URL map, most stores see a temporary 10% or smaller traffic dip that recovers in 4-8 weeks. Skip the URL mapping and 301s, and you're risking a 30%+ permanent loss.

Do customer passwords transfer to Shopify? No. Passwords are encrypted and can't be migrated. Every customer has to reset on first login. Send a reactivation email at launch and follow up at day 7 and day 14 to soften the friction.

How much does a Shopify migration cost? Bands: DIY $0-$500, migration app $150-$1,500, small/medium agency $500-$5K, Shopify Plus $10K-$50K, enterprise $50K+. Most agency quotes include hidden add-ons; budget 20-30% above the initial quote.

Can I migrate my product reviews to Shopify? Reviews don't migrate natively. You'll need a third-party app like Judge.me, Loox, or Yotpo. Some review platforms offer import from your old source if it's a supported integration. Otherwise it's a re-collection campaign.

Which migration app is best: Matrixify, LitExtension, or Cart2Cart? Matrixify if you've got a technical operator and a big catalog. LitExtension if you want a guided experience with strong support across 140+ source platforms. Cart2Cart for fast jobs where you're willing to handle hiccups.

Should I migrate to Shopify Plus or standard Shopify? Standard plans handle most stores up to $5M-$10M GMV. Plus makes sense at $1M+/mo, for B2B features, or if you need things like Launchpad, scripts, or Flow. Don't pay for Plus features you won't use.

What's the biggest mistake stores make during migration? Underestimating the 14-day post-launch support spike. The migration itself is the easy part. The aftermath, when customers can't log in, can't find old orders, and notice missing reviews, is where unprepared stores lose revenue. Pre-deploy your customer-support layer, including AI phone coverage, before you flip DNS.

Final thoughts

The cutover is the easy part. The 30 days after are where stores get hurt or where they grow.

Three things separate the successful migrations from the painful ones. They build a complete URL map before they import anything. They authenticate their email so password resets actually deliver. And they front-load their customer-support layer instead of scrambling when calls spike.

If you're migrating to Shopify and want AI phone coverage in place before the call spike hits, start your free Ringly trial. Setup takes about three minutes. Seth resolves 73% of post-migration calls automatically.