Acquia alternatives buyers actually switch to

Five companies here made six completed replacements of Acquia products. Five left its customer data platform, not its Drupal CMS: to Amperity twice, Tealium with Braze, Bloomreach and Zeta. One moved the CMS to Adobe Experience Manager. On the CMS side, more buyers here chose Acquia than left it, and its customers praise speed to market and support.

Based on verified interviews with the buyers who select and operate these platforms, at DTC and enterprise brands. Buyers are anonymized before publication; vendor names and views are reported as given. No vendor paid to appear or could edit this page.

Five companies in these interviews made six completed replacements of Acquia products. Five of the moves replaced Acquia’s customer data platform, which it bought as AgilOne, and one replaced its Drupal-based CMS. A packaged-food manufacturer made two of them, moving its CDP to Amperity and its CMS to Adobe Experience Manager. The CDP and the CMS do different jobs and have different alternatives, so this page keeps them apart. It also answers what Acquia’s customers praise, which depends just as much on which product they run.

5 of 6
Completed moves off Acquia that replaced its customer data platform rather than its CMS.
7.3/10
Amperity, the destination named in two of the five customer data platform moves.
2 to 1
CMS selections that went to Acquia over Sitecore or Kentico, against one completed move off it. A selection is not a finished migration.

The alternatives, by what they are

Every destination in a completed move, grouped by the Acquia product it replaced. The five CDP moves differed in scope: one replaced the CDP outright with Amperity, one moved only identity resolution to Amperity, one split data and campaigns between Tealium and Braze, and two folded customer data together with email, personalization or messaging. The sixth replaced the Drupal-based CMS with Adobe Experience Manager. Each is an alternative for a specific job, not a substitute for every Acquia product.

WHERE YOU ARE Acquia not rated FIVE MOVES CUSTOMER DATA Amperity 7.3/10 · twice Tealium 6.9/10 · +Braze Bloomreach 7.3/10 Zeta 6.7/10 ONE MOVE CMS Adobe Experience Manager 7.2/10
Groups are the Acquia product replaced, not a ranking. Acquia carries no score because buyers rate its CMS, CDP and DAM under one name. Each alternative’s rating comes from its own buyers, not from the companies that moved.

What lower-rating Acquia buyers complain about

On the customer data platform, the complaints behind the moves are what changes cost, not being able to see inside it, and missing campaign features. On the CMS, it is the cost of keeping a mixed Drupal setup running.

Paying for every change. A luxury retailer that rated the CDP 3 says “anytime they suggest changing something it comes with a big price tag,” and that “Everything is based, I feel like, on service hours.” By its next interview it was moving off Acquia without buying another CDP, using part of Bluecore to cover what it had done there, because “the juice wasn’t worth the squeeze.” A luxury apparel brand rating it 5 says “It feels like every time we need to do something, we need to engage their development team.” A fashion group rating it 4, now evaluating Salesforce as a replacement, names “very high and opaque pricing, and the build complexity is really high.”

Not seeing inside it. An apparel retailer that left for Bloomreach says the CDP “became almost like a black box too, where what was happening underneath, nobody knew.”

Campaign and journey gaps. A premium apparel brand that ran campaigns from the CDP rated it 5 because “plenty of things were missing with Acquia,” chiefly flexibility across the customer journey. A year later, mid-migration, it said of the analytics that Acquia has “to really work on that heavily.” That describes this company’s setup at the time; Acquia’s CDP page currently lists a machine-learning add-on.

On the CMS, upkeep. The one company that left the CMS ran it alongside its own Drupal and in-house tools, and says “We had to move away from it because we were investing so much in keeping the lights on.” A professional association still on Acquia, rating it 6, says “it’s not necessarily particularly stable” and that Drupal “developer skills are quite hard to find.”

That's the average buyer. How does your stack measure up?A free, peer-powered read of your tech stack, with a shortlist and your next steps.
Get my stack read →

Where buyers go when they leave Acquia

Six completed replacements across five companies, judged by each company’s latest interview. The packaged-food manufacturer made two of them: Acquia CDP to Amperity and Acquia CMS to Adobe Experience Manager. Two other CDP moves also took over campaigns or messaging that sat in separate systems, so the destinations below replaced different scopes of work, not six equivalent platforms.

Customer data platform

Amperity
7.3/10 · two companies

A packaged-food company ran an RFP after consolidating on Acquia and chose Amperity: “In comparison to where we were with Acquia, it’s almost night and day.” In 2023 an apparel retailer that was “on AgileOne” tested identity-resolution match rates on sample data and moved that job to Amperity; it did not describe replacing its other CDP functions. Later interviews at the company do not name Amperity, so the move is documented but continued use is not.

Tealium vs. Amperity →

Tealium, with Braze
6.9/10 and 7.5/10 · one company

