Ask buyers why they changed marketing automation platforms and two patterns emerge. Some replacement decisions are explained primarily by problems with the incumbent: a poor fit for the company's requirements, operational complexity, cost or persistent CRM synchronization issues. In about half of the explained moves, buyers also identify a broader organizational event, such as a suite consolidation, an acquisition, a CRM change, a contract renewal or a leadership change. These events and product complaints can overlap, and many event-associated moves involve no stated complaint about the previous platform. The moves run in every direction. Within the replacements captured in these interviews, Marketo and Eloqua have more observed departures than arrivals, while HubSpot appears frequently on both sides of a move, as companies move up from it to Salesforce or Marketo and down to it to simplify. These are directional flows within the interview set, not estimates of vendor churn, customer growth or market share. The companion reads are what marketing automation buyers wish they'd known, where the ratings live, and top complaints about marketing automation platforms.
The pressure that builds
These are the product-related reasons buyers give for reconsidering marketing automation software. Some moves are explained by these issues without a broader organizational event; in others, the same frustrations accompany a consolidation, CRM migration or other company-wide change.
Outgrown it, or the wrong shape
The pressure buyers name most, and it means different things by direction. Companies leaving Pardot describe manual work — “we were using Pardot, which is a tool provided by Salesforce, which was very manual. It offers very low personalization possibilities.” Companies leaving HubSpot describe B2C or ecommerce scale, and companies moving into Salesforce Marketing Cloud describe multi-brand journeys. Sometimes it runs the other way, and the platform was too much: “I don't think that we're there as an organization to utilize that kind of tool at this time,” one buyer says of moving off Marketo.
Named in this context: Pardot · HubSpot · Marketo · Salesforce Marketing Cloud
Too complex, and it takes specialists
Behind most moves to HubSpot and off Eloqua. “It's a very overpowered tool for the way that we use it,” one buyer says of Marketo; another remembers that “there was a longer training gap when we had someone leave the company.” A smaller number describe a platform that feels behind: “It feels like a little bit more legacy, not as nimble to things that we need.”
Named in this context: Marketo · Eloqua · HubSpot
Cost and the pricing model
Database or contact-based pricing, renewal increases, and paying for two tools at once. Some moves are simply on price — “we switched from Marketo due to better pricing.” Cost also compounds other problems: one buyer whose CRM changed would have needed a new Marketo instance, which “didn't justify the cost of the migration nor the cost of the tool,” so the company moved to HubSpot instead.
Named in this context: Marketo · HubSpot · Pardot
The sync with the CRM
The pressure that dominates moves within the Salesforce world and many of the moves off Eloqua. One buyer found that “if you change Salesforce instance to a new one, there is a lifelong sync that you can't disconnect”; another, weighing a move, wants to “remove that kind of sync friction that we have.” It cuts both ways: some companies moved to Marketo for its Salesforce sync, and some left it over the same thing.
Named in this context: Eloqua · Marketo · Pardot · HubSpot
The event that fires the decision
These are the broader events buyers associate with about half of the explained moves. They help explain when a company acts, though they often overlap with the product pressures above, and the interviews do not always establish which one caused the decision.
Consolidating onto one vendor's suite
The event buyers name most: a company standardizing on Salesforce, Adobe or HubSpot, often by directive. Most of these moves name no complaint about the old tool at all. One buyer describes who makes the call: “people making decisions of what those platforms should be aren't necessarily marketers.” Nearly half of the moves into Salesforce's marketing products follow a suite, CRM or directive decision.
Named in this context: Salesforce Marketing Cloud · Pardot · Marketo · HubSpot
An acquisition or merger
Two tech stacks meet, and one wins. “That's the merging of two tech stacks from one of our larger acquisitions from a few years ago,” one buyer explains. The result runs both ways: sometimes onto the acquirer's standard, sometimes onto the lighter tool the acquired company already ran — “Some of the smaller companies came into the merge using it, and it just sort of happened.” About half of these moves name no complaint about the tool.
Named in this context: HubSpot · Eloqua · Pardot · Marketo
A CRM change, a renewal, or a new leader
A new CRM or a new Salesforce instance reopens the marketing platform, often with sync complaints attached; one company even used a stopgap because it was “filling a gap between our license renewals with Salesforce and HubSpot.” Renewals come up in about one in ten explained moves — more than for BI tools, but still a minor stated trigger: “We're up on our contract later this year, and so I think that it was an appropriate time to evaluate if we did need to switch.” And new leaders bring their own platforms: “I'm a 13-year HubSpot user, so I came in, they were using Marketo.”
Named in this context: HubSpot · Marketo · Salesforce
Where they go
Among completed migrations and committed replacements being implemented in these interviews, HubSpot is the most frequently observed destination, followed closely by Salesforce Marketing Cloud and then Marketo; a smaller number move to ecommerce-focused email platforms, usually B2C brands leaving HubSpot. The moves run in every direction. Marketo to HubSpot outnumbers the reverse, with complexity and cost pushing towards HubSpot and Salesforce sync and customization pulling back to Marketo. HubSpot to Salesforce outnumbers the reverse too, and most moves off HubSpot go up — to Salesforce or Marketo — while companies come down to it to simplify. Eloqua to Marketo is far more common than the other way, and Pardot to HubSpot has no counterpart here. Within the counted marketing automation moves, Marketo and Eloqua show the largest net losses of observed replacements, while HubSpot receives nearly as many incoming moves as outgoing ones. Salesforce Marketing Cloud is a frequent destination, but its flows are not directly comparable, because this page includes it only when a move involves one of the marketing automation platforms being tracked. These counts describe the interview sample, not vendor-level net customer growth. The ratings for each platform are on what marketing automation buyers wish they'd known.
Want this checked against your own stack?
Start my checkup →The stories behind the switches
The counter-current: why many stay
Campaign history is the strongest anchor: “Thus far, we've stayed with Marketo because of the history of activity that we've conducted within the system.” Migration effort is the second — “it seems like it would be too complex to move our business off of Marketo and into HubSpot for right now.” Renewals can arrive before anyone is ready to move: “there's no time to migrate, we'll sign and we'll reevaluate.” Mergers freeze decisions — “Until we know what our sister companies use with our merger, we probably won't make a change there until after that point.” And some moves reverse or bring second thoughts: one company was going to switch Marketo off, “but we changed the decision on that”; another, just moved, says “if after a year we're not getting more value out of it, I would consider switching back to Salesforce”; a third asks, after leaving Marketo, “Why didn't we have these problems with Marketo, but we're having them with Klaviyo?”
What this means if you're weighing a switch
In about half of the explained marketing automation moves, buyers identify a broader organizational event alongside the replacement decision, and some of those moves involve no stated complaint about the previous platform. Other moves are explained primarily by product fit, complexity, pricing or CRM synchronization, and these pressures can also contribute when a larger initiative creates an opportunity to switch. Our recommendations, not practices buyers describe: if a CRM change or a suite consolidation is coming, decide the marketing platform as part of it rather than inheriting whatever comes with the suite; check how campaign history and reporting will carry over before committing, since that is what keeps most companies in place; test the CRM sync with your own data during the evaluation; and be clear whether you need more platform or less, since the moves in these interviews run both up and down.
Common questions
Why do companies switch marketing automation platforms?
In these interviews the pressures that build are outgrowing the platform or finding it the wrong fit, complexity that needs specialists, cost and the pricing model, and the sync with the CRM. About half of the explained moves also come with a broader event — a consolidation onto one vendor's suite, an acquisition, a CRM change, a contract renewal or a new leader — while the rest are explained by product pressures without a broader event. The two often overlap, and the interviews do not always establish which factor caused a decision.
Which marketing automation platform do companies switch to?
Among completed migrations and committed replacements being implemented in these interviews, HubSpot is the most frequently observed destination, followed closely by Salesforce Marketing Cloud and then Marketo; some companies also move to ecommerce-focused email platforms. Moves run in every direction: Marketo to HubSpot and back, HubSpot to Salesforce and back, Eloqua to Marketo. These are observed decisions, not churn rates.
Why do companies leave Marketo?
Buyers in these interviews who moved off Marketo most often describe complexity and the specialists it takes to run, cost, and a platform larger than their programme needs; smaller teams tend to move to HubSpot, while enterprises consolidating onto Salesforce move to Marketing Cloud. Others moved to Marketo for its Salesforce sync and customization, so the moves run both ways.
Why do companies move from HubSpot to Salesforce?
In these interviews moves from HubSpot to Salesforce's marketing products most often come with a Salesforce CRM rollout or a company-wide consolidation onto Salesforce, sometimes timed to the end of a HubSpot contract, and with marketing programmes that have outgrown HubSpot. Fewer companies move the other way, usually to simplify or after an acquisition brings HubSpot in.
Why do companies stay with a marketing automation platform they complain about?
Because campaign history and data are hard to carry over, migrations take time with no certain gain, renewals sometimes arrive before a migration can be done, and mergers put decisions on hold. Some companies that planned to switch reversed the decision, and a few that moved say they would consider going back.
Get a checkup on your tech stack
A physical for your marketing stack, built from hundreds of verified buyer interviews: what matters most to you, a shortlist for your stack, and your next steps.
Start my checkupFree · no password · your answers are anonymized before they inform research like this.