A leadership team gathered around a laptop in a meeting room above the city at dusk

What moves from Salesforce to HubSpot?

The records move. The way you work is redesigned.

Moving from Salesforce to HubSpot brings your records and history across: leads, contacts, accounts, opportunities, cases, tasks, campaigns, events and custom objects. Automation, permissions, reports and integrations are rebuilt on HubSpot rather than copied, which is where the real change happens.

Who should careCTO, CROMetric it movesData quality, forecast accuracy, TCO

At a glance

Imported versus redesigned.

Moves acrossRecords and history
LeadsContactsAccountsOpportunitiesCasesTasksCampaignsEventsCustom objects
Imported
RebuiltHow you work
AutomationData modelPermissionsReportsIntegrations
Redesigned

Objects as listed in HubSpot's Salesforce import documentation, available on Professional or Enterprise tiers.

What data moves from Salesforce to HubSpot?

Records and their history. HubSpot's Salesforce import supports leads, contacts, accounts, opportunities, tasks, campaigns, cases, events and custom objects, on Professional or Enterprise tiers (HubSpot Knowledge Base). HubSpot's Smart Transfer tool also creates the properties and pipelines in your new account and can transfer users, currencies and activity history such as calls, emails, meetings, notes and tasks, with one-time transfers for items such as attachments (HubSpot Knowledge Base).

What has to be rebuilt rather than copied?

Anything that encodes how you work. HubSpot lists integrations, automation, and reports and dashboards as part of a switch (HubSpot). In practice that means:

  • Automation. Salesforce flows and rules become HubSpot workflows, redesigned rather than translated line by line.
  • Data model. Fields, record types and picklists are mapped to HubSpot properties and pipelines. Many are retired.
  • Permissions. Roles and sharing rules become HubSpot teams, permission sets and, for regional groups, brand and market structures.
  • Reports. Rebuilt around the revenue number, not the old report list.
  • Integrations. ERP, finance and messaging connections are rebuilt against the new customer model.

What changes for your teams?

Marketing, sales and service work on one platform and one customer record. Admin work tends to move from developers to operations teams, because HubSpot is configured more than coded. Reporting changes most: one pipeline definition and one set of dashboards, by market and for the group. That is also the foundation HubSpot's AI agents draw on.

How does HubSpot support the move?

HubSpot describes three approaches: HubSpot-led, partner-led and hybrid (HubSpot). It also describes a phased approach in which both systems stay on during the move. Smart Transfer runs in six steps: audit your data, prepare your portal, sync your records, transfer additional data, mark empty properties, and clean up (HubSpot Knowledge Base).

How long does a Salesforce migration take?

HubSpot says it typically sees most businesses complete their migration within three months, and that it may take longer depending on approach (HubSpot). For multi-market enterprises, the number of markets, integrations and approvals sets the real pace.

What goes wrong, and how do you avoid it?

  • Copying the old model. Design the HubSpot model first, then map Salesforce to it.
  • Migrating everything. Move what has a business purpose and a lawful basis. Archive the rest.
  • Ignoring data protection. HubSpot hosts data in the EU, Canada, Australia and the US (HubSpot). Document the transfer for each market before data moves.
  • A single big-bang cutover. Migrate in waves, by market, with a pilot first.
  • No decommission date. Set one and keep it.

Map the move before you make it.

A strategy call reviews your Salesforce estate and what the HubSpot model should look like.