17 Things That Break in a Salesforce to HubSpot Migration

The problem with a migration going wrong is when you find out. A record count that came up short surfaces weeks later, inside a report nobody can reconcile. A deal with no history attached gets discovered by the rep who needed that history. Files, old activity, quoting data, and opt-out history turn up still sitting in Salesforce, often after the contract has already ended.

These are the seams where two very different systems meet, and each one can be caught during scoping rather than at cutover. This guide covers 17 of them, with a plain explanation of what happens, what it looks like in your own data, and a check your admin can run before anything moves.

What You’ll Find Inside

Walk into your migration knowing what to check and when. This guide covers the Salesforce settings that can prevent the connection from working, count checks that catch missing records, field and dropdown issues that can fail without an error, and sync patterns that can create duplicates after go-live. It also covers data areas that are often left behind, including files, old activity, quoting objects, and opt-out records. Each item includes the check to run and the fix to apply.

Who This Is For

RevOps, sales ops, and marketing ops teams planning a move off Salesforce
Teams working against a Salesforce renewal date or contract end date
Salesforce admins who will run the exports, field mapping, and permissions
Companies running HubSpot and Salesforce side by side who keep hitting sync problems
Non-technical stakeholders who need to understand what can go wrong and why