Accounts & Contacts
Deduplicated and mapped to HubSpot's company and contact model before anything moves.
Salesforce to HubSpot
Salesforce is the migration we run most often. Native sync handles your live data, Serendipity architects the rest, so associations, pipeline history, and custom fields survive the move intact.
This is one path within a full HubSpot migration. See how it fits with workflow rebuilds and team adoption.
The Foundation
This can include, but isn't limited to, the following, scoped to how customized your Salesforce org actually is.
Deduplicated and mapped to HubSpot's company and contact model before anything moves.
Stage history, close dates, and won or lost data preserved, so forecasting doesn't break at cutover.
HubSpot's Salesforce integration configured and scoped for what should sync ongoing versus what's a one-time import.
An audit of what your org actually uses, so custom fields get mapped intentionally instead of copied by default.
Closed opportunities, old activities, and anything the live sync won't carry, imported and associated correctly.
Record counts and association checks before go-live, so nothing quietly goes missing in the move.
The Problem
Salesforce orgs are rarely simple. Here's what goes wrong when a migration treats it like a basic export.
Opportunity stages don't map cleanly.
A custom Salesforce stage model gets flattened into HubSpot's defaults, and your forecast stops meaning anything.
Custom fields get left behind.
The fields your team actually relies on weren't scoped, so they're quietly missing after go-live.
The sync is left running both ways.
Bidirectional sync after cutover means updates flow back into a system you're supposed to be retiring.
Reps keep two tabs open.
Without a clear cutover and training plan, your team quietly keeps working in Salesforce.
Part of a Full Migration
Moving the data is one part. Here's where it connects to the rest of the migration.
Accounts, contacts, opportunities, and associations mapped and migrated from your Salesforce org.
Salesforce Flows and Process Builder logic audited and rebuilt properly in HubSpot, not just copied.
Change Management & AdoptionTraining and a go-live plan so your team actually stops opening the Salesforce tab.
FAQs
For current, active data, usually yes. The native sync handles contacts, companies, and deals well. Custom objects only sync natively if you're on an Enterprise-level HubSpot hub; without that tier, custom objects, along with historical and closed records and anything else the sync doesn't support, need a separate mapped import.
They don't transfer automatically. We audit what's actually running, then rebuild the logic that still matters inside HubSpot's workflow tools. See our workflow migration page for how that works.
It depends on how customized your org is, how many objects and fields you use, and how much historical data needs to move. We scope a timeline after the discovery audit, not before.
Yes, where Salesforce's export tools support it. We scope file and attachment migration separately since volume and format vary a lot org to org.
Keep Exploring
See how a Salesforce migration fits into a full CRM replatform.
Migration PathHow Serendipity rebuilds your automation logic in HubSpot.
Migration PathTraining and go-live planning so your team actually switches over.
Free Scoping Call
In one call, we'll map your Salesforce org and show you exactly what a real migration looks like, with a scope built around your data, not a template.
Book My Free Scoping Call →Prefer email? Reach out through the Get Started form and we'll schedule a discovery call.