The short answer: a Salesforce to HubSpot migration works best in phases. You audit what's in Salesforce, design how HubSpot should be set up, clean and map the data, migrate and test, and only then switch the team over. Automation and reports are rebuilt in HubSpot rather than copied. You can do it with HubSpot, with a HubSpot Solutions Partner, or as a mix of both.
Businesses usually leave Salesforce for the same few reasons. It's become expensive for what the team actually uses. Every change needs an admin or a consultant. And sales and marketing still don't share one clear view of the customer.
HubSpot solves a lot of that, but only if the move is planned. Here's how to approach it.
Most Salesforce orgs have years of customisation layered on top of each other. Before planning the move, take stock of:
This audit usually shows that a large share of the setup can be simplified or left behind.
Resist the urge to rebuild Salesforce inside HubSpot. Instead, map your current sales and service process and set HubSpot up for that: pipelines, deal stages, lifecycle stages, properties and permissions. The migration then fills that structure.
A few things work differently and need a decision up front:
Merge duplicates, standardise values like states and countries, and archive dead records before anything moves. Then map every field you're keeping to a HubSpot property, including dropdown values, owners and record associations.
HubSpot recommends a phased migration that keeps both systems running during the transition, and its own Salesforce integration can help with mapping and moving records. More complex or heavily customised data may need HubSpot's APIs or a migration specialist.
Whichever method you use, migrate a sample first and have the people who will use HubSpot every day check it before the full move.
Salesforce flows don't convert into HubSpot workflows automatically. Document what each one does, decide if it's still needed, then rebuild it properly. Do the same with reports: list the ones people actually use, consolidate them, and rebuild them in HubSpot.
Set a firm date when Salesforce becomes read-only. Train the team before that date, not after, and make sure someone is on hand to answer questions in the first few weeks. Our guide to getting your team to actually use HubSpot covers this in more detail.
HubSpot offers HubSpot-led, partner-led and hybrid migrations. Working with a local HubSpot Solutions Partner gives you someone who understands both platforms, works in your time zone, and stays involved after go-live to help with adoption, reporting and integrations.
When comparing options, ask who will do the hands-on work, how data will be tested, what happens to your integrations, and what support looks like once you've switched.
It depends on how much data and customisation you have and how involved your team can be. HubSpot says most businesses complete the move within about three months.
Not always, but it can help. HubSpot's Salesforce integration needs a Professional or Enterprise HubSpot subscription and a Salesforce edition with API access, or Salesforce Professional. Some migrations use imports or migration tools instead.
Yes, for a short, planned period. Running both for too long creates confusion about which system is right, so set a clear cutover date.
Foundry 11 is a HubSpot Solutions Partner working with businesses across Australia and New Zealand. If you're thinking about moving from Salesforce, get in touch and we'll talk through what the migration would look like for you.