HubSpot migration from Salesforce, Dynamics, Zoho, Pipedrive or spreadsheets
We move CRMs to HubSpot as a HubSpot Platinum Solutions Partner, with a signed field map, a test run on a copy of your data, a quiet-day switchover and training by role. Pick the system you are leaving below to see what moves and what has to be rebuilt.
Free, 30 minutes, and you'll leave with at least one clear next step.
How do you choose a migration path?
Start with the system you are leaving, because that sets most of the work. A move from Salesforce or Dynamics 365 usually carries custom objects, years of activity history and automations that need rebuilding. A move from Zoho depends on which other Zoho apps stay connected. Pipedrive moves turn on export rules and merging pipelines, and spreadsheet moves on cleanup.
The second choice is how the data travels. HubSpot's Smart Transfer tool handles standard records for several of these systems. Custom objects go through HubSpot's API, and automations and reports get rebuilt by hand.
The third choice is timing. Most teams switch in one planned cutover after a full test. Teams whose accounting or support apps can't stop sometimes run HubSpot next to the old system and switch once everything checks out.
Still deciding? Our comparison pages show where HubSpot fits. Ready to plan? The Salesforce to HubSpot migration checklist lists what to gather, and most of it applies to any starting system.
What moves to HubSpot, and what doesn't?
Comes across as data
- Contacts, companies and deals, with their owners, stages and amounts
- Leads, as contacts or HubSpot leads, marked so you can tell them apart
- Calls, meetings, tasks and notes on each record's timeline, and products on deals as line items
- Support cases, as tickets linked to the right company and contact
- Attachments and files, in a separate pass after the main records
- Custom objects, on HubSpot Enterprise, loaded through HubSpot's API
Gets rebuilt or archived
- Automations and approval rules, rebuilt as HubSpot workflows
- Reports and dashboards, rebuilt from the list your managers actually open
- Formula fields, rebuilt as calculated properties
- Page layouts and record types, rebuilt as pipelines, views and property groups
- Roles and visibility rules, rebuilt as HubSpot teams and permissions
- Field history and old email that has no place to land, kept in an archive export
What doesn't move on its own?
Records and their history move as data, but the logic built on top of them has to be rebuilt. No tool turns a Salesforce Flow, a Dynamics plug-in, a Zoho script or a Pipedrive automation into a HubSpot workflow, so each one gets listed, checked and rebuilt by hand. It is also the moment to drop the ones that stopped mattering.
Reports work the same way. We rebuild the ones your managers open every week in HubSpot reporting and leave the rest.
Some data needs its own plan, like files stored inside Dynamics notes or email that Zoho's backup leaves out. Each system page covers these, and we settle them during the audit.
How a Push migration runs
Every move follows the same five steps, whatever system you are leaving. We never skip the test run.
Stage 1: List what you have today
We list every object, field, automation, report and connected app in the old system, and how full each field is.
We pull fill rates, find duplicate fields, check which automations still run and note every tool that reads from or writes to the old CRM, like web forms, phones, accounting or an ERP.
You get An inventory of what moves, what gets rebuilt and what stays behind.
Stage 2: Give every field a home in HubSpot
Each field gets a HubSpot property, an association, or a note saying it stays behind. You sign off before any data moves.
Dropdown values get matched one by one, and owners get matched to HubSpot users. Lookups become associations. We also add the lifecycle stage and lead source fields HubSpot reports need.
You get A field map you can read, with every decision written down.
Stage 3: Run the whole move on a copy
We move all of your data into a HubSpot test account and compare it with the old system.
We compare record counts object by object, check that files open, and have your team click through accounts they know well. We fix the map and run it again until the counts match.
You get A test report with counts, gaps and fixes.
Stage 4: Switch over on a quiet day
We take a full backup, freeze the old system, run the final move and point forms, phones and connected tools at HubSpot.
The freeze covers only the final run, planned for your quietest window. Anything entered during testing comes over in that run. The old system stays readable so anyone can look things up.
You get Your team working in HubSpot the next morning, with the backup kept with you.
Stage 5: Train each role on its own records
Short sessions for reps, managers and admins, using your pipeline and your customers.
Reps learn their daily views and tasks. Managers learn the dashboards that replaced their old reports. Admins learn how to change properties and workflows without breaking anything.
You get A team that uses HubSpot daily, plus written admin notes.
What decides how long a migration takes?
We don't quote a timeline before the audit, because the same system can mean a small move for one company and a large one for the next. These set it.
How much logic needs rebuilding. Records load quickly. Automations, approval rules and custom scripts each need to be rebuilt and tested, so a heavily automated account takes longer than a large but simple one.
Custom objects and connected systems. Every custom object needs its own design in HubSpot, and every connected tool, like an ERP or accounting app, needs to be reconnected and tested. Our ERP guide covers that part.
History and data quality. Years of activity, stored files and old email each add a pass, and messy data makes mapping take longer.
Your team's time. Someone signs off on the field map and checks records in the test run. Moves go fastest when that person has time set aside.
Check your renewal date on the old system early, so the switch lands before it. A power systems manufacturer that left Salesforce with us followed this same plan, with its ERP kept in sync through the move.
Pick the system you're leaving
Dynamics to HubSpot migration
We move Microsoft Dynamics 365 CRM data to HubSpot, rebuild Power Automate flows and keep your ERP connected. See the Dynamics pitfalls and when to stay put.
Pipedrive to HubSpot migration
Leaving Pipedrive? We move your deals, people, activities and files to HubSpot, rebuild your automations and train the team. See the limits we plan around.
Salesforce to HubSpot migration
Leaving Salesforce? We move your data to HubSpot with a signed field map, a full test run, a quiet switchover and training. See what moves and what doesn't.
Spreadsheets to HubSpot
Running sales from Excel, email and QuickBooks? We clean your sheets, set up HubSpot around how you sell, connect QuickBooks and train the team to use it daily.
Zoho to HubSpot migration
Moving off Zoho CRM? We move your records, files and custom data to HubSpot, rebuild your automations and keep the Zoho apps you still use connected to it.
Questions owners ask us first
Which systems can you move to HubSpot?
We have pages for moves from Salesforce, Dynamics 365, Zoho, Pipedrive and spreadsheets. For another CRM, bring a sample export to the first call and we'll tell you what it would take.
Can our team keep selling in the old CRM during the move?
Yes. Your team works in the old system through the audit, mapping and test run. Only the final move needs a freeze, and we plan it for an evening or weekend. Anything added during testing comes over in the final run.
Can HubSpot's own import tools handle a migration?
They handle part of it. HubSpot's Smart Transfer and import tools move standard records well, and we use them where they fit. Custom objects, automations and reports need HubSpot's API or a rebuild.
Does every migration need HubSpot Enterprise?
No. Enterprise matters when your old system has custom objects with live data, because HubSpot custom objects need an Enterprise plan. If your data fits in contacts, companies, deals and tickets, the move itself doesn't need Enterprise. The audit shows which plan your data needs before you buy.
Should we clean up our data before we migrate?
We clean it as part of the move, so you don't need a separate project first. During mapping we drop empty fields and merge duplicate ones, and duplicate records get merged before the final run.
What happens to the old CRM after the switch?
It stays readable, so anyone can look up an old record while the team settles in. You also keep a full export with files. Most teams cancel the old system after a full sales cycle in HubSpot.