What the interviews show. Both platforms are described running large, complex commerce estates, and buyers name each other in both directions. Adobe Commerce buyers describe a platform that will do anything and asks for developers to do it — “super flexible”, “very open”, and in the same breath “very dev-reliant” and “costly on development”. Salesforce Commerce Cloud buyers describe one that arrives configured and connected — “a lot less custom work than what we used to have to do” — and a boundary around what they can change afterwards: “pretty boxed in”, “we don't really have the agility to go in and make changes”. The word flexible appears on both sides and means opposite things, which is the clearest thing these interviews separate. And the alternative most present in both sets is neither of the two: Shopify appears more often among the lower raters of either platform than the other platform does, so a shortlist built from this pair alone is probably short a name.
| Strongest contrast in these interviews | What you can build on it, and the developers it takes to build it | What arrives configured, and the boundary around changing it |
|---|---|---|
| Buyer pattern in these interviews | Retail and manufacturing brands with in-house or agency development, often on the platform for many years | Global brand groups running many markets on one contract, frequently alongside other Salesforce clouds |
| Most-discussed job | The e-commerce storefront and catalog | The e-commerce storefront and catalog |
| Also does | B2B and multi-store estates, heavily customized subscription and pricing setups | Site search, merchandising and product recommendations in-platform, with the wider Salesforce estate alongside |
| Praised most | Flexibility, and the size of the developer pool — “it's so common… you can find developers” | Scale and connectedness — “a globally scalable platform”, “out-of-the-box integrations, integration APIs available” |
| Top complaint | The development every change requires, and upgrades that re-break customizations | Speed of change, raised by nine of its lower raters against two of its high ones |
| Relative cost | Cost sits almost entirely in the lower band — nine of sixty-three lower raters against one of thirty-three high ones — and buyers split it between licence and development hours | Cost is raised across the range, by eighteen lower raters and six high ones, usually as total cost of ownership rather than sticker |
| Where buyers say it fits | Praise concentrates where a team can carry development and wants the store to work its own way | Praise concentrates where many markets need one platform and standard coverage is enough |
What buyers say about each platform
Every buyer interview spends its minutes somewhere — praising the thing that won the deal, or flagging the thing that still stings. Map where those minutes go for Adobe Commerce and Salesforce Commerce Cloud, and the strongest contrasts run in opposite directions:
Relative share of buyer commentary by theme in Alium's verified interviews, praise vs. complaint, through September 2026. Widths compare themes within this pair — they are relative, not counts.
In their own words
The phrases buyers reach for, verbatim, when they describe each platform:
Adobe Commerce
“super flexible” build
“you can find developers” hiring
“our site builds are safe, they're strong, they don't break” stability
“very dev-reliant” effort
“costly on development” cost
“we fix one thing and something else breaks” upgrades
Commerce Cloud
“a globally scalable platform” reach
“out-of-the-box integrations, integration APIs available” connected
“a lot less custom work than what we used to have to do” effort
“pretty boxed in” ceiling
“we don't really have the agility to go in and make changes” speed
“very expensive to maintain” cost
Where Adobe Commerce buyers concentrate their praise
Adobe Commerce's praise concentrates on what buyers can build on it. Its high raters describe a platform that bends: “super flexible” with the ability to “do it your way”, “very open and… very good to create a custom website in whatever direction you want to go”, a wide universe of plugins from third-party vendors. Alongside that runs something no Salesforce Commerce Cloud buyer in this set raises at all — the size of the talent pool. Four of its thirty-three high raters name it directly: one rates it “a strong nine” because “it's so common” that “you can find developers, you can find people that know what you're talking about”, another that “a lot of people can support that platform”, a third that the developer ecosystem is “quite good in our geography”. Stability appears in the same band — “our site builds are safe, they're strong, they don't break”, and one account reporting uptime “pretty much 100% of the time”. The complaints are the same fact from the other side. The platform is “very dev-reliant”, “very heavy on development” and “costly on development”, and it is not an out-of-the-box scenario like Shopify or BigCommerce. Upgrades are where that compounds: buyers describe having to “back patch” customized sections after security updates and significant re-work of the existing custom code, and one says that with enough customization “we fix one thing and something else breaks”. Development, though, is not what separates its satisfied buyers from its dissatisfied ones: it is named at close to the same rate in both bands, which is what the wider Adobe Commerce commentary shows too. Cost is the theme that splits them — nine of its sixty-three lower raters raise it against one of its thirty-three high ones — and it is split between the licence and the development hours, with one buyer on the open-source edition noting they are “paying zero” against a six-figure contract at a previous employer.
Where Salesforce Commerce Cloud buyers concentrate their praise
Salesforce Commerce Cloud's praise concentrates on arriving configured and connected. Its high raters describe “a globally scalable platform that does 70% of what you need it to do in a very manageable way”, extensive integration capabilities, with out-of-the-box integrations, integration APIs available, and a “very connected ecosystem” that several describe running alongside other Salesforce clouds. The effort saving is named directly and in the same terms Adobe Commerce buyers use for the opposite: one says Salesforce offers “a lot less custom work than what we used to have to do”, another that it lets the marketing team make quick changes directly instead of going through developers. Global brand groups are the recurring pattern — one platform, one contract, many markets. The complaints are the ceiling that comes with it. Speed of change is the clean band split here: nine of its one hundred and thirty-one lower raters raise it against two of its eighty-one high ones — “we don't really have the agility to go in and make changes”, a “backlog” created by needing a specific headcount to manage the backend, changes described as “slow” and sometimes “painful”. Buyers describe the platform as “pretty boxed in” with “very little variation in what's out of the box”, and one as “very close-ended… either this is how it works, use it or don't use it”. Cost runs across the whole range rather than only the bottom — eighteen lower raters and six high ones — and it is usually framed as total ownership rather than sticker: “very expensive to maintain a Salesforce website”, “real expensive” with significant SI work that makes it feel “effectively on-prem”. One high rater calls it “very expensive” and worth it in the same sentence.
What buyers wish they'd known
Before picking Adobe Commerce
The flexibility and the development load are the same property, and its buyers say so — one counts the ability to “mold them to what you need” among both the best and the worst things about Adobe products. What separates its happy buyers from its unhappy ones is not that load, named at close to the same rate in both bands, but cost. Our recommendation, not a practice buyers describe: price the upgrade path and the running development, not just the build — buyers describe the pain arriving at version upgrades rather than at launch. On third-party integrations the commentary points both ways — several buyers name a wide universe of plugins as a strength, one lower rater says “no one is really building for Magento”. Check the integrations you need specifically.
Before picking Salesforce Commerce Cloud
Speed of change produces one of the clearest rating-band differences in its commentary: nine lower raters raise it against two high raters. Our recommendation, not a practice buyers describe: take the changes your merchandising team made last quarter and ask how each would be done here — its high raters describe standard coverage being enough, and its lower raters describe waiting on a backlog. Ask about cost as total ownership rather than licence; buyers in both bands frame it that way.
Four questions the interviews raise
Buyers describe changes going through code: “very dev-reliant”, and “a significant lift on our side” for customer-facing work.
Buyers describe the marketing team making quick changes directly instead of going through developers — within what the platform already does.
Its high raters describe building well past it — heavily customized subscription, pricing and B2B setups.
Its lower raters describe the boundary: “pretty boxed in”, “very little variation in what's out of the box”.
Multi-store estates appear in its commentary, usually described alongside the customization holding them together.
Global brand groups on one contract are the recurring pattern, and scale is its most-praised theme.
Four of its high raters name the developer pool as a reason to stay — “it's so common… you can find developers”.
No buyer in this set raises developer availability; several describe needing a dedicated headcount or systems integrator instead.
Don't see your exact situation?
Get the read for your brand →How the operating conditions differ
Recurring situations in the corpus, and where the evidence concentrates in each:
Pressures visible in these interviews
The complaints these interviews carry sit on both sides: Adobe Commerce's are development load, upgrade breakage and cost; Salesforce Commerce Cloud's are speed of change, the limits of out-of-the-box coverage, and total cost of ownership. Pace of innovation is raised on both, by high and lower raters alike, so these interviews record it as contested rather than as a difference between them. Both sets of buyers describe constraints on changing the store, and they locate them differently: Adobe Commerce buyers describe the development and maintenance a change requires; Commerce Cloud buyers describe the boundaries and the backlog around changes the platform does not make easy. The implication — ours, not a buyer's — is that the choice is less about what either can do than about which constraint your team is equipped to absorb. Worth noting for anyone reading this as a shortlist: Shopify is named more often by each platform's lower raters than the other platform on this page, so the real alternative set is wider than this pair — and while several accounts describe moving from Adobe Commerce to Commerce Cloud, no buyer in this set describes moving the other way. For adjacent reads, see Shopify vs. Salesforce Commerce Cloud, BigCommerce vs. Salesforce Commerce Cloud, and commercetools vs. Shopify, and the churn hubs for Adobe Commerce and Salesforce Commerce Cloud.
Common questions
Adobe Commerce vs. Salesforce Commerce Cloud: which is better?
These interviews do not establish one as better. Adobe Commerce praise concentrates around what buyers can build on it — “super flexible”, “you can do whatever you want to do” — and around how easy the skills are to hire: four of its thirty-three high raters name the size of the Magento developer pool as a reason to stay, and no Salesforce Commerce Cloud buyer in this set raises developer availability at all. Salesforce Commerce Cloud praise concentrates around arriving configured and connected — a “globally scalable platform”, “out-of-the-box integrations, integration APIs available”, and “a lot less custom work than what we used to have to do”. The complaints expose the tradeoff on each side. Adobe Commerce's lower raters describe the development the platform asks for and what it costs to change anything; Salesforce Commerce Cloud's describe the boundary of what they can change and the cost of operating inside it.
Is Adobe Commerce harder to maintain than Salesforce Commerce Cloud?
Buyers on both platforms describe maintenance as real work, and they describe different work. On Adobe Commerce it is code: buyers report needing to “back patch” customized sections after security updates, describe upgrades that require significant re-work of the existing custom code, and one says that with enough customization “we fix one thing and something else breaks”. On Salesforce Commerce Cloud it is throughput: buyers describe needing a specific headcount to manage the backend, a resulting “backlog”, and significant SI work. Neither set is small, and these interviews do not measure hours, so the honest comparison is the kind of maintenance rather than the amount.
Why do buyers migrate from Magento to Salesforce Commerce Cloud?
Several accounts in this set describe that move, and the reasons they give are consistency and pace rather than a missing feature: one describes the platform it left as “a dinosaur… conceived in another age”. What the interviews do not show is that these two are mainly weighed against each other. Shopify is the platform named most often by buyers on both sides — in eighteen of Adobe Commerce's sixty-three lower raters and twenty-six of Salesforce Commerce Cloud's one hundred and thirty-one — so the alternative most present in this commentary is a third platform, not the other one on this page.
Which is more customizable, Adobe Commerce or Salesforce Commerce Cloud?
Buyers use the word in opposite directions, and they use it about each other. An Adobe Commerce buyer reports “some customization issues which are not that flexible compared to Salesforce”, while a Salesforce Commerce Cloud buyer calls it “a little clunky and not very flexible” specifically when compared to other platforms like Magento and Shopify. The two are describing different things. On Adobe Commerce, flexibility means the code is open and a developer can change it — one buyer says Adobe products are “made for you to be able to mold them to what you need”, and counts that among both the best and the worst things about them. On Salesforce Commerce Cloud it means configuring inside the platform, which is faster where it reaches and stops where it does: buyers describe it as “pretty boxed in” with “very little variation in what's out of the box”, while another says it has “really made good on that promise for maximal flexibility”.
See which one fits your exact stack
Re-platforming, or deciding whether to stay? Do a 15-minute interview about your stack and get this personalized — what your team can realistically change without developers, and what each platform would put in front of you.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.