Adobe Commerce buyers frequently describe the platform as development-heavy — but that complaint does not distinguish satisfied buyers from dissatisfied ones. Development work is named at almost the same rate by buyers who rate the platform 8 or better as by buyers who rate it in the bottom half. What separates those two groups is cost. For the enterprise shelf this platform sits on, see Salesforce Commerce Cloud alternatives, and Adobe Commerce vs. Salesforce Commerce Cloud for the head-to-head.
The alternatives, by what they are
Every platform buyers name around Adobe Commerce, sorted into lanes by what the product is and whether anyone was observed moving to it. The concentration in the second lane is the striking feature: departures from this platform do not fan out across the category.
What lower-rating Adobe Commerce buyers complain about
Cost is the theme that actually divides the two groups, and the gap is wide. One in five buyers rating Adobe Commerce in the bottom half raises cost, licensing or price; among buyers rating it 8 or better, one in thirty-four does. No other theme in these interviews separates them like that. Buyers who left describe high licensing cost and weaker vendor/marketplace ecosystem, and high development cost, inflexibility, and scalability issues. A second cluster is about the platform feeling behind: buyers describe it as outdated and limiting across merchandising, content updates, navigation and mobile experience, and one reports page load times and stability problems while migrating away. That ageing theme is real but small — it appears in under a tenth of the low ratings, and a handful of satisfied buyers raise it too, so it is a complaint rather than a verdict on the platform’s direction.
Why the developer complaint is not the dividing line
Adobe Commerce is widely described as dev-heavy, and buyers say so in these interviews — roughly a quarter of them mention development work, engineering time or code. The part worth noticing is that the rate barely moves with satisfaction: about a quarter of the buyers rating it 8 or better say it, and about a quarter of those rating it in the bottom half. Customization and flexibility behave the same way, named by around a third of each group.
Development dependency therefore does not behave like a dissatisfaction signal in these interviews; it is a characteristic buyers describe at similar rates whether they rate the platform well or poorly. One buyer calls it highly customizable and enterprise-suited in the same breath as less nimble and more dependent on developers for changes. The implication — ours, not a buyer’s — is that development burden alone does not explain the difference in satisfaction, and cost does. That makes what will this cost us over three years, including the team required to operate it? a useful question to put beside how much development will it need?
Where buyers go
Grouped by whether buyers were observed moving there. The first group is where the departures went, and it is one platform in two tiers. The second registers as churn without leaving Adobe. The third is named in the category by buyers weighing their options — a considered comparator is not an observed destination, and the page keeps the two apart.
Where the departures actually went
Ten of the sixteen departures that state where they went name Shopify. Buyers explain it through their own team’s speed rather than through platform capability — one describes Shopify’s backend toolkit as more familiar and flexible for their team, another moved after finding the incumbent dev-heavy, a third describes the platform they left as slow to change.
Four more state a move to the enterprise tier, and it is the highest-rated platform in this set. One describes moving after weighing high licensing cost and a weaker vendor and marketplace ecosystem; another had been running an old and barely functioning installation before the move.
No head-to-head published yet
Stayed inside Adobe rather than leaving
One departure is an Adobe-internal consolidation rather than a like-for-like commerce-platform replacement: a company standardizing globally moved several regional website platforms, Adobe Commerce among them, onto Adobe Experience Manager. It registers as churn in the data while Adobe keeps the account, and AEM is a content and experience platform rather than a commerce platform, so it is worth separating from the rest on both counts.
No head-to-head published yet
Named in the category, but not where anyone went
Rated a little above Adobe Commerce and still below what buyers give software generally. Nobody in these interviews left Adobe Commerce for it; one buyer comparing the two describes Adobe Commerce as more constrained for development and flexibility. A considered comparator is not an observed destination, and its own departures run to Shopify as well.
The composable-commerce option in this comparison set. Named in the category and in nobody’s exit here, and rated only a little above the platform they would be leaving.
No head-to-head published yet
The highest-rated of the platforms nobody in this corpus moved to, on a sample small enough to read with care. It appears in the category conversation but not in the observed exits.
No head-to-head published yet
Across the set, the destinations that actually attract departures rate well above what buyers left, and the platforms that rate closest to it attract none. That is consistent with the cost finding above rather than a capability one: these buyers are not trading up in platform weight so much as trading out of its economics. The next section takes the other side.
Want this read against your own stack?
Get my read →When does staying on Adobe Commerce make sense?
Thirty-four buyers in this corpus rate Adobe Commerce 8 or better, and they describe many of the same characteristics as lower-rating buyers: customization depth, flexibility and development requirements. The clearest difference is cost. That suggests the useful stay-or-switch question is not whether Adobe Commerce requires engineering — it does for buyers on both sides of the rating — but whether the cost of the platform and the team around it remains defensible for the job it is doing. The interviews establish the difference in cost commentary; they do not establish exactly why one team accepts those economics and another does not.
Common questions
Why do buyers leave Adobe Commerce?
Cost is the complaint that most clearly distinguishes lower-rating buyers, and it also appears directly in the departure accounts. Development burden is named at almost the same rate by buyers who rate Adobe Commerce 8 or better as by buyers who rate it in the bottom half — roughly a quarter of each group mentions development work, engineering time or code. Cost does not behave that way at all: one in five buyers rating it in the bottom half raises cost, licensing or price, against one in thirty-four of the satisfied. The departures echo that split. Buyers describe leaving over high licensing cost and weaker vendor ecosystem, high development cost, inflexibility, and scalability issues, and one describes the platform as expensive with support that made basic site changes slow. The developer dependency is real and buyers who like the platform describe it too — they simply do not treat it as a reason to leave.
What do buyers switch to when they leave Adobe Commerce?
Shopify, overwhelmingly. Sixteen of the twenty-four departures in this corpus state where they went, and fourteen of those name Shopify or Shopify Plus — ten to Shopify and four to Shopify Plus. Shopify rates 8.1/10 and Shopify Plus 8.2/10 against Adobe Commerce at 6.2/10, so the observed destinations are rated substantially higher by their own buyers. The reasons buyers give centre on operating speed rather than capability: one describes Shopify's backend toolkit as more familiar and flexible for their team, another moved after finding Adobe Commerce dev-heavy, a third describes the platform they left as outdated and limiting across merchandising, content updates and navigation. The other two go elsewhere: one moved to Shopware, and one is an Adobe-internal consolidation onto Adobe Experience Manager rather than a commerce-platform replacement. Three further departures name a platform only as a comparison without stating a move, and five name no destination at all.
Is Adobe Commerce still called Magento?
Buyers still call it Magento, and that is worth knowing if you are searching for opinions about it. Adobe acquired Magento in 2018 and renamed the commercial product Adobe Commerce, but in this corpus eighteen of the twenty-five departure accounts refer to it as Magento and only two use the Adobe Commerce name. Both names describe the same platform in these interviews, and buyers use them interchangeably when they use the newer one at all. The practical consequence is that research about the platform is split across two names: a search for Adobe Commerce will miss most of what buyers who left it actually said, because they said it about Magento.
Is Adobe Commerce a good platform?
It rates 6.2/10 across a large sample, which is below the corpus-wide average of about 7.2/10 across all software categories, and below every other commerce platform here that clears a meaningful sample. But the rating splits rather than settling: thirty-four buyers rate it 8 or better and forty-nine rate it in the bottom half, and both groups describe the same characteristics. Customization and flexibility are named by about a third of each group; development work by about a quarter of each. What separates them is cost. The pattern suggests that development dependency alone does not explain satisfaction; the much clearer dividing signal is whether buyers object to the economics around the platform. The interviews do not establish exactly which organizational conditions make those economics acceptable.
Get this research made for your stack
Weighing whether Adobe Commerce still fits, or what a move to a lighter platform would actually cost you? Do a 15-minute interview about your stack and your roadmap, and get a personalized read.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.