Salesforce to HubSpot migration: simplifying without losing what works
Companies move from Salesforce to HubSpot to get a system the team will actually use and administer. The risk is carrying years of unused fields and automation across with you.
A Salesforce to HubSpot migration moves accounts, contacts, leads, opportunities and activities into HubSpot companies, contacts, deals and timeline activity, and rebuilds only the automation and reporting that is still used. Leads and contacts merge into one contact record, record types become pipelines or properties, and custom objects need checking against what your HubSpot plan supports. The first step is an audit of what to leave behind.
Salesforce
HubSpot
Slack
QuickBooks
NetSuite
Zapier
Where the numbers come from
These counts come straight from the lists on this page. Nothing here is a survey result or a client outcome.
What should you leave behind?
Anything nobody has used in a year, and anything that exists only to work around a limit you no longer have.
- Fields with no data or no recent edits.
- Automation that fires on processes the company has dropped.
- Reports and dashboards with no recent views.
- Old leads that will never be worked; archive them instead.
What does not map cleanly?
Lead and contact separation, record types, complex permission models and heavily customised objects.
- Leads and contacts become one contact with a lifecycle stage.
- Record types become pipelines, properties or teams.
- Fine-grained sharing rules need rethinking as teams and permissions.
- Custom code has no direct equivalent; check whether the need still exists.
When is the move the wrong decision?
When the business depends on Salesforce features HubSpot does not match on your plan, or when the real problem is an untidy org and not the platform.
- Complex quoting, territory or partner processes built deep into Salesforce.
- Many custom objects with their own automation.
- A clean-up and better administration would solve the complaints.
Compare on your own processes. Features and plan limits change; confirm them in the vendors' own documentation.
Questions buyers ask about this
Will reps lose their history?
No. Activities load onto the contact, company and deal timelines, and files can be attached. Decide how far back to bring.
When should we time the move?
Work back from your Salesforce renewal date, leaving time to run read-only for a period, and avoid quarter end.
Can HubSpot handle our custom objects?
HubSpot supports custom objects on some plans. We check your objects against the plan before the design is fixed.
Are you a HubSpot or Salesforce partner?
We are an independent consultancy. This page is not published or endorsed by HubSpot or Salesforce.
Vendor documentation to check against
Product details, plans and pricing change. Confirm current details in each vendor's own documentation. Consultants in a Box is a Make partner and otherwise an independent consultancy; this page is not published or endorsed by any vendor named. Names and logos are trademarks of their owners.
Go deeper on our site
Related solutions
HubSpot to Salesforce migration
The records move easily. What takes thought is the model: Salesforce separates leads from contacts and expects accounts, and the automations and reports have to be rebuilt, not copied.
See the pageRevOps consulting
When marketing, sales and customer success each keep their own numbers, every meeting starts with an argument about whose are right. Revenue operations fixes the definitions, the data and the hand-offs.
See the pageAPI integration services
Two systems that do not share data cost you every day in re-typing, mismatched records and reports nobody trusts. An integration fixes that once, if it is built to survive change.
See the pageAll solutions
AI, automation and integration, ERP and CRM, data and analytics, and leadership.
See the hubWant to talk this project through?
Book a call and we will look at your systems, what the work involves and what it should cost. Or start with the free business analysis.
