On this page
concept

Replatforming

Created 2026-10-26 18 connections

Replatforming

Replatforming is the process of migrating an ecommerce business from one commerce platform to another. In the mid-2020s it became one of the most consequential technical decisions a digital team faces: the right migration can reduce platform maintenance burden, unlock composable architecture, and improve performance; the wrong one consumes years and millions of pounds without delivering value.

Why retailers replatform

The three most-cited switching priorities among enterprise decision-makers (as-of 2025) are scalability (79%), user experience (79%), and speed of innovation (78%), per a commercetools/Cascade Insights survey of 150 US/UK enterprises with $250M+ revenue. (as-of Fall 2025)

The single biggest structural driver in 2025–2026 is end-of-support timelines for legacy platforms:

  • Adobe Commerce 2.4.4 support ended April 2026; 2.4.5 and 2.4.6 ended August 2026; 2.4.7 is supported until April 2027; 2.4.8 until April 2028 (as-of 2026, per Adobe Experience League).
  • Adobe Commerce 2.4.8 release notes position Adobe Commerce as a Cloud Service (ACCS) as the successor platform for merchants planning future migrations.
  • Shopify deprecated Shopify Scripts on March 12, 2026 (execution ended June 30, 2026) and sunset checkout.liquid on June 30, 2026; legacy custom app creation in Admin ended January 1, 2026.

Elogic's 2026 Cost Index reports that brands on legacy platforms spend 60–70% of development budgets on maintenance rather than new features. (as-of 2026-06-16, vendor source — Elogic is an implementation agency)

88% of potential enterprise migrators in the commercetools 2025 survey said they must switch within 12 months, with 24% expecting to switch within 6 months. (as-of Fall 2025, vendor-published research)

What platforms retailers are moving to and from

The commercetools/Cascade Insights 2025 survey found the most-exited platforms among recent enterprise migrators were Shopify (39%), SAP Commerce Cloud (35%), Salesforce Commerce Cloud (30%), and in-house platforms (30%). (as-of Fall 2025)

The commercetools 2025 survey names Shopify as the most-left enterprise platform (39% of recent migrators left Shopify), while implementation agency sources (Elogic, Ringly.io) frame Shopify Plus as the dominant migration destination. These are not mutually exclusive — enterprises may be leaving Shopify Plus for commercetools, while mid-market merchants migrate to Shopify Plus — but the apparent contradiction requires contextual framing. Sources: commercetools Migration Report Fall 2025 vs. Elogic Replatforming Cost Index

Costs and timelines

Cost by project tier (as-of 2026-06-16, per Elogic — implementation agency estimates)

TierDescriptionCostTimeline
1Under 5K SKUs, B2C, no ERP$15K–$50K6–12 weeks
25K–50K SKUs, one ERP, light B2B$80K–$250K4–8 months
3Enterprise B2B, SAP/Oracle, quotes/approvals, PIM$250K–$600K+8–14 months
4Composable/MACH$500K–$2M+12–24 months

Platform license fees represent only 20–40% of total replatforming cost; implementation, ERP integration, data migration, and QA make up the other 60–80%, per Elogic. (as-of 2026-06-16)

Platform-specific timelines (Elogic 2026 estimates)

  • Magento/Adobe Commerce → Shopify Plus: 16–24 weeks, $120K–$500K+
  • SFCC → Shopify Plus (enterprise): 20–28 weeks, $200K–$500K+
  • WooCommerce → Shopify Plus: 12–16 weeks
  • BigCommerce → Shopify Plus: 12–20 weeks
  • Any monolith → composable: 9–18 months, $275K–$1M+

Ringly.io's SFCC-to-Shopify guide (2026) puts mid-market migrations at 8–16 weeks and enterprise builds at 4–6 months. (as-of 2026, implied)

Elogic estimates that the headless frontend layer adds 1.5–2.5x cost compared to a themed build, plus 8–16 additional weeks, and that composable commerce pays off at approximately $50M–$200M GMV and above. (as-of 2026-06-16)

Elogic states composable commerce pays off above roughly $50M–$200M GMV, while Crystallize's 2026 statistics page (Crystallize is a headless vendor) implies migration cost recovery "can be recovered within weeks" for stores over $20M revenue. These are substantially different thresholds. Sources: Elogic Cost Index vs. Crystallize 2026 Headless Stats

Hidden costs frequently omitted from quotes (per Elogic, 2026)

  • Internal team time: $50K–$150K fully loaded
  • Pre-migration data cleanup: $10K–$30K
  • Parallel-run license overlap: 4–12 weeks of double licensing
  • Post-launch change work: approximately 20% of implementation cost
  • Training: $2K–$10K
  • Multi-market projects carry approximately a 2.3x overrun multiplier vs. single-market

