
Short answer: There are three real options, not one. Migrate fully to HubSpot, run HubSpot alongside Salesforce with a proper sync, or start a clean HubSpot portal for one part of the business and leave the rest. A full migration with us starts at £9,500, $12,000 or €11,000, fixed after a source audit. The right answer depends on whether Salesforce is your company-wide system of record, how much custom code runs your process, and when your Salesforce contract ends.
I’ve had a lot of Salesforce conversations this year. The interesting thing is how few of them ended in a straight “move everything to HubSpot” project.
The three options
| Option | When it fits | What it involves |
|---|---|---|
| Full migration | HubSpot will become the system of record for sales | Audit, mapping, test run, cutover, Salesforce switched off |
| Run both, synced | Salesforce stays the company-wide record (finance, ops, other teams) | HubSpot for marketing and maybe sales, Salesforce as master, a sync designed properly |
| Clean HubSpot for one team | One business line needs to move fast, the rest can wait | A new portal, a small API sync for a handful of fields, no history migrated |
Full migration
The simple ones really are simple. One founder told me he’d moved his pipeline and contacts himself on a Sunday afternoon and found HubSpot “a hundred times easier”. He had a small team, no custom objects and very little automation.
The ones that need a partner have years of custom objects, Flows, Apex, validation rules and integrations. That’s where the cost is, and it’s nearly all in the rebuild, not the data.
Run both, synced
This is more common than people think. At my previous agency, which I founded and grew into the UK’s largest HubSpot partner, we ran HubSpot alongside Salesforce as the master CRM for Elliptic, a fintech compliance company, with a new website and an SEO, content and paid programme on top. Web sessions grew 220% and contacts 315% year on year, while Salesforce stayed the master.
The catch is that the native sync has quirks, and they show up in reporting. One US healthcare business I’m working with has Salesforce opportunities and HubSpot deals connected, but the contacts on each opportunity weren’t associated. So HubSpot couldn’t see who was involved in a deal, and attribution from ads to revenue broke. The fix is designing the sync around the reporting you need, not just switching it on.
Clean HubSpot for one team
A US legal services firm needed a new HubSpot instance live by a hard cutover date. Their Salesforce used a custom “Intake” object instead of opportunities, so the native sync couldn’t map it. We built a clean portal with Deals renamed to “Intake”, two custom objects for the case details, and an API sync of just four to six fields back to Salesforce. No history migrated, because company changes meant the old data was about to become irrelevant anyway.
It went live on time. That’s a valid migration strategy: don’t move what you won’t use.
When not to leave Salesforce
- Your company runs on custom code. If core operations depend on Apex and complex Flows, price the rebuild honestly first.
- Salesforce is the system of record for finance and operations. Keep it, and make the sync work.
- The setup is the problem, not the tool. Messy data and an unclear process move with you. An audit tells you which it is.
What actually moves
| Moves cleanly | Needs planning | Gets rebuilt |
|---|---|---|
| Leads and contacts | Activity history and attachments | Flows and Apex logic |
| Accounts as companies | Custom objects and their relationships | Validation rules |
| Opportunities as deals | Record types (usually become pipelines or properties) | Reports and dashboards |
| Owners, products and line items | Campaign history | Approval processes |
Statuses rarely map one to one. In the legal firm’s case, Salesforce statuses arrive in HubSpot as text and a separate HubSpot stage drives reporting. That’s fine, as long as it’s designed up front rather than found at go-live.
The parts people underestimate
Custom objects. HubSpot supports them, but they need Enterprise and they should be designed for how you’ll report, not copied from Salesforce. Often a renamed standard object does the job.
The rebuild. Automation, validation and reports are rebuilt by hand. This is a chance to cut what nobody uses, which is usually a lot.
Licences. HubSpot’s pricing changed in October 2026 for new EMEA customers (per seat, plus monthly credits). Model the real seat count, not your Salesforce user list. See what HubSpot licences really cost.
Your Salesforce contract end date. The single biggest driver of the timeline. Start too late and you’ll pay for both, or renew the system you’re leaving. Find the end date and notice period before you ask anyone for a quote.
Adoption. Salesforce users are used to a certain way of working. Training on your own portal, with the changes explained, matters more than the data move. More in getting your team to use HubSpot.
How a full migration runs
- Source audit. What’s in Salesforce, what’s used, what’s dead, and what’s custom.
- Mapping. Every object and field, agreed in writing, including how statuses and record types land.
- Build. HubSpot built to the design, automation rebuilt and simplified.
- Test migration. A full run into a sandbox, checked by your team.
- Cutover. A short data-entry freeze in Salesforce, the final move, validation, training.
We prefer a clean cutover over long parallel running. Two systems both being edited is how records go missing.
What it costs
A full Salesforce to HubSpot migration with us starts at £9,500, $12,000 or €11,000, fixed after the source audit. The “clean HubSpot for one team” route is often cheaper, because nothing historical moves. A sync redesign is scoped on its own. HubSpot licences are always separate. Full breakdown in how much a HubSpot migration costs.
Frequently asked questions
How much does a Salesforce to HubSpot migration cost? With Imagine Growth, from £9,500, $12,000 or €11,000, fixed after a source audit. HubSpot licences are separate.
Should we migrate from Salesforce or run both? If Salesforce is your company-wide system of record and isn’t changing, run both with a properly designed sync. If HubSpot will become the system of record for sales, migrate.
Do Salesforce Flows and Apex migrate to HubSpot? No. Automation is rebuilt in HubSpot, which is a chance to simplify it.
Can HubSpot handle Salesforce custom objects? HubSpot supports custom objects on Enterprise. Often a renamed standard object, such as Deals renamed to Intake, does the same job more simply.
Do we have to migrate all our Salesforce history? No. Move what someone will use or report on. Old history can stay as an archive, and sometimes a clean portal with no history is the right call.
How long does a Salesforce to HubSpot migration take? It depends on custom objects, automation and integrations, and is driven by your Salesforce contract end date. The source audit sets a fixed plan and cutover date.
Next: how much a HubSpot migration costs, or how we run a HubSpot migration.


