Salesforce to HubSpot Migration: A Complete Guide to Data, Process & Best Practices

A Salesforce to HubSpot migration is not a matter of exporting one CRM and importing another.

Salesforce may contain leads, contacts, accounts, opportunities, cases, activities, campaigns, products, quotes, users, custom objects, lookup relationships, validation rules, flows, and years of historical decisions built into the data model.

HubSpot can support a connected customer platform, but it represents some of those concepts differently. The migration succeeds only when the business meaning, record relationships, ownership, history, and go-forward processes survive the translation.

This guide explains what can move, what needs to be transformed, what must be rebuilt, and how to migrate Salesforce to HubSpot without leaving your team with clean-looking but disconnected data.

Why Are Businesses Moving from Salesforce to HubSpot?

Salesforce is highly configurable and can support complex enterprise requirements. That flexibility is valuable, but it can also create an environment that requires significant administration, specialist development, and ongoing governance.

Businesses commonly consider HubSpot when they want:

• Sales, marketing, service, content, and customer data on one platform.
• A CRM that teams can configure and adopt with less operational overhead.
• Faster implementation of pipelines, properties, workflows, and reports.
• Better alignment between demand generation and revenue teams.
• A consolidated CRM after an acquisition or operating-model change.
• A simpler technology stack with fewer integrations between customer-facing systems.

Migration should still be tied to a specific capability or operating goal. A complicated Salesforce org does not become simple merely because its records move. Unnecessary fields, conflicting processes, duplicate automations, and poor ownership rules should be resolved before they are recreated in HubSpot.

Use the migration as an opportunity to simplify, but do not simplify by deleting context the business still needs.

Salesforce vs. HubSpot: What Changes in the CRM Data Model?

Salesforce and HubSpot can represent the same customer journey, but the object models and platform behavior are not identical.

The largest design decision is often the Salesforce Lead object. HubSpot uses one contact record across the lifecycle, while Salesforce commonly separates unconverted leads from contacts associated with accounts.

Before migration, decide how each Salesforce lead category maps to HubSpot. Do not flatten every person into the same lifecycle stage, because that will distort routing, funnel reporting, and automation from day one.

Which Salesforce Data Can Be Migrated to HubSpot?

Most customer and revenue data can be migrated when the source is accessible and the target model is prepared. Typical scope includes:

• Leads and contacts.
• Accounts and account-related fields.
• Opportunities, pipelines, stages, amounts, and close dates.
• Cases and service records.
• Tasks, calls, meetings, notes, emails, and other supported activities.
• Products, price information, quotes, and line items where supported.
• Campaign membership and attribution fields through an agreed target design.
• Standard and custom fields.
• Custom objects supported by the target subscription.
• Users, owners, and record attribution.
• Record associations and supported relationship labels.
• Attachments and files where an appropriate migration path exists.

The correct question is not only “Can this record move?” It is “Can the record land with the same meaning and the relationships the business depends on?”

What Salesforce Data Doesn't Map Directly to HubSpot?

Some Salesforce concepts require translation because HubSpot implements them differently.

Leads and conversion history

Salesforce leads may become HubSpot contacts, but lead status, conversion state, source, and historical qualification context need explicit properties and lifecycle rules.

Account hierarchies and complex relationships

Parent-child accounts, junction objects, multiple contact roles, and custom lookup structures may require redesigned associations or custom objects in HubSpot.

Campaigns

Salesforce campaigns can represent events, lists, outbound programs, or broad membership structures. HubSpot campaigns are designed primarily to group marketing assets and measure performance. Campaign members may need lists, marketing events, custom objects, or dedicated properties depending on how the data is used.

Multi-select and restricted values

Salesforce picklists, multi-select picklists, formulas, dates, currencies, and validation-enforced values do not always map one-to-one to HubSpot property types. Define a transformation and fallback for every incompatible value.

Audit and field history

Created dates, last-modified dates, field history, opportunity-stage history, and conversion events may not recreate themselves as native HubSpot history. Preserve the required source timestamps and events in supported activity types or custom properties.

Permissions and sharing

Salesforce profiles, roles, permission sets, sharing rules, and record-level access do not simply import into HubSpot. Users, teams, seats, and permissions need to be designed for the target platform.

What Salesforce Data Needs to Be Rebuilt in HubSpot?

Data migration and operating-model migration are separate but connected workstreams.

The following normally need to be rebuilt or redesigned:

• Salesforce Flow, Process Builder logic, workflow rules, and Apex automation.
• Validation rules and required-field behavior.
• Assignment rules, queues, territories, and escalation logic.
• Email templates, cadences, and sales sequences.
• Reports, dashboards, forecasts, and custom report definitions.
• Page layouts, record types, views, and navigation.
• Profiles, permission sets, roles, and sharing rules.
• Integrations, connected apps, webhooks, and authentication.
• Marketing assets and campaign structures that do not have a direct equivalent.