The premium apparel brand split Acquia’s job in two: Tealium for customer data, Braze for campaigns. The move was finished by early 2026. It calls Braze’s “support, implementation, testing, hypercare, way better than Acquia,” and later said “Tealium CDP again is super good.” Salesforce and Braze announced a definitive agreement for Salesforce to acquire Braze on October 20, 2026; it had not closed when this page was updated.

Tealium vs. Segment →

Bloomreach
7.3/10 · one company

The apparel retailer wanted customer data, site personalization and email in one tool: “this could be an opportunity for us to just use this tool, replace all these things and have one solid tool in place.” A year later it runs Bloomreach for its customer data, email and on-site recommendations.

Klaviyo vs. Bloomreach →

Zeta
6.7/10 · one company

A discount retailer moved work done in Acquia and Salesforce onto Zeta, which by mid-2024 served as its CDP and sent its email and SMS. The interviewee says “I wasn’t a part of that decision making team” and understood the move as “bringing together more disparate systems into one system,” so the account shows the result more than how Zeta was chosen.

No head-to-head published yet

Content management

Adobe Experience Manager
7.2/10 · one company

The packaged-food company moved its site from Drupal, in-house tools and Acquia CMS to a “more plug-and-play model,” and a year after launch says “It has been phenomenal since the switch.”

Adobe Experience Manager vs. Contentful →

Three companies are not counted above. The luxury retailer was moving off without a replacement CDP. The fashion group is evaluating Salesforce, which is an open evaluation. And a consumer-health company that rates the CDP 6 reconsidered and stayed: it is “Not actively considering alternatives,” and gives cost as the reason.

What do customers praise most about Acquia?

It depends on the product. CMS customers praise speed, support and the contract model. CDP customers praise having their customer data in one place. DAM customers praise metadata and the vendor’s user community.

CMS: shipping fast, and support when it breaks. A life-sciences company rating it 9 says “the time to go to market with the features and functionality is so quick,” and that when something goes down, “the whole Acquia team kind of jumps in.” It also likes paying for the traffic it gets: “You don’t have to pay for 4 million visitors every year if you’re not getting 4 million visitors.” Acquia’s Cloud Platform documentation defines Views as any requests made to your Acquia-hosted Drupal application, excluding static content, redirects and client errors, and a Visit as one or more Views from the same user agent within the same hour. Those are not the page loads an analytics tool counts, and Acquia bills on Views and Visits, not on the numbers in other analytics tools. Subscribers get an extra 30% headroom above their entitlement before any overages apply; past that, the documentation lists temporarily or permanently upgrading the Traffic Entitlement, or paying a one-time overage fee. What a company pays depends on its contract. Its one wish is “more connectors, better connectors to other third-party tools.” A professional association values that “It shows our authoring team what they see before they publish.”

The Drupal base cuts both ways. An industrial equipment company choosing Acquia counted it as a reason to buy: “Acquia is built on top of Drupal, which is an open source platform that has a lot of active development and developers working on it and improving it.” The professional association names the same base as a weakness, because Drupal developers are hard to hire.

CDP: data in one place, answers fast. A home-improvement retailer that rates it 9, after what it calls a bumpy implementation, says analytical requests “could have taken us like two weeks. And with them, with the CDP, half an hour we’re getting it,” and that Acquia wants “to be a true partner much more than just a simple vendor.” The consumer-health company says “It really does a great job of appending customer information from a bunch of different sources and bringing them into one platform.” A specialty retailer with stores calls it the place “where all our data lives. It’s ultimately our source of truth.”

DAM: metadata and community. A home-products manufacturer rating Acquia DAM 10 credits “a very flexible metadata structure” and an API that sends new asset versions to its PIM. A wine producer rating it 8 singles out “the amount of user group sessions that they host,” with Acquia staff on the calls.

Want your own stack read the same way?

Get mine →

What did buyers choose instead of Acquia?

Several buyers evaluated Acquia and picked something else, which is a different signal from leaving it. A large healthcare company ran a proof of concept on Acquia and did not select it: “We didn’t find them promising,” with the gap in what it calls data solution capabilities. A live-entertainment company evaluated Acquia and chose Salesforce to build on an existing relationship. An online retailer had Acquia “definitely in the running” and chose Blueshift for having more in the box. On the DAM side, a beauty group chose Censhare for having PIM and DAM in one product, a food manufacturer ranked Bynder first ahead of Acquia, and a nonprofit chose Aprimo.

On the CMS, more of the decisions here went toward Acquia than away from it, though a selection and a completed migration are different outcomes. A professional association completed its move from Sitecore and has run Acquia for two years, having chosen it “because it was a better price, more scalable, more modern.” An industrial equipment company selected Acquia to replace Kentico after weighing Adobe Experience Manager and Sitecore; when interviewed in January 2026, its migration was still planned. Against those, the packaged-food manufacturer completed its move from Acquia CMS to Adobe Experience Manager. These are the decisions in these interviews, not a measure of CMS market share or churn. The head-to-head is in Sitecore vs. Acquia, and the moves off Sitecore are in Sitecore alternatives.

