Executive Summary
Gymshark's site went down for 8 hours during a major sale. Cost: an estimated £100,000 in lost revenue. Bombas grew from 500 to 4,000 daily transactions and watched their checkout break — costing $15,000 in minutes. Neither company received a warning. The platform didn't send an alert. The checkout just stopped working during the biggest day of the year.
The question isn't whether to migrate. It's whether you can survive the journey — because 83% of migration projects exceed their budget, but 90% of completed migrations improve revenue.
The platform doesn't send a warning. Your checkout just stops working during your biggest sale.
The Signals That Matter
Operators often frame replatforming as a feeling: "I think we've outgrown Shopify." Feelings aren't decision criteria. Revenue events are.
You need to replatform when any of these are true
Rising maintenance costs that eat margins. If your development budget is consumed by routine maintenance rather than growth features, the platform is costing you twice — the fees you pay and the features you can't build.
More add-ons than built-in features in use. When your Shopify app spend exceeds $800/month, you're paying for a platform that doesn't do what you need out of the box.
Manual processes your competitors automate. Inventory sync, discount management, multi-channel publishing — if these require manual work on your platform, you're subsidizing the platform's limitations with your team's time.
Cart abandonment climbing with no platform tools to fix it. If your platform can't A/B test checkout, offer dynamic discounts, or recover abandoned carts natively, you're leaving 60–80% of potential revenue untouched.
What Migration Actually Costs
The budget you set is almost certainly wrong. Here's what migration actually costs across three scenarios:
| Component | Small Store (< 1K SKUs) | Mid-Market (1K–10K SKUs) | Enterprise (10K+ SKUs) |
|---|---|---|---|
| Platform migration (dev + data) | $2,000–$15,000 | $15,000–$75,000 | $75,000–$500,000 |
| SEO recovery (traffic loss period) | 1–3 months, 10–15% drop | 2–4 months, 15–30% drop | 4–12 months, 20–40% drop |
| App/integration rebuilds | $500–$3,000 | $5,000–$25,000 | $25,000–$100,000 |
| Team retraining | 1–2 weeks | 2–4 weeks | 1–3 months |
| Opportunity cost | Low | $50K–$200K in delayed initiatives | $200K–$2.3M in foregone campaigns |
| Timeline | 2–8 weeks | 3–9 months | 6–14 months |
| Post-migration maintenance (Year 1) | 10–20% of project cost | 10–20% of project cost | 10–20% of project cost |
The cost you don't budget for
The SEO Tax Nobody Plans For
Even perfect migrations lose organic traffic. The question is how much and for how long.
| Migration Quality | Traffic Drop | Recovery Timeline | Permanent Loss Risk |
|---|---|---|---|
| Well-executed (all redirects, URL mapping, structured data) | 10–30% in Month 1 | 90–95% recovery within 30 days, full recovery by 90 days | Minimal |
| Average execution (most redirects, some gaps) | 20–40% in Month 1 | 4–12 weeks before improvement begins | 5–10% permanent |
| Poor execution (missed redirects, broken canonical tags) | 30–60% drop | 6–12 months — or never fully recovers | 15–30% permanent |
| No SEO planning | 50%+ drop | Average 523 days to recover (17 months) | Significant |
Key Takeaway
The Migration Readiness Score
Before running the cost comparison, score your current situation. This separates operators who should migrate from operators who think they should migrate because they saw a competitor's shiny new site.
Rate each dimension 1-5 (1 = no issue, 5 = critical):
- Revenue ceiling: Has the platform caused lost sales? (Checkout failures, capacity limits, missing features that directly prevent transactions)
- Maintenance drag: What percentage of dev/team time goes to platform workarounds vs. growth work? (>50% = score 5)
- Cost escalation: Are platform costs (fees + apps + integrations) growing faster than revenue? (Calculate: platform cost growth rate ÷ revenue growth rate. If >1.5x, score 5)
- Competitive gap: Can competitors do things their platform enables that yours prevents? (Not features you want — features that generate revenue you can't)
- Data portability: If you decided to leave tomorrow, how much data would you lose or need to rebuild? (Full export available = 1, locked in = 5)
Score interpretation: 5-10 = stay and optimize. 11-17 = monitor quarterly, fix the highest-scoring dimension. 18-25 = migration likely justified — run the cost comparison below.
Gymshark scored a 22 the quarter before their Black Friday crash — revenue ceiling (5), maintenance drag (4), cost escalation (4), competitive gap (4), data portability (5). Bombas was at 19 when their checkout started failing at 4,000 daily transactions. Both cases: the score predicted the crisis by 3-6 months. The operators who run this score quarterly catch the problem before the checkout breaks during a sale.
The Decision Framework
Step 1: Calculate the Cost of Staying
Add up what your current platform costs you — not the subscription, but the total cost:
- Monthly platform fees + transaction fees + app subscriptions
- Developer hours spent on maintenance (not features)
- Revenue lost to platform limitations (checkout failures, missing features, slow load times)
- Opportunity cost of features you can't build
Step 2: Calculate the Cost of Leaving
Use the table above to estimate your migration scenario. Add 30% buffer — 83% of projects exceed their budget.
Step 3: Compare Over 3 Years
The comparison that matters
If the gap is less than 20%, don't migrate. The risk and disruption aren't worth a marginal improvement.
Step 4: Check Your Timing
Migrate during your slowest quarter. Never during peak season. J.Lindeberg migrated in 16 weeks and saw 70% revenue growth — but they timed it for their off-season.
Three Operator Profiles
Profile 1: Solo DTC, 200 SKUs, $15K/Month on Shopify
App costs hit $600/month. Transaction fees are $360–$435/month. Total platform spend: ~$1,100/month on Basic Shopify.
Stay. At this revenue, migration to WooCommerce would cost $5K–$10K and save ~$400/month in transaction fees. Break-even: 12–25 months. Not worth the SEO risk and operational disruption. Revisit at $50K/month.
Profile 2: Growing Brand, 3,000 SKUs, $80K/Month on Shopify
Transaction fees: $1,920–$2,320/month. App costs: $1,200/month. Site slowing during promotions. Need B2B pricing tier that requires Plus ($2,300/month).
Consider migrating. Total Shopify cost at Plus: ~$5,800/month. WooCommerce equivalent: ~$2,500/month (hosting + maintenance). Savings: ~$3,300/month = $39,600/year. Migration cost: $25K–$50K. Break-even: 8–15 months. The math works — if you have developer resources.
Profile 3: Enterprise, 40K SKUs, $500K/Month on Custom Legacy
Site crashes during sales. Integration with new 3PL impossible on current architecture. 6-person dev team spends 70% of time on maintenance.
Migrate. The dev team maintenance cost alone is $300K+/year on a platform that's actively limiting revenue. Migration to Shopify Plus or modern headless: $200K–$500K upfront, but frees 4 developers ($200K+ annually) and eliminates crash risk during peak. Daniel Wellington cut licensing costs 50% after migrating from Commercetools to Shopify Plus.
When Not to Migrate (The Other Half of the Decision)
Do not migrate if
You're migrating for features you won't use in 6 months. The new platform's feature list is seductive. But if you haven't validated demand for those features with your customers, you're spending $25K–$500K on a hypothesis.
You don't have a dedicated project owner. Migrations without a single person accountable for timeline, budget, and redirect mapping have the highest failure rate. If "the team" owns the migration, nobody owns the migration.
Related Decisions
- The eCommerce Platform Decision Framework — If you've decided to leave, this framework helps you choose what to move to. Constraint-based evaluation, not feature lists.
- The Real Cost of Your eCommerce Tool Stack — Sometimes the problem isn't the platform — it's the 15 apps bolted onto it. Audit your tool stack before assuming the platform is the issue.