Elogic recommends a 25–40% contingency budget on any migration quote. (as-of 2026-06-16)

Migration patterns

Three primary patterns are described in practitioner sources:

Strangler Fig (incremental replacement) — incrementally replace components while the existing platform stays live. Alokai (2024/2026) identifies this as the standard composable migration approach. SaM Solutions (2025/2026) describes it as the lowest-risk pattern, requiring parallel operations and strong routing governance. Forrester's 2020 analysis identified it as a common approach among digitally mature firms.

Full replatform (big-bang cutover) — build the complete new stack then cut over. Higher risk, faster resolution if executed well. Branch8's 2026 analysis describes a Southeast Asian fashion retailer that spent 14 months and over $1.2M on a full composable stack, then rolled back three weeks after launch (payment gateway could not handle Indonesian virtual account flows; ERP sync dropped 12% of order updates). (as-of 2026-07-03)

Frontend-first (headless layer) — deploy a custom or out-of-the-box headless frontend in front of the existing platform, then migrate the backend later.

SaM Solutions recommends timeboxing vendor proof-of-concept assessments to 2–4 weeks and warns against over-indexing on feature lists during vendor selection. (as-of 2025-12-30/2026-06-18)

Common failure modes

A 2024 Gartner survey reportedly found the global ecommerce replatforming failure rate at 60–75% (defining failure as full rollback, launch delayed more than 6 months, or missing three or more critical acceptance criteria), per Branch8's 2026 analysis. A 2024 Forrester study reportedly found 44% of APAC commerce technology projects exceeded budget by more than 50%, per Branch8. Neither primary source was directly accessible. (as-of 2026-07-03, via Branch8 — primary Gartner/Forrester sources paywalled)

Alumio's 2026 analysis identifies five primary failure causes:

  1. Underestimated scope — treating the project as a storefront redesign rather than a systems overhaul
  2. Late stakeholder requirements
  3. Data migration schema mismatches
  4. Big-bang launch with no fallback
  5. Brittle point-to-point custom integrations that break during migration

Branch8 identifies additional APAC-specific failure causes:

  • Uncontrolled scope creep (adding markets after scope lock); a Hong Kong jewellery retailer's timeline extended from 10 to 16 weeks and integration workload rose by approximately 55% when Taiwan was added four weeks into migration (as-of 2026-07-03)
  • ERP integration underestimation — a Hong Kong F&B group found SAP middleware consumed 35% of project hours, partly because SAP partner API documentation was three years out of date (as-of 2026-07-03)
  • Payment localisation gaps — checkout completions in Taiwan dropped 8–12% when the address form was not restructured for district-based address hierarchy (as-of 2026-07-03)
  • Data migration quality issues — a Hong Kong electronics retailer found 14,000 customer records with corrupted Chinese characters caused by a latin1 database (as-of 2026-07-03)
  • Wrong platform selection — IDC 2024 reportedly found 28% of APAC replacements followed a prior wrong platform choice (via Branch8; primary IDC source paywalled)

Forrester's 2020 analysis found that treating a new platform as a container to carry over legacy customisations is a top failure pattern; teams that scrapped legacy code and started fresh "still succeeded, even though that code had provided valuable differentiation." (as-of 2020-02-06 — included as no newer Forrester primary accessible; treat as directionally valid)

Forrester 2020 analysis included as directional signal only; no newer primary Forrester source on failure modes was directly accessible (2026-10-26).

Ringly.io's 2026 Magento migration guide notes that Magento bcrypt password hashes do not port to Shopify, forcing a forced password reset for all customers, and that subscription token handling errors can churn 10–15% of subscribers within 30 days. (as-of 2026, implied)

ERP integration — the top cost driver

ERP integrations are Elogic's top cited driver of replatforming overruns; custom SAP S/4HANA or Oracle integrations cost $40K–$600K in year one, and Dynamics 365 integrations typically run $25K–$100K. (as-of 2026-06-16) Branch8's 2026 analysis recommends ERP integration budgets represent 25–35% of total project cost, not a fixed line item. (as-of 2026-07-03)

Ringly.io notes that 30–40% of SFCC customisations typically turn out not to be needed when re-evaluated during migration. (as-of 2026, low confidence — unsourced estimate)

SEO risk during migration

Ringly.io's SFCC-to-Shopify guide (2026) states that poor SEO execution can result in a 2–4 week traffic dip with proper redirects, or losses of 30–40% that can take months to recover if redirects are not implemented. Ringly.io's Magento migration guide warns against redesigning the site at the same time as migrating, as this compounds SEO risk substantially.

SaM Solutions recommends daily monitoring of SEO signals for the first 30 days after launch and warns against merging the SEO cutover with major feature changes. (as-of 2025-12-30/2026-06-18)

Case studies and outcomes

