
Short answer: A migration to HubSpot with us starts at £9,500, $12,000 or €11,000, fixed after a source audit, once we know what’s worth moving. The price is set by your data model (especially custom objects), how much history you need, how many integrations have to be rebuilt, and how clean the data is. Records move. Automation gets rebuilt. And integrations to finance or ERP systems need a clear rule for which system owns which data, decided before anything is switched on.
Most of the migrations we’re asked about aren’t simple “export from A, import to B” jobs. This year alone we’ve scoped moves from Salesforce, Zendesk Sell, Zendesk Support, a ten-year-old QuickBase build, and a Copper and Airtable setup held together with custom code.
They all have the same shape. And they all go wrong in the same places.
What a migration actually costs
| Item | Typical cost | Notes |
|---|---|---|
| Source audit | Included in our migration fee | What you have, what’s used, what’s dead |
| Migration (mapping, test run, cutover, validation, training) | From £9,500 / $12,000 / €11,000 | Fixed after the audit |
| Process redesign | Scoped separately where needed | Where the old system forced bad habits |
| HubSpot licences | Paid to HubSpot | Separate, in your name |
| Old system overlap | Whatever your contract says | Check the end date and notice period first |
The fixed price covers mapping, a test migration into a sandbox, cutover, validation and training on the new portal. We fix it after the audit rather than before, because quoting a migration you haven’t looked at is guessing, and guesses get padded.
What moves, what needs planning, what gets rebuilt
| Moves cleanly | Needs planning | Gets rebuilt |
|---|---|---|
| Contacts, companies, deals | Activity history (emails, notes, calls) | Workflows and automation |
| Owners and teams | Custom objects and their associations | Validation rules and required fields |
| Products and line items | Attachments and documents | Reports and dashboards |
| Basic properties | Lead objects that don’t map to HubSpot’s model | Integrations and middleware flows |
Automation never migrates. No tool on the market copies a Salesforce Flow or a Zendesk trigger into a HubSpot workflow and has it work. Treat the rebuild as a chance to simplify. Most of the automation we audit is either dead or duplicating something else.
The five things that decide whether a migration goes well
1. The data model doesn’t match
Every CRM shapes data slightly differently. Some examples from real scoping calls this year:
- Zendesk Sell uses a lead record that becomes a contact and a deal when it converts. HubSpot doesn’t, so thousands of leads need splitting into the right objects, with the uncertain ones held back for review.
- Salesforce orgs often use custom objects instead of Opportunities. One firm we work with used a custom “Intake” object. In HubSpot we renamed Deals to “Intake” and kept two custom objects hanging off it, rather than rebuilding everything custom.
- Old all-in-one tools (QuickBase, Airtable, home-grown databases) often hold contracts, projects and revenue timing that a CRM normally wouldn’t. Those need a decision: custom object in HubSpot, or stays in a finance system?
Get this design agreed in writing before a single record moves.
2. History: how much do you really need?
“Bring everything” sounds safe and is usually expensive. One buyer this year wanted around 200,000 internal notes moved, which is fine, but also 13 to 14 GB of documents that were already stored in SharePoint. Linking to the existing documents was cheaper and better.
Ask three questions about every kind of history:
- Will someone look this up in the next year?
- Does it feed a report or a compliance need?
- Can it live as a linked archive instead?
3. Duplicates and bad merges
Migrations surface every duplicate your old system was hiding. The worst ones are wrongly merged companies, where contacts and deals from two different businesses end up on one record. One prospect had subsidiaries of different large groups merged together, which then flowed downstream into their finance and project systems.
We de-duplicate and fix associations before import, not after. It’s much cheaper.
4. Fragile integrations nobody fully understands
The phrase I hear most is “a bit fragile”. Zapier zaps, Power Automate flows and custom scripts built over years by people who’ve since left. Each one needs listing, an owner, and a decision: rebuild natively in HubSpot, rebuild in middleware, or retire.
5. The cutover date
Your old system’s contract end date sets the timeline more than anything else. One help desk team was worried they’d be “slow rolled into a renewal” because nobody knew the exact date. Find it first, then work back. We prefer a clean cutover with a short data-entry freeze over running both systems in parallel.
Connecting HubSpot to your ERP or finance system
Integrations come up on almost every migration call. Here’s how we think about them.
Decide who owns what, before anything is switched on
The most common integration failure isn’t technical. It’s two systems both believing they own the customer. Write down:
- Which system creates the customer, and which one receives it
- The unique ID that links a record in both systems
- Which fields flow which way, and how often
- What happens when they disagree
One client couldn’t switch their ERP sync on at all because company names in HubSpot didn’t match the ERP. Fixing the naming and the ID came first.
Native connector, middleware or custom build?
| Option | Good for | Watch out for |
|---|---|---|
| Native connector | Standard flows, like a won deal creating a draft invoice | Limited mapping and fixed sync rules |
| Middleware | Several systems, more control, monitoring | A monthly cost and another tool to own |
| Custom API build | Unusual data models, legacy systems | Build and maintenance cost |
Xero, NetSuite and several Sage products have connectors that cover the common flows. Legacy systems without a usable API sometimes need a stepping stone, like a scheduled file export, while a proper integration is built behind it.
What finance actually wants from HubSpot
Usually not more CRM. They want to stop re-keying data and to see the whole picture. For one client we joined accounting, HubSpot and Google Workspace into a single finance dashboard delivered to Slack each month. Monthly reporting went from a full day of spreadsheet work to zero, and they saw true profit and margin for the first time. That’s written up as our self-updating finance system case study.
A sensible first finance flow: deal marked closed won in HubSpot, a draft invoice created in the finance system for someone to check and send, and payment status flowing back so sales and success can see it. Keep a human check in phase one.
How a migration runs with us
- Source audit. What you have, what’s used, what’s dead.
- Object and field mapping. Every object and field, agreed in writing.
- Process redesign. Where the old system forced bad habits.
- Test migration. A full run into a sandbox, checked by your team.
- Cutover and training. Go live, validate, train.
Your live pipeline isn’t touched until the test run checks out.
What we’ve done before
Before Imagine Growth, Rikki and Mark founded the agency that became the UK’s largest HubSpot partner. Two migrations from that time show the range:
- Kingdom Services Group consolidated several business units off Salesforce, Microsoft Dynamics, NetSuite and others onto one HubSpot portal and one website, tracking £225m of open revenue in one place.
- nShift, after an acquisition, merged two CRMs into one HubSpot and four multilingual websites into one, keeping organic traffic through the move.
At Imagine Growth, we replaced a Shopify, Klaviyo, Mailchimp and Gorgias stack for Stories Flooring with one connected HubSpot system across CRM, sales, marketing and service. That’s in our Stories Flooring case study.
When not to migrate
- The setup is the problem, not the CRM. Messy data and broken process move with you. An audit tells you which it is.
- Your old system is the company-wide system of record and isn’t changing. Fix the sync instead. Plenty of our clients run HubSpot alongside Salesforce.
- Your business runs on heavy custom code. Price the rebuild honestly before you decide.
Frequently asked questions
How much does a HubSpot migration cost? With Imagine Growth, from £9,500, $12,000 or €11,000, fixed after a source audit. HubSpot licences are separate.
What data can be migrated to HubSpot? Contacts, companies, deals, owners, products and line items move cleanly. Activity history, attachments and custom objects need planning. Automation, validation rules and reports are rebuilt.
Do workflows migrate to HubSpot? No. Automation from Salesforce, Zendesk or other tools is rebuilt in HubSpot, which is a chance to simplify it.
How do we avoid duplicates in a HubSpot migration? De-duplicate and fix company associations before import, and agree the unique ID for each object during mapping.
Can HubSpot integrate with our ERP or finance system? Yes. Xero, NetSuite and several Sage products have native connectors. Where the data model doesn’t fit, use middleware or a custom integration, and agree which system owns each piece of data first.
Should we run the old and new systems in parallel? Usually not for long. A clean cutover with a short data-entry freeze avoids records being edited in two places.
How long does a HubSpot migration take? It depends on the data model, history, integrations and your contract end date. The source audit sets a fixed plan and cutover date.
Next: the Salesforce to HubSpot guide, Zendesk to HubSpot Service Hub, or how we run a HubSpot migration.