Rebuilding does not mean copying every Salesforce process exactly. Some complexity may exist only because Salesforce required a particular implementation. Recreate the business outcome in HubSpot using the simplest supported design that preserves control, reporting, and user experience.

How to Create a Salesforce-to-HubSpot Data Mapping Strategy

Create a complete inventory

List every object, field, relationship, record type, pipeline, stage, owner, automation, report, integration, and permission dependency. Capture source record counts by object and meaningful business segment.

Preserve Salesforce IDs

Create a legacy Salesforce ID property on each HubSpot object. These IDs act as the stable join between source and destination and support associations, repeatable updates, validation, and post-cutover investigation.

Map objects before fields

Start with the target architecture:

• Which Salesforce leads become HubSpot contacts?
• How do accounts become companies?
• How do opportunities map to pipelines and deals?
• Which cases become tickets and in which pipeline?
• Which custom objects remain custom objects?
• Which lookup and junction relationships become HubSpot associations?

Only after the object model is agreed should individual fields be mapped.

Map every field and value

For each field, record the source type, target type, transformation, required-value rule, dropdown crosswalk, default, and in-scope status.

Give special attention to:

• Lead status and lifecycle stage.
• Opportunity stages and probabilities.
• Owners, queues, inactive users, and default owners.
• Multi-select values.
• Currencies, dates, time zones, and number formats.
• Consent, opt-out, subscription, and legal-basis data.
• Formula and rollup outputs.
• Original source, campaign, and UTM fields.

Decide what not to migrate

Exclude obsolete fields, test records, dead integrations, duplicated automation, stale leads, and historical information that has no legal, operational, or reporting value.

Document every exclusion and obtain business sign-off. “Not migrated” should be a decision, not a surprise discovered after cutover.

How to Migrate Salesforce to HubSpot Step by Step

1. Audit and clean Salesforce

Identify duplicates, incomplete relationships, inactive owners, unused fields, obsolete record types, invalid picklist values, and data that should be archived. Resolve known merges and ownership problems in the source while the business context is still available.

2. Back up data and metadata

Export the required Salesforce data and retain a metadata reference for objects, fields, relationships, automation, layouts, reports, and integrations. If HubSpot already contains records, export a pre-migration snapshot of the target as well.

3. Design and build HubSpot

Create users, teams, permissions, objects, custom properties, pipelines, deal stages, ticket stages, association labels, lists, and required target structures.

Build replacement automation in an inactive or safely controlled state. Pause existing HubSpot workflows that could trigger when migrated records are created or updated.

4. Complete field and association mapping

Finalize object mapping, field mapping, value crosswalks, owner mapping, legacy-ID properties, and relationship rules. Define how leads, campaigns, account hierarchies, opportunity contact roles, custom junction objects, and historical activities will be handled.

5. Choose the migration method

HubSpot's native import tools can suit smaller migrations with carefully prepared files and supported objects. API-based migration provides more control over transformations, associations, repeat runs, and large datasets. A purpose-built migration platform reduces manual engineering when the Salesforce org contains custom objects, complex associations, historical activity, ongoing changes, or extensive validation requirements.

The native HubSpot-Salesforce integration is designed for ongoing synchronization between live systems. Do not assume it will perform a complete one-time historical migration or rebuild your target model automatically.

6. Run a representative test

Test hundreds of records across every important object, not only clean contacts. Include custom fields, multiple opportunity contacts, account hierarchies, inactive owners, tasks, events, cases, consent values, and records that should fail.

Validate the result and correct the mapping before scaling.

7. Run the full migration in dependency order

A common sequence is:

1. Users and owner mappings.
2. Companies from Salesforce accounts.
3. Contacts and leads according to the approved lead strategy.
4. Deals from opportunities.
5. Tickets from cases.
6. Activities, notes, emails, and files.
7. Products, line items, quotes, and custom objects.
8. Remaining associations and relationship labels.

The exact order must follow your relationship dependencies.

8. Validate records and relationships

Reconcile counts and failed records, then inspect fields, owners, stages, timestamps, consent, and associations. Compare high-value customers, open opportunities, active cases, and recent activity histories in both systems.

9. Run the delta migration

Capture leads, contacts, accounts, opportunities, cases, activities, ownership changes, and relationship updates created after the initial extraction. Run the final delta during the cutover window and confirm the target is current.

10. Cut over, train users, and stabilize

Redirect forms and integrations, enable the required HubSpot automation in a controlled order, and make HubSpot the new system of record. Give teams the views, pipelines, reports, email connections, and training they need to work on day one.

Keep Salesforce available as a read-only reference through a defined stabilization period.

Common Salesforce to HubSpot Migration Challenges

