Skip to content
Get a quote

How do we migrate from Salesforce to HubSpot without losing deal and activity history?

Short answer

Move the history as a one-time migration, not through the sync. The integration's activity sync only picks up activities created or updated after you turn it on. Smart Transfer moves email messages, events, notes and tasks, but not calls or custom objects. Store each record's original created date in a custom property, because HubSpot's is read-only for everything except deals.

By

Where history gets lost

History usually goes missing in one of three places. The integration is a sync, not a backfill. Smart Transfer doesn’t cover every activity type. And HubSpot stamps import time on any date you don’t map. Salesforce also stores activities differently from HubSpot. Calls and emails are often Tasks with a Type value, meetings are Events, and notes may be legacy Notes or Salesforce Files, so each needs its own mapping.

What the native tools do / where they stop

ToolWhat it movesWhere it stops
HubSpot–Salesforce integration (activity sync)Two-way sync of tasks, emails, calls and meetingsHubSpot: “Turning on the sync will not automatically import all task data from Salesforce”
Smart TransferEmail messages (as email activities), events (as meetings), notes, tasks; attachments as a one-time transferCalls not listed; custom objects not supported; custom field mappings need Data Hub; Super Admin only
Import toolCalls, emails, meetings, notes and tasks from files, with an activity dateActivities default to the import date if you don’t map one; emails, meetings, notes and tasks can’t be updated by import
HubSpot’s paid CRM Data MigrationSalesforce records up to 5M (Gold)Quotes, price books, workflows and reports are out of scope

Steps that keep history intact

  1. Create users in HubSpot first, so owners and activity authors match by email.
  2. Design pipelines, one per opportunity record type, and map every stage.
  3. Add custom properties for the Salesforce ID, original created date, stage probability and forecast category.
  4. Load companies, contacts and deals, with associations, in that order.
  5. Load activities by type, with Activity date mapped and associations to the contact, company and deal.
  6. Load files, which HubSpot can attach only as existing file IDs.
  7. Reconcile: activity counts per deal in Salesforce compared with HubSpot, on a sample of deals.

Step 3 is the one people regret skipping. HubSpot’s Create date is read-only for every object except deals, so a contact created in 2017 will otherwise show the migration date for good.

Where FlitStack AI fits

FlitStack AI moves Salesforce calls, emails, tasks, meetings and notes with their original timestamps and owners. It also maps record types to pipelines, and you review the mapping. See Salesforce to HubSpot or HubSpot migrations.

Questions, answered

A few useful answers.

Can we run Smart Transfer and the Salesforce integration together?

Pick one per object. Running both against the same Salesforce data risks creating duplicates. Use a one-time migration for history, then the integration only if both systems stay live.

What happens to Salesforce opportunity stage history?

It doesn't move as history. HubSpot will show today's stage. If you report on stage duration, migrate the Salesforce field history into custom properties or a custom object.

Do Salesforce record types survive?

HubSpot has no record types. Each opportunity record type usually becomes its own deal pipeline with its own stages.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote