Ask brands that replatformed what set it off and the answer is almost never a single dramatic outage. It's a slow-burn condition tolerated for a year or two — data and transaction limits at scale, a total cost of ownership that keeps climbing, an architecture that can't do what the brand wants next — meeting a sharp event that finally forces the decision: a peak-season failure, a vendor price hike or forced upgrade, or an acquisition or modernization mandate. Neither alone does it. The pressure gets absorbed; the event moves a platform that had already lost its case. Below are both families of trigger, and where brands actually go — which, overwhelmingly, is Shopify. For the buyer-side of the move, the companion read is what buyers wish they'd known before replatforming; for the wider stack-consolidation wave, the great consolidation.
The pressure that builds
These are the slow-burn conditions brands live with — often for a year or more — before anything forces the issue. On their own they rarely start a replatform; they set the stage for one.
You outgrew the platform — the ceiling shows up at scale
The most common pressure on the easy end of the market: a brand grows into limits the platform can't clear. Buyers describe data inaccuracies and transaction limitations that surface as they scale, and that bite hardest in peak periods like Q4 — one DTC retailer said it had effectively outgrown its platform because of exactly these constraints. On the heavy end, the opposite ceiling: an enterprise platform too rigid and slow to keep up with a fast-moving DTC strategy. Either way, the platform still runs day to day; it just can't take the brand where it's going, and that gap is what starts the search.
Named in this context: Shopify · Salesforce Commerce Cloud · Adobe Commerce
Total cost of ownership climbs — the license is the small part
On the enterprise platforms especially, the bill that matters isn't the license — it's the agencies, developers, and specialized skills required to run and change the thing. Buyers describe the incumbents as expensive and challenging to manage, with a total cost of ownership that keeps rising against the value they get, and the satisfaction ratings reflect it: the enterprise platforms sit in the low-to-mid sixes while Shopify sits around 8.1. When a brand realizes it's paying enterprise money to move slower than a Shopify competitor, the TCO becomes the argument for leaving, even before anything breaks.
Named in this context: Salesforce Commerce Cloud · Adobe Commerce · Shopify
The architecture blocks the roadmap — headless, DTC speed, or the backend
Sometimes the platform can't do the next thing the brand needs. Buyers describe wanting to go headless or composable for design freedom and speed, or needing to move faster on DTC than a monolithic enterprise platform allows, or hitting backend rigidity around integrations and workflows. The current platform isn't failing — it's a straitjacket, and every roadmap conversation runs into the same wall. That accumulating friction, where the architecture rather than the uptime is the problem, is a quieter but decisive pressure toward a platform that fits where the brand is heading.
Named in this context: Shopify (Hydrogen) · commercetools · Salesforce Commerce Cloud
The event that fires the decision
These are the sharp triggers — the ones buyers can date. Each turns a tolerated situation into an active replatform, and each tends to decide the move at a level that pressure alone never reaches.
A peak-season failure exposes the ceiling
Nothing forces a replatform like a site that buckles when it matters most. Buyers describe data and transaction problems that become acute in high-return, high-traffic periods like Q4 and Black Friday — the moment the platform's limits stop being a tolerable annoyance and start costing real revenue in front of leadership. A performance wall during peak converts a slow-burn "we should look at this someday" into a board-level "this can't happen again," and the replatform gets funded. The pressure was there all year; the peak-season failure is what makes it undeniable.
Named in this context: Shopify · Salesforce Commerce Cloud
A vendor price hike, forced upgrade, or end-of-life resets the economics
The vendor can pull the pin itself. A forced upgrade that requires rebuilding the site, a price increase that breaks the TCO math, or a platform version reaching end-of-life turns "we're not thrilled but it works" into "we have to do something anyway" — and if you're rebuilding regardless, buyers reason, you might as well rebuild on the platform you actually want. An expensive mandatory upgrade is one of the clearest replatform triggers in the corpus precisely because it removes the do-nothing option: the cost of staying suddenly rivals the cost of leaving.
Named in this context: Adobe Commerce (Magento) · Salesforce Commerce Cloud · Shopify
An acquisition or modernization mandate decides it from above
Sometimes the replatform is decided two levels up. An acquisition or merger forces the integration of disparate stacks and a decision about which platform the combined business runs on; a new CMO or CTO arrives with a mandate to modernize; or a parent company standardizes its brands onto one platform. Buyers describe replatforming as part of integrating businesses after acquisitions, and consolidating multiple stores and stacks onto a single system. When the trigger is organizational rather than technical, the best-fit platform can lose to the one leadership has already chosen — and the ecommerce team's job becomes executing a move it didn't originate.
Named in this context: Shopify · Salesforce Commerce Cloud · Adobe Commerce
Where they go
The triggers vary; the destination rarely does. The replatforming wave in the corpus runs overwhelmingly in one direction — off the enterprise incumbents and onto Shopify — with a composable option for the teams that genuinely need it.
Where most brands land, DTC-first: easy setup, a deep app ecosystem, fast time to market, and cost. Shopify Plus (~8.2) carries the larger programs. The clear gravitational center of the wave.
The route for enterprise teams that need front-end flexibility across many touchpoints and have the engineering to own it — buy the flexibility, accept the assembly. A minority path, not the mainstream.
Common where the enterprise backend still matters: move the DTC storefront to Shopify for speed while keeping a heavier platform for omnichannel, ERP, and auditability rather than a clean cut.
The counter-current: the brands that don't replatform
For every brand that moves, others stay on a platform they grumble about — and the reason is the migration itself. Replatforming is a multi-quarter project that migrates data, rebuilds every integration, and re-instruments tracking, and the switching cost keeps dissatisfied brands in place for years, exactly as it does in CRM and CDP. The enterprise backend is the strongest anchor: brands that depend on ERP integration, roles and permissions, auditability, and true omnichannel find no clean Shopify equivalent, so they hold — or split the difference, moving DTC while keeping the incumbent for the back office. The lesson buyers draw is that pressure without a trigger, or a trigger without a plan for the migration, isn't a reason to move yet. The platform that basically works is worth more than the replatform that goes sideways.
What this means if you're weighing a replatform
Three checks before you start. First, diagnose which half of the equation you're actually in: a slow-burn pressure you've tolerated for a year is a reason to plan, but not yet a reason to move — the brands that replatform well have both a real pressure and a datable trigger. Second, be honest about the destination and the hold: Shopify is where the wave goes for DTC, but if your requirements live in the enterprise backend and across channels, the hybrid — DTC on Shopify, the incumbent for omnichannel — may be the rational answer rather than a clean cut. Third, respect the migration: it's a multi-quarter project, and a trigger that forces the timing shouldn't force a rushed cutover. For the full buyer-side playbook, see what buyers wish they'd known before replatforming; for the consolidation wave these moves are part of, the great consolidation; and for the composable-vs-all-in-one decision behind many of these moves, commercetools vs. Shopify.
Common questions
Why do companies replatform their ecommerce site?
Rarely because the site failed outright — almost always because a slow-burn pressure met a sharp trigger. The pressures build for a year or more: outgrowing the platform's data and transaction limits at scale, a total cost of ownership that climbs with licenses, agencies, and developers, and an architecture that blocks what the brand wants to do next. On their own, those are tolerated. What fires the decision is a sharp event: a peak-season performance failure, a vendor price hike or forced upgrade or end-of-life, or an M&A deal or leadership mandate to modernize. Neither half alone moves a brand; together they turn a working-but-strained platform into an active replatform. And the destination is overwhelmingly Shopify (about 8.1/10) against roughly 6.6 for Salesforce Commerce Cloud and 6.25 for Adobe Commerce.
Why are brands leaving Salesforce Commerce Cloud and Magento for Shopify?
Because the satisfaction gap is wide and the pressures point one way. Shopify (about 8.1/10, Plus 8.2) and the enterprise incumbents — Salesforce Commerce Cloud (about 6.6) and Adobe Commerce/Magento (about 6.25) — are separated by roughly a point and a half, and buyers describe the incumbents as expensive and complex to manage. The move is usually DTC-led: brands shift their storefront to Shopify for speed, ecosystem, and cost. What holds some back is the enterprise backend — ERP, roles and permissions, auditability, omnichannel — where the heavier platforms still lead, so a common pattern is moving DTC to Shopify while keeping a legacy platform for omnichannel rather than a clean cut. But the direction of travel is clear: the incumbents are the platforms brands most often leave, and Shopify is where they go.
What triggers an ecommerce replatform?
Six recurring triggers, in two families. The slow-burn pressures: outgrowing the platform (data inaccuracies and transaction limits at scale, especially in peak seasons), climbing total cost of ownership (license plus the agency and developer tax), and an architecture that blocks the roadmap (can't go headless, can't move fast on DTC, a rigid backend). The sharp events: a peak-season or performance failure that exposes the ceiling, a vendor price hike or forced upgrade or end-of-life that resets the economics, and an M&A deal or leadership modernization mandate that decides the move above the ecommerce team. A tolerated pressure plus a datable event is what pulls the pin — so diagnose which pressure is driving you and whether a trigger has genuinely arrived, because the migration is a multi-quarter project you don't want to start on the wrong reason.
This is the aggregate. Your stack is specific.
Weighing a replatform right now? Do a 15-minute interview about your current platform and what's pushing you, and get this personalized — which trigger is really driving your move, where peers your size landed, and what the migration actually cost them.
Get my personalized briefNo password needed · your interview is anonymized before it ever informs a page like this one.