Salesforce to HubSpot, Done Once and Done Right

Most Salesforce projects don't fail on the data

They fail on everything around it. The records come across fine, and then nobody can find the report they used to run. The workflows were rebuilt by someone who never sat in the pipeline. The sync runs one direction and marketing stops trusting the numbers. The team quietly goes back to spreadsheets.

We've been on both sides of this — as the consultants running the project, and years earlier as the sales leader who had to live in the CRM afterward. That's the difference between moving data and building something that holds.

Three ways this usually goes

Not everyone needs to leave Salesforce. Before we recommend anything, we find out which of these you actually are.

You're migrating off Salesforce. You've decided HubSpot is the system of record and you want everything in one place — records, history, pipelines, reporting, automation. This is the most common project we run, and most of this page is about it.

You're keeping Salesforce and adding HubSpot. Maybe Salesforce is entrenched with your enterprise sales team, or ops won't move, but marketing needs what HubSpot does well. We help you choose the right HubSpot package for the job, then connect the two so both teams work from the same truth.

You already have both, and they aren't talking. Or they're technically connected and the sync is a mess — duplicate records, fields overwriting each other, lifecycle stages that don't mean anything. This is fixable, and it's usually faster than people expect.

Not sure which one you are? That's what the discovery call is for. We'll tell you honestly, including when the answer is "don't migrate."

If you're migrating: what comes across

Your records. Accounts, contacts, leads, opportunities, and activity history — including the notes, calls, and emails that give a rep context on a deal they're picking up cold.

Your custom fields and objects. Mapped deliberately, not dumped. Most Salesforce instances have accumulated fields nobody has used in three years, and a migration is the right moment to decide what earns its place.

Your pipelines and process. Stages, probabilities, and the rules your team actually sells by — rebuilt natively in HubSpot rather than forced into a Salesforce-shaped hole.

Your automation. Workflows, assignment and routing rules, sequences, and notifications.

Your reporting. This is the part most migrations shortchange. We rebuild the dashboards leadership depends on before go-live, not after someone escalates that they're missing.

Your integrations. Zapier, marketing tools, billing systems, and anything else wired into your old stack.

If you're keeping Salesforce: what a good integration looks like

A working Salesforce–HubSpot setup isn't just switching the connector on. The decisions that matter get made before anything syncs.

Which records sync, and which don't. Syncing everything is rarely right. We define inclusion rules so HubSpot gets the records it needs without importing a decade of closed-lost noise.

Which system wins. Every synced field needs an owner. Get this wrong and one system quietly overwrites the other for months before anyone notices.

What marketing hands to sales, and when. Lifecycle stages, lead status, and the handoff point between the two systems — defined as a process first, configured second.

Attribution that survives the handoff. If a lead is nurtured in HubSpot and closed in Salesforce, the revenue needs to trace back. This is where most two-system setups break down, and it's fixable.

Reporting across both. So leadership isn't reconciling two dashboards that disagree.

We work with HubSpot's native Salesforce integration where it fits, and build custom or middleware solutions where it doesn't.

How it works

1. Discovery. We get under the hood of your current setup and find out how your team really works — which is rarely how the CRM is configured. You leave with a recommendation on migrate versus integrate, a clear scope, and an honest timeline.

2. Mapping and cleanup. We map every object and field, and flag the data that shouldn't come with you. Migrating a mess just relocates it; syncing a mess duplicates it.

3. Build and test. We stand up HubSpot, rebuild your workflows and reporting, and run tests in a controlled environment so you see the result before it's live.

4. Go-live and training. We cut over or switch on the sync, then train your team — not a feature tour, but how to run their day in the new setup. We stay on after go-live, because the first week or two following go-live is when the real questions surface.

Why teams pick us for this

Our founder ran enterprise sales before starting KoiShark, then led a full Salesforce-to-HubSpot migration from the inside — the data, the training, the reporting build. Revenue grew afterward. He did it again at a second company, building and leading the sales department alongside it.

We've since moved tens of thousands of records for companies migrating off Salesforce, Pipedrive, Zoho, and Keap — and built integrations for teams running more than one system on purpose. We're a certified HubSpot Solutions Partner, our client reviews are public in the HubSpot Solutions Directory, and we work in English and Spanish across the US, Canada, and Latin America.

We're not a big agency and we don't try to be. You work with the person doing the work.

Common Questions

Do we have to leave Salesforce to use HubSpot?
No. Plenty of teams run both on purpose — Salesforce as the system of record for a complex sales org, HubSpot for marketing, service, or a specific business unit. The two integrate well when the sync rules are thought through. Migrating is one option, not the only one.

Should we migrate or integrate?
It usually comes down to how entrenched Salesforce is and who depends on it. If it's mostly inertia and licensing costs, migrating is often cleaner and cheaper long-term. If you have heavy customization, compliance requirements, or a team that genuinely needs Salesforce's depth, integrating is the better call. We give you a straight recommendation during discovery, including when that recommendation is to stay put.

How long does a Salesforce to HubSpot migration take?
Most run 4 to 8 weeks from kickoff to go-live. The variables are data volume, how many custom objects you're carrying, and how many integrations need rebuilding. A lean instance with clean data can move faster; a heavily customized org with ten years of history takes longer. Integrations are typically faster — often 2 to 4 weeks, depending on how much cleanup the existing data needs.

Will we lose our historical data?
No. Activity history, notes, call logs, and email records come across with the records they belong to. Anything we recommend leaving behind — stale fields, duplicate records, unused objects — is your decision to make, and we flag it rather than deciding for you.

We already have Salesforce and HubSpot but they aren't connected properly. Can you fix that?
Yes, and it's one of the more common things we get called in for. Usually it's duplicate records, fields overwriting each other, or a sync that was switched on without anyone defining which system owns what. We audit what's actually happening, then rebuild the rules so both systems agree.

Can we run Salesforce and HubSpot at the same time during a migration?
Yes. Some teams cut over in a weekend; others run parallel for a period, or keep a two-way sync while a single department pilots HubSpot first. We'll recommend an approach based on your team's size and risk tolerance.

What happens to our Salesforce reports and dashboards?
We rebuild them in HubSpot as part of the migration, not as a follow-up project. If you're keeping both systems, we build reporting that reconciles across them. Either way, if there are reports your leadership checks weekly, tell us in discovery and they'll exist on day one.

What does this cost?
It depends on scope — record volume, custom objects, integrations, and how much training your team needs. A focused integration cleanup is a much smaller project than a full migration. We scope it during a free discovery call and give you a number before you commit to anything.

Do you train our team, or just handle the technical work?
Both. Training is included, and it's the part that determines whether any of this actually worked. We tailor sessions to where your team is, from reps who've only ever known Salesforce to admins who need to run the system themselves.

Not sure which path is yours?

Schedule a free 15-minute call. Tell us what you're running now and what isn't working — we'll tell you honestly whether to migrate, integrate, or leave it alone.