I get the same call about once a quarter.

“We’re moving off Marketo.” Or HubSpot. Or Pardot. Or some hybrid Frankenstack the last marketing ops person stitched together before they left.

The conversation always opens the same way. A feature complaint. We don’t have nested workflows. The forms don’t render on mobile. The reporting is broken. Sales says the leads are bad.

And the conversation almost always ends the same way. The feature complaint isn’t why you’re switching.

After running a few hundred of these conversations across our consulting practice, four patterns keep showing up. None of them are about the tool.

 

Pattern 1: Cost pressure after a growth-stage shift

A 50-person retail-media SaaS came to me last summer. Post-acquisition. On HubSpot Starter. Trying to consolidate Clearbit, LinkedIn Sales Navigator, ad spend, and a half-built attribution model into a single source of truth. They’d inherited the setup from a contractor who left. The CEO’s exact words: “I don’t want to spend three months trying to figure this shit out.”

That’s not a Marketo-vs-HubSpot question. That’s a stage-of-business question. Around 100 employees, the platform you bought at 20 stops working. Not because it broke. Because your operating complexity caught up.

 

Pattern 2: An acquisition or org event that exposes the seams

Late last year I scoped a project for an EV company that had just been acquired. Their Marketo instance had 30 forms, no global double-opt-in, no preference center, mobile templates that were going to need custom code. The acquiring entity wanted compliance and consistency by Q1.

The replacement question wasn’t “is Marketo good enough?” It was “can we hit a Q1 deadline working with what we have, or do we cut over?”

Different question entirely.

I always insist on a health check first. Always. Because replacing the platform without auditing the data and processes underneath is how you ship the same problems into a new tool, six months and seven figures later.

 

Pattern 3: A personnel gap

A healthcare staffing director told me last spring her team was leaving Marketo. Her words were sharp. “Putting a Band-Aid on a bullet hole, fixing all my problems with a bunch of different tools.”

Underneath the complaint was the actual driver. Her last admin had left. The second one didn’t have the depth. She couldn’t get HR alignment on hiring a third.

Marketo wasn’t the problem. The depth-of-bench was. HubSpot would arrive with the same depth gap, just papered over with friendlier UX for a quarter.

If you’re switching MAPs because you can’t staff your current MAP, switch your hiring strategy first.

 

Pattern 4: The fantasy of “one source of truth”

This is the most common driver, and the most seductive. Every company hits a moment where they look at their stack (MAP, CRM, data enrichment, sales engagement, attribution, BI, tag management, customer data, ABM platform) and decide the answer is consolidation.

Sometimes it is. Sometimes it isn’t.

The honest assessment is whether your current fragmentation is a tool problem (real, fixable with consolidation) or a data-model problem (will follow you into the new tool).

I’ve watched companies migrate from Marketo to HubSpot, six months later still complaining about the same lead routing issues, the same attribution gaps, the same sales-marketing alignment friction. Because the data model was broken upstream of the MAP, and the MAP wasn’t the upstream cause.

 

The health check before the cutover

If you’re considering a marketing automation replacement, here’s the work. Before the RFP. Before the demos. Before the budget approval.

Audit the data model. Lead, contact, account. Required fields. Source-of-truth rules. Sync logic with CRM. Most of the migration pain is here.

Audit the process flow. What’s the actual lifecycle stage progression? Who owns each transition? Where do leads get stuck?

Audit the people. Who runs the platform today? Will they survive the migration? Do you have bench depth, or are you hoping the new tool’s UX papers over the gap?

Audit the content debt. Templates, nurture flows, scoring models. How much of this gets ported, how much gets rebuilt?

If those four come back clean, then shop platforms. If any of them come back broken, fix them first. They’re going to break the next platform too.

The pattern across all four drivers: the MAP is rarely the cause of the pain. It’s the surface where pre-existing pain becomes visible.

Replace the MAP after you’ve replaced the underlying problem. Not before.