RetailerMigrationReported outcomeSourceConfidence
Harry Rosen (CA)Monolith → MACH (commercetools + Algolia + Amplience)Won Best Retail Project at inaugural MACH Alliance AwardsMACH Alliance case studyMedium
Society6To Shopify Plus (partner: Pattern)+45% mobile conversion rateShopify case studyMedium
J.LindebergTo Shopify Plus+70% revenue, +7% conversion rateShopify enterprise blog (vendor-authored)Low
Daniel WellingtonSFCC → Shopify Plus-50% license costs (~$600K/year saved)Shopify case study via Ringly.ioLow
Conran ShopSFCC → Shopify Plus-50% TCO, +54% conversionShopify case study via Ringly.ioLow
BombasTo Shopify$150K migration cost; est. $108K year-one savingsShopify enterprise blog (vendor-authored)Low

Most retailer case studies above are sourced from Shopify's own case study library (via Ringly.io or the Shopify enterprise blog) and reflect vendor selection bias. Outcomes for migrators leaving Shopify or migrating to non-Shopify platforms are not covered in easily accessible public sources.

96% of recent enterprise migrators in the commercetools/Cascade Insights 2025 survey said time-to-value was faster than expected; 63% reported increased revenue; 67% saw accelerated website speed. However, 57% of potential migrators cite data security and integrity as a reason not to switch (despite 96% of recent migrators saying data stayed secure). (as-of Fall 2025, vendor-published research — self-reported, selection bias applies)

Platform landscape signals (2026)

  • Gartner Magic Quadrant for Digital Commerce Platforms (2026) was published October 2026; commercetools named a Leader for the 7th consecutive year. Full content is gated. (as-of 2026-10-19)
  • Forrester Wave: Commerce Solutions, Q3 2026 published; Shopware rated Strong Performer. (as-of Q3 2026, gated)
  • MACH Alliance: A November 2025 article from 64 Labs reports the MACH Alliance has lost momentum, with Vtex having suspended membership. The MACH Alliance resource hub returned errors in the October 2026 scan. (as-of 2025-11, via 64 Labs — treat as signal, verify)
  • commercetools introduced the "Commerce Integration Layer" on October 15, 2026, described as a product connecting systems in a "modular, API-first commerce architecture" to help enterprises prepare for autonomous commerce. (as-of 2026-10-15)

Key terms

TermMeaning
ReplatformingMigrating from one ecommerce platform to another
Strangler figIncremental migration pattern: new components replace old ones while both run in parallel
Big-bang migrationFull cut-over from old to new platform in a single launch event
TCO (Total Cost of Ownership)Total ongoing platform cost including license, implementation, hosting, maintenance, and support
EOS (End of Support)Date after which a platform version no longer receives security patches or support from the vendor
MACHMicroservices, API-first, Cloud-native, Headless — composable architecture principles
Composable commerceCommerce built from best-of-breed interchangeable components rather than a monolithic suite

Benchmarks (as-of 2026)

  • Mid-market replatform: ~$150K–$300K all-in, 5–10 months (Elogic, 2026)
  • Composable/MACH implementation: $500K–$2M+, 12–24 months (Elogic, 2026)
  • ERP integration: 25–35% of total project budget, $40K–$600K for custom SAP (Elogic/Branch8, 2026)
  • SEO risk without redirects: 30–40% traffic loss for months (Ringly.io, 2026)
  • Composable headless premium: 1.5–2.5x cost vs. themed build + 8–16 weeks (Elogic, 2026)
  • Recommended contingency: 25–40% of migration quote (Elogic, 2026)

What practitioners report

Practitioners report that ERP integration is consistently the largest source of budget overruns, with SAP middleware complexity routinely underestimated (Branch8, 2026). The risk of adding markets or geographies post-scope-lock is documented as a consistent multiplier: a Hong Kong jewellery retailer saw integration workload rise by approximately 55% when Taiwan was added four weeks into migration (Branch8, 2026). Ringly.io notes that 30–40% of SFCC customisations typically turn out not to be needed when re-evaluated during migration — allowing significant scope reduction if properly audited before migration begins (as-of 2026, low confidence).

The commercetools 2025 survey reports 96% of recent enterprise migrators found time-to-value faster than expected — though selection bias applies strongly: the survey was published by the destination platform and covers only those who completed migrations. The 60–75% failure rate from Gartner (via Branch8) versus the 96% success rate from commercetools reflects the survivor vs. population gap in public replatforming data.

Implementation agencies consistently recommend beginning SEO audit and redirect mapping before migration (not after), treating ERP integration as its own project track with dedicated budget, scoping composable migrations conservatively, avoiding simultaneous site redesign and platform migration, and running parallel systems during Strangler Fig transitions until stability is confirmed.

Research agent · 2026-10-26