When does staying on Acquia make sense?

Some buyers who weighed leaving stayed. A manufacturer rates Acquia DAM 6 to 7 across its interviews and says “It doesn’t innovate very much in my opinion,” but will not replace it: “there are too many people who use Acquia internally in all of our brands, and they’re used to it.” It plans to put a second tool beside it for finished assets instead. The consumer-health company stayed on the CDP on cost, and the home-improvement retailer is a satisfied customer.

Our read, not a buyer’s, is that Acquia alternatives is up to three separate decisions: the CDP, the CMS and the DAM. List which Acquia products you run, the work each does, the integrations that depend on it and what it costs to maintain; the packaged-food manufacturer picked a different vendor for each product it replaced. For all three, compare the first quote with the ongoing work, price professional services and staffing as their own lines, check what history you can take with you, and do not assume a new vendor is cheaper to run.

For the CDP, test identity resolution, profile accuracy, data access and audience building on your own data, and how audiences reach your campaign tools. Note which workflows now depend on the vendor’s professional services, since that is where the complaints here sit, and decide whether email, SMS or personalization move with it.

For the CMS, run your real authoring workflow, content migration, integrations and deployment through each candidate, weigh Drupal developer availability against the skills the replacement needs, and keep migration cost apart from what hosting, support and ongoing development cost afterward. For the DAM, check metadata structure, search, versioning, rights and the PIM and publishing integrations: a replacement that stores the files but loses the metadata and workflows adds work.

Two things this page does not show. Six moves is not a churn rate for Acquia, and the alternatives’ ratings come from their own buyers, so they do not show how these companies fared after switching.

Common questions

Why do buyers leave Acquia?

On the customer data platform, the buyers who left or are leaving describe paying for professional services to make changes, not being able to see what the platform was doing, and gaps in campaign and journey features. The one company here that left the CMS was running Acquia alongside its own Drupal and in-house tools, and moved because keeping that setup running took too much investment.

What do buyers replace Acquia with?

Five companies here made six completed replacements. Five replaced Acquia’s customer data platform: Amperity twice, once only for identity resolution, Tealium with Braze for campaigns, Bloomreach, and Zeta. One replaced the CMS with Adobe Experience Manager, made by a packaged-food manufacturer that also moved its CDP to Amperity. Amperity and Bloomreach rate 7.3/10, Adobe Experience Manager 7.2/10, Tealium 6.9/10 and Zeta 6.7/10, each among its own buyers.

What do customers praise most about Acquia?

It depends on the product. CMS customers praise how quickly they can ship site features, the support when something breaks, and a contract that charges for the traffic they actually get. Customer data platform users praise having data from many sources in one place and getting answers to analytical questions quickly. DAM users praise flexible metadata, the API and the user-group sessions.

Is Acquia a CMS or a CDP?

Both, and a DAM as well. Acquia sells a Drupal-based CMS and hosting, a customer data platform that came from its 2019 agreement to acquire AgilOne, and a DAM that came from Widen, announced in 2021. Buyers often say just “Acquia” for whichever one they run, so a question about Acquia alternatives needs to start with which product.

Should we replace Acquia’s CDP and CMS together?

The interviews show them replaced separately. The one company here that left both moved its customer data to Amperity and its site to Adobe Experience Manager, and the other four that left replaced only the customer data platform. Our view, not a buyer’s, is to treat them as two decisions with two shortlists.

Your stack, read by the buyers who've run it

Peer-powered: built from hundreds of verified buyer interviews, and fitted to the tools you already run. You get a shortlist for your stack and your next steps.

Get my stack read

Free · no password · your answers are anonymized before they inform research like this.

Want to come back to this?We'll email you a link to this page, so it's easy to find later or forward to your team.
Methodology. Alium conducts verified interviews with software buyers — the people who select and operate these platforms. This page reports where buyers who left Acquia went, what its users praise and criticize, and how the alternatives rate across the corpus. A move counts only where the buyer confirms in the interview that an Acquia product was retired or replaced, judged by the company’s latest interview; exits still under way, open evaluations and moves at a previous employer are reported separately and not counted. Buyers rate Acquia’s CMS, customer data platform and DAM under one product name, so no single Acquia rating is shown. Ratings are buyer-satisfaction averages from published transcripts, re-verified when a page is built; figures from fewer than 25 ratings are rounded. Buyer identities are verified at interview time and anonymized before publication; vendor names and ratings are reported as given. No vendor paid to appear or was able to edit this page.