Skip to content
Get a quote

HubSpot Salesforce integration or a one-time migration

Short answer

Use the HubSpot Salesforce integration when both systems stay in use: it is an ongoing two-way sync that needs HubSpot Professional or Enterprise and a Salesforce edition with API access. Migrate once when you are leaving one system: the integration doesn't backfill past activities. FlitStack AI runs that one-time migration, with history, and can set up the integration after.

By

What we handle5
  • Keep HubSpot and Salesforce in step every day
  • Bring existing records across on day one
  • Bring past activity history
  • Salesforce Group Edition or HubSpot Starter
  • Leave Salesforce for HubSpot

What the native tool does, and where it stops

TaskNative toolWith FlitStack AI
Keep HubSpot and Salesforce in step every dayThe HubSpot Salesforce integration: an ongoing two-way sync of contacts, companies, deals and activities.Not a replacement. FlitStack AI's delta migration only keeps systems aligned during a cutover window.
Bring existing records across on day oneRecords don't sync automatically after setup. You import them or wait for sync triggers.Moves the full existing database in one validated run.
Bring past activity historyTimeline activities from before a contact syncs are not synced retroactively. Turning on activity sync doesn't import all Salesforce task data.Backfills emails, calls, meetings, tasks and notes with original timestamps and owners.
Salesforce Group Edition or HubSpot StarterNot supported: the integration needs HubSpot Professional or Enterprise and a Salesforce edition with API access (or Professional).Works through each platform's API as a one-time project.
Leave Salesforce for HubSpotHubSpot points to Smart Transfer for a one-time move. Running it with the integration creates duplicates.One-time migration including custom objects, which Smart Transfer doesn't support.
Rebuild automation in the new systemNeither the integration nor Smart Transfer rebuilds Salesforce flows or reports.The implementation service sets up pipelines and workflows in the destination.

“HubSpot Salesforce integration” gets searched by two very different groups. One runs marketing in HubSpot and sales in Salesforce and wants the two to agree every day. The other is leaving one system for the other and hopes the connector will carry everything across. The integration is built for the first group. For the second, it leaves the history behind. This guide explains the difference, with HubSpot’s documented requirements, and gives a decision table.

What is the difference between an integration and a migration?

Integration (sync)Migration (one-time)
PurposeKeep two live systems alignedMove data out of a system you’re leaving
DirectionTwo-way, ongoingOne-way, once (plus a cutover delta)
Existing recordsSync when triggered, or after you import themAll moved in the first run
Past activitiesNot backfilledBackfilled with original dates
LicencesBoth systems stay licensedOld system can be switched off
Typical toolsHubSpot’s Salesforce integration, iPaaS toolsSmart Transfer, migration tools, services

Choosing the wrong one is the expensive mistake. A sync set up as a migration leaves years of emails and calls behind. A migration chosen when both teams keep their systems leaves the data drifting apart from day two.

What does the HubSpot Salesforce integration require?

From HubSpot’s installation guide:

  • HubSpot: a Professional or Enterprise subscription in Marketing Hub, Sales Hub, Service Hub, Data Hub or Content Hub, or Smart CRM. Starter isn’t enough.
  • Salesforce: an edition with API access, or Salesforce Professional. Government Cloud is supported; Group Edition is not.
  • Salesforce user: a system administrator with API Enabled, View Setup and Configuration, Modify All on the objects you sync, Download AppExchange Packages, and the Task Type field visible.
  • API budget: a single contact sync can take up to four API calls per record, against a per-day cap.

What does the integration sync, and what doesn’t it?

The integration syncs contacts, companies, deals, activities and other supported data. The limits that matter for history, from HubSpot’s activity sync guide:

  • Records don’t sync on install. HubSpot says records won’t automatically sync after you set up the integration. You import them or let sync triggers create them.
  • Timeline sync is one-way, from HubSpot to Salesforce, as tasks.
  • Activity sync is two-way for tasks, sales emails, calls and meetings.
  • No backfill. For sales emails, tasks, meetings, notes and sales content views, “any activities from prior to the contact sync will not be synced retroactively.”
  • No bulk task import. Turning on the sync doesn’t import all task data from Salesforce to HubSpot.

So if a rep logged 200 calls in Salesforce over three years, the integration brings forward the contact, not those 200 calls.

When should I use the integration?

Use it when both systems stay in production:

  • Marketing runs in HubSpot, sales runs in Salesforce, and leads must flow both ways.
  • A business unit stays on Salesforce while another moves to HubSpot.
  • You’re phasing a move over months and need both systems current throughout. Even then, pair it with a one-time backfill of history.

When should I migrate instead?

Migrate when one system is going away:

  • You’re consolidating onto HubSpot or onto Salesforce.
  • The Salesforce licence renewal date is the deadline.
  • You need the timeline (emails, calls, meetings, notes) in the new system from day one.
  • You use Salesforce Group Edition or HubSpot Starter, which the integration doesn’t support.

HubSpot’s own advice is to use Smart Transfer for a one-time migration and the integration if you keep using Salesforce, and not both: running them together creates duplicate records because they use different identifiers.

What goes wrong when the integration is used as a migration?

These are the patterns that show up when teams switch the connector on, wait for records to flow, then cancel the old system:

  • Empty timelines. Contacts arrive, but calls, emails and meetings logged before the sync stay in Salesforce. Reps open a contact and see no history.
  • Missing records. Only records that hit a sync trigger come across. Old, unchanged accounts can sit unsynced indefinitely.
  • Original dates lost. Records created by the sync carry the sync date as their HubSpot create date.
  • API exhaustion. At up to four API calls per contact sync, a large initial backlog competes with every other integration on the org’s daily allowance.
  • Custom objects left behind. Objects outside the integration’s supported set never sync.
  • Duplicates. Adding Smart Transfer later to fill gaps creates duplicate records, because the two tools use different identifiers.

Each of these is cheap to avoid before cutover and expensive to repair after the Salesforce licence ends and the source data is gone.

Which should I choose? A decision table

Your situationChoose
Both systems stay, data must agree dailyIntegration
Leaving Salesforce, simple data, no custom objectsSmart Transfer, then check history
Leaving Salesforce, custom objects or full history neededOne-time migration (tool or service)
Leaving HubSpot for SalesforceOne-time migration into Salesforce
Phased move over several monthsMigration of history first, then integration for the overlap
Both systems stay, but the history is missingOne-time backfill, then keep the integration

How do I migrate Salesforce to HubSpot without losing history?

  1. Decide the model. Leads, record types and opportunity stages need HubSpot equivalents (contacts with lifecycle stages, pipelines, properties).
  2. Build HubSpot first: properties, pipelines, stages, association labels and users.
  3. Turn off anything that would sync or duplicate, including an existing integration, while the migration runs.
  4. Move records in order: companies, contacts, deals, then activities and files, keeping original create dates in a property.
  5. Run a delta for records changed during the cutover window.
  6. Rebuild automation and reports in HubSpot. Flows, validation rules and reports don’t migrate as data.
  7. Only then decide whether you still need the integration for any team that stays on Salesforce.

When to bring in FlitStack AI

FlitStack AI is a data-migration platform sold as software plus a done-for-you service. It runs the one-time migration the integration doesn’t: every object, including custom objects, with activities carrying original timestamps and owners, field-level mapping you review, validation on every record and one-click rollback. Delta migration keeps both systems aligned during cutover, and the HubSpot implementation service sets up pipelines, workflows and the integration itself if you keep both.

See Salesforce to HubSpot, HubSpot to Salesforce, the Smart Transfer guide, or the HubSpot migration hub. For a quote, book a free scoping call.

Questions, answered

A few useful answers.

Is the HubSpot Salesforce integration a migration tool?

No. HubSpot describes it as designed for ongoing, two-way syncing, and points to Smart Transfer for a one-time migration. It doesn't sync existing records automatically after setup, and timeline activities from before a contact syncs are not synced retroactively.

What do I need to use the HubSpot Salesforce integration?

A Professional or Enterprise subscription in Marketing, Sales, Service, Data or Content Hub, or Smart CRM; a Salesforce edition with API access, or Salesforce Professional (Group Edition isn't supported); and a Salesforce system administrator with API Enabled, View Setup and Configuration, Modify All on synced objects, Download AppExchange Packages and Task Type visible.

Can I run Smart Transfer and the Salesforce integration together?

HubSpot says no: using both at the same time creates duplicate records in HubSpot and Salesforce, because they use different identifiers. Pick one for the job.

Does the integration use Salesforce API calls?

Yes. HubSpot says a single contact sync can take up to four API calls per record, and usage is capped per day. Large databases and frequent updates can use up a Salesforce org's daily API allowance.

Get a quote

Rather have it done for you?

FlitStack AI maps, validates and migrates your data, sets up the process in the new system, and keeps a one-click rollback.

Get a quote