"It depends. Book a call."
That's the answer almost every HubSpot partner gives when someone asks what a Salesforce migration costs. I've given it myself for years. It's true, and it's also a terrible answer, because the prospect already has a number in their head, and if nobody offers a better one, the imaginary number wins.
So I built a calculator and put it on our site. Visible assumptions, visible math, a first-year total you can get without talking to anyone. Here's what goes into it, and what deliberately doesn't.
Most people price a migration by comparing the Salesforce invoice to the HubSpot quote. That difference is real, and it's usually the smallest of the numbers that matter.
Contract overlap. If you have 14 months left on Salesforce and 9 on Marketo, you'll pay for two stacks while you build and cut over. Months remaining on your current contracts is one of the first things the calculator asks, because overlap quietly decides whether a migration makes sense this year or next.
The build. A migration isn't an export-import job. Each hub you stand up is its own implementation: sales process, marketing assets, service workflows, CPQ if you quote. The calculator prices each major workstream at $25K as a planning assumption, with the legacy data migration itself as its own line. Complex portals cost more. The point is that zero is never the number.
Integrations. Everything connected to Salesforce today has to keep working after the move. The calculator assumes roughly $2.5K to implement a marketplace connector and $10K for a custom build. And a warning straight from the calculator page: "A marketplace connector existing doesn't always mean it does what you need. Field coverage, sync direction and frequency all vary."
There's a fourth cost: the productivity dip while your team relearns everything. We left it out of the calculator on purpose. It's real, but we have no honest way to size it, and anyone who quotes you a precise figure for it is guessing.
You can't price the dip, but you can manage it. Time your go-live so the team gets a full month of real, daily use before any long break. A system people worked in for four straight weeks survives the holidays. A system launched a week before everyone disappears gets relearned from zero in January.
One more honest limit: the calculator won't tell you whether you should migrate at all. Sometimes fixing the Salesforce instance you already own is the right answer. That's a strategy conversation, not a form field.
Two reasons.
First, fantasy quotes waste everyone's time. If your gut says one number and the math says four times that, better to learn it in five minutes on a web page than after three discovery calls.
Second, and this is the one other partners push back on: services buyers shop on fear of failure at least as much as on price. They're worried the project blows up, the timeline drags, and their name is attached to it. Showing your cost math before the first call is the first piece of evidence the project won't surprise them later.
A word on HubSpot's own onboarding, because it comes up in almost every migration conversation. For a straightforward portal, it's fine, and I'd tell you to take it. For an upmarket migration with custom objects, an ERP in the mix, and integrations that have to work on day one, standard onboarding was never designed to carry that load. That gap is where migrations go wrong, and it's why the build numbers above exist.
The calculator is live: Salesforce to HubSpot Migration Cost Calculator. Every figure is non-binding and no substitute for proper scoping. Run your numbers, then tell me which one looks wrong. That's how it gets better.