Lead-to-contact translation

Flattening every lead and contact into one undifferentiated contact population breaks lifecycle reporting and routing. Define the target lifecycle model before loading records.

Complex relationships

Account hierarchies, opportunity contact roles, junction objects, and custom lookups can lose secondary relationships if the migration preserves only the primary parent.

Historical activities

Tasks, events, emails, calls, notes, timestamps, owners, and parent references need more work than standard records. Define the required history depth before estimating the migration.

Custom automation

Salesforce flows and Apex logic do not become HubSpot workflows automatically. Rebuild the business outcome and test it against migrated data.

API limits and long-running migrations

Large migrations must respect the current limits of Salesforce, HubSpot, and every connected application. Use bulk endpoints, batching, retries, backoff, and a monitored delta strategy instead of a single uncontrolled job.

Duplicate records

Email and domain matching alone may not reflect Salesforce duplicate rules. Clean duplicates in the source, preserve Salesforce IDs, and define how records without a reliable key will be handled.

Incorrect automation enrollment

Imported records can trigger HubSpot workflows, lead routing, notifications, and customer emails. Pause or suppress automation until the relevant enrollment rules have been tested.

Reporting discontinuity

Dashboards may return different results because lifecycle, stage, source, or campaign definitions changed. Rebuild and reconcile critical reports before users rely on them.

Salesforce to HubSpot Migration Checklist

Decide

• Define the business goal and target HubSpot subscription.
• Approve the Salesforce Lead-to-HubSpot Contact strategy.
• Decide the custom-object and association architecture.
• Define the historical activity depth.
• Agree on exclusions and archival requirements.

Prepare

• Inventory data, metadata, automation, reports, users, and integrations.
• Capture source counts by object.
• Clean duplicates and invalid values.
• Preserve Salesforce IDs in the target design.
• Complete field, value, owner, pipeline, and consent mapping.
• Back up Salesforce and the existing HubSpot portal.

Build

• Create users, teams, permissions, objects, and properties.
• Recreate pipelines, deal stages, ticket stages, and labels.
• Rebuild required automation, reports, lists, and routing logic.
• Pause workflows that could trigger during import.
• Prepare integrations and cutover instructions.

Execute

• Run a representative test migration.
• Correct mappings and repeat until clean.
• Load full data in dependency order.
• Review failed records after every major batch.
• Validate values, owners, stages, timestamps, consent, and associations.
• Run the final delta.

Cut over and stabilize

• Pass the predefined go/no-go criteria.
• Redirect forms, integrations, and users.
• Re-enable automation deliberately.
• Reconcile critical reports.
• Train teams and provide one support channel.
• Keep Salesforce read-ready through hypercare.
• Decommission only after the target is stable.

Move from Salesforce to HubSpot- Without Losing What Matters, with SuprSwitch

A Salesforce migration becomes difficult when the source contains years of custom objects, relationships, activities, ownership, and process logic. That is where manual exports and generic imports begin to lose context.

SuprSwitch by Suprdense is designed to move Salesforce data into HubSpot while preserving the structure around each record. It supports guided object and property mapping, activities, users, ownership, associations, validation, retries, and delta migration.

Use SuprSwitch when your Salesforce-to-HubSpot migration needs more than a flat transfer - especially when custom objects, complex relationships, historical activity, or ongoing source changes are in scope.

Frequently Asked Questions

What Salesforce data can be migrated to HubSpot?

Leads, contacts, accounts, opportunities, cases, activities, notes, products, selected campaign information, standard and custom fields, users, ownership, supported custom objects, and associations can be migrated. The exact scope depends on the source configuration, target HubSpot subscription, and migration method.

How are Salesforce Leads, Contacts, Accounts, and Opportunities mapped to HubSpot?

Salesforce leads and contacts generally become HubSpot contacts, accounts become companies, and opportunities become deals. Lead status, lifecycle stage, pipelines, owners, and relationship rules must be mapped explicitly so the records retain their business meaning.

What Salesforce data needs to be rebuilt in HubSpot after migration?

Salesforce flows, Apex triggers, validation rules, assignment rules, permissions, layouts, reports, dashboards, and many integration configurations need to be rebuilt or redesigned in HubSpot. They do not move automatically with CRM records.

How is Salesforce activity history preserved during migration to HubSpot?

Tasks, events, calls, emails, and notes should be extracted with their Salesforce IDs, timestamps, owners, activity types, and parent references. They can then be recreated as supported HubSpot activities and associated with the correct contacts, companies, deals, or tickets.

How long does a Salesforce to HubSpot migration take?

A small, clean migration using standard objects may take a few days. A complex migration involving custom objects, historical activities, multiple integrations, relationship reconstruction, testing, and delta synchronization can take several weeks. Data-model complexity and preparation quality usually have more impact than record count alone.