Skip to content
Get a quote

Salesforce to HubSpot migration

Moving from Salesforce Sales Cloud to HubSpot means collapsing Salesforce's Lead-Contact-Account-Opportunity object graph into HubSpot's Contact-Company-Deal model. FlitStack AI maps every Salesforce record — Leads routing to HubSpot Contacts, Accounts to Companies, Opportunities to Deals — preserving original timestamps and owner assignments so your new HubSpot instance reflects the full history of every relationship from day one.

Short answer

FlitStack AI migrates contacts, companies, deals, activities and notes from Salesforce to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

By

Source Salesforce
DestinationHubSpot
ContactCompanyDealActivityNote
Mapped field by field · sample run · one-click rollback

What moves from Salesforce to HubSpot?

Salesforce Sales Cloud separates Leads and Contacts into distinct objects with a conversion workflow, while HubSpot operates on a single Contact object with a lifecycle_stage property.

Read the full summary

This fundamental data-model difference drives every mapping decision in a Salesforce-to-HubSpot migration. We extract Leads, Contacts, Accounts, Opportunities, custom fields, tasks, events, and notes via the Salesforce REST and Bulk APIs, then write them into HubSpot's CRM using the Contacts, Companies, and Deals API endpoints. Salesforce record types — which scope Opportunity stage pick-lists and page layouts per business unit — have no native HubSpot equivalent; we either collapse them into HubSpot deal pipelines or flag them for manual pipeline design post-migration. Salesforce Flows, workflow rules, Process Builder automations, and validation rules do not migrate — we export their definitions as rebuild references for your HubSpot admin. Owner resolution happens by email match against HubSpot users. Salesforce's CreatedDate migrates as a custom HubSpot property since HubSpot overwrites Createdate at import time.

transformed

Lead → Contact

Salesforce Leads have no direct HubSpot equivalent — HubSpot has one Contact object.

How it maps

We import all Salesforce Leads as HubSpot Contacts, setting lifecycle_stage to 'lead' by default. The original Salesforce Lead Status maps to a custom pick-list property on the Contact record so that qualification status is preserved as a reference field post-migration.

direct

Contact → Contact

Salesforce Contacts migrate directly to HubSpot Contacts.

How it maps

The AccountId lookup on the Salesforce Contact determines the primary Company association in HubSpot. Salesforce Contacts without an AccountId receive a placeholder company association to maintain data integrity on the HubSpot side. This ensures all contact records have a valid company reference and prevents orphaned records from blocking deal associations.

direct

Account → Company

Salesforce Accounts map 1:1 to HubSpot Companies.

How it maps

Parent Account relationships (Salesforce ParentId) translate to HubSpot's parent-company hierarchy. Multi-address accounts collapse to a single primary address in HubSpot, with additional addresses stored as a custom property if needed for reference. The organizational hierarchy between parent and child accounts is preserved in the HubSpot company structure.

direct

Opportunity → Deal

Salesforce Opportunities map to HubSpot Deals.

How it maps

The Opportunity StageName becomes the HubSpot dealstage within the designated pipeline. CloseDate, Amount, and Name map directly. The Salesforce RecordTypeId that scoped the Opportunity's stage pick-list does not exist in HubSpot — we create one HubSpot pipeline per record type and flag the mapping plan for your admin to validate.

split

Opportunity (RecordTypeId) → Deal (Pipeline)

Each Salesforce record type becomes a separate HubSpot deal pipeline.

How it maps

A Salesforce org with three record types (New Business, Upsell, Partner) yields three HubSpot pipelines with independent stage sets. The stage probability and forecast category from Salesforce are stored as custom properties on the HubSpot deal since HubSpot does not use a probability field by default.

direct

Account Contact Relation → Company Association

Salesforce's Account Contact Relations support N:N contact-to-account associations natively.

How it maps

HubSpot also supports N:N contact-to-company associations. We migrate all active relations and preserve the IsPrimary flag as a HubSpot contact property since HubSpot has no native primary-flag on associations. This maintains the complete web of relationships between contacts and their multiple company affiliations.

What moves15 objects
SalesforceHubSpot
  • LeadContacttransformed
  • ContactContact1:1
  • AccountCompany1:1
  • OpportunityDeal1:1
  • OpportunityDealsplit
  • Account Contact RelationCompany Association1:1

+ 9 more in the mapping below

How Salesforce and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionSalesforceHubSpot
Record type modelSalesforce uses RecordTypeId on Opportunities to scope stage pick-lists and page layouts per business unit; each record type requires its own page layout assignment.HubSpot has no record-type equivalent; all Deals live in one object with pipeline-stage pick-lists scoped per pipeline, and all contacts share a single record structure.
Lead handlingSalesforce maintains a separate Lead object with Status pick-list and conversion to Contact/Account/Opportunity; converted leads retain a converted flag.HubSpot has no Lead object — all records land as Contacts and use lifecycle_stage to distinguish Subscriber from Customer status.
Account-Contact relationshipSalesforce contacts require an AccountId lookup; N:N relationships use Account Contact Relations; each contact has exactly one primary Account.HubSpot supports N:N contact-to-company associations natively; a contact can belong to multiple companies simultaneously with no primary enforcement.
Automation modelSalesforce automations live in Flow (Screen, Autolaunched, Record-Triggered), Process Builder, and Workflow Rules; Apex triggers add code-level logic.HubSpot automations are called Workflows and operate on Contacts, Companies, Deals, and Tickets; no equivalent to Salesforce's Apex triggers exists in native HubSpot.
Custom field namingSalesforce custom fields append __c to the API name (e.g., Customer_Tier__c) and store metadata in FieldLevelSecurity per profile.HubSpot uses camelCase internal names with a display label; custom properties are created in Settings > Properties and scoped to specific object types.
Activity storageSalesforce stores emails as Tasks with Type='Email', calls as Tasks with Type='Call', meetings as Events with start/end datetimes, and notes as Salesforce Files or the legacy Note object.HubSpot stores all engagement types — emails, calls, meetings, notes — as Activities on the contact or company timeline, with a single engagement type property.
Pricing modelSalesforce charges per seat (Enterprise $175/user/month) plus add-ons for API access, Data Loader usage, and sandbox environments; hidden costs include 8–10% annual uplift and storage overages.HubSpot charges per seat with API and integrations included in all paid tiers; HubSpot Starter starts at $15/user/month with a 5-seat minimum, scaling to Enterprise with custom pricing.
Reporting architectureSalesforce uses a dedicated Reports tab with a drag-and-drop report builder; custom report types can join up to three objects; Salesforce Analytics (Tableau) is a separate licensed product.HubSpot uses a custom report builder inside the CRM; Sales Hub Enterprise adds custom property-based reports, predictive lead scoring, and revenue attribution.

Salesforce to HubSpot field mapping

The 30 most-used fields of 48 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
SalesforceHubSpot
  1. FirstNameLead firstnameContact
  2. LastNameLead lastnameContact
  3. EmailLead emailContact
  4. PhoneLead phoneContact
  5. MobilePhoneLead mobilephoneContact
Salesforce fieldHubSpot fieldMappingNote
Lead.FirstNameContact.firstnamedirect
Lead.LastNameContact.lastnamedirect
Lead.EmailContact.emaildirect
Lead.PhoneContact.phonedirect
Lead.MobilePhoneContact.mobilephonedirect
Lead.TitleContact.jobtitledirect
Lead.CompanyContact.associatedcompanyidtransformedLead.Company creates or links to a HubSpot Company record; association is set on the Contact after the Company exists.
Lead.StatusContact.sf_lead_status__ccustom_field_requiredHubSpot has no Status field on Contact; we create a custom property to preserve the original Salesforce Lead Status value.
Lead.LeadSourceContact.hs_analytics_sourcevalue_mappingSalesforce LeadSource pick-list maps to HubSpot's contact source property; unmapped values default to 'Other'.
Lead.IsConvertedContact.sf_was_converted_lead__ccustom_field_requiredHubSpot stores a boolean flag indicating the record was a converted Salesforce Lead.
Lead.CreatedDateContact.original_create_date__ccustom_field_requiredHubSpot's createdate is set at import time; original Salesforce CreatedDate preserved as a custom datetime property.
Lead.IdContact.source_system_id__ccustom_field_requiredSalesforce Lead ID stored on the HubSpot contact for traceability and delta-run de-duplication.
Contact.FirstNameContact.firstnamedirect
Contact.LastNameContact.lastnamedirect
Contact.EmailContact.emaildirect
Contact.PhoneContact.phonedirect
Contact.MobilePhoneContact.mobilephonedirect
Contact.TitleContact.jobtitledirect
Contact.AccountIdContact.associatedcompanyidtransformedSalesforce AccountId resolves to a HubSpot Company ID; the Company must be migrated before the Contact.
Contact.BirthdateContact.date_of_birth__ccustom_field_requiredBirthdate is not a native HubSpot property; migrated as a custom date property.
Contact.CreatedDateContact.original_create_date__ccustom_field_requiredOriginal Salesforce CreatedDate preserved as a custom datetime for reporting continuity.
Contact.LastModifiedDateContact.original_last_modified_date__ccustom_field_requiredOriginal Salesforce LastModifiedDate preserved as a custom datetime for delta-tracking.
Contact.IdContact.source_system_id__ccustom_field_requiredSalesforce Contact ID stored on the HubSpot contact for traceability and delta-run de-duplication.
Account.NameCompany.namedirect
Account.WebsiteCompany.domaindirect
Account.IndustryCompany.industryvalue_mappingSalesforce Industry pick-list values mapped to HubSpot industry options; unmapped values mapped to 'Other'.
Account.NumberOfEmployeesCompany.numberofemployeesdirect
Account.AnnualRevenueCompany.annualrevenuedirect
Account.BillingStreetCompany.addressdirect
Account.BillingCityCompany.citydirect

What to watch for in a Salesforce to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Salesforce RecordTypeId has no HubSpot equivalent — stage scoping requires pipeline redesign

Salesforce record types scope Opportunity stage pick-lists, page layouts, and business-unit-specific validation rules.

How we handle it

HubSpot has no record-type construct — all deals in a pipeline share the same stage set. A Salesforce org with four record types (New Business, Renewal, Partner, Internal) will have four HubSpot pipelines, each with its own stage set. Stage probabilities from Salesforce are preserved as a custom deal property since HubSpot does not natively model probability. We deliver a record-type-to-pipeline mapping plan before migration runs so your team can pre-design the HubSpot pipeline structure.

high

Salesforce Leads collapse into HubSpot Contacts — lifecycle stage assignment requires business logic

Salesforce maintains a separate Lead object with a Status pick-list (New, Working, Nurturing, Converted) and a conversion workflow that creates Contact, Account, and Opportunity records simultaneously.

How we handle it

HubSpot has no Lead object — all records land as Contacts. We import Salesforce Leads as HubSpot Contacts with lifecycle_stage set to 'lead' by default, and we preserve the original Lead Status in a custom property (sf_lead_status__c). Converted Salesforce Leads land as Contacts with lifecycle_stage='customer' since conversion implies a deal was created. Your team decides whether to route all Leads to the same lifecycle stage or apply a value-mapping based on Lead Status.

high

HubSpot custom objects cap at 10 per portal — excess Salesforce custom objects need consolidation

HubSpot Enterprise limits custom objects to 10 per portal.

How we handle it

Salesforce orgs with more than 10 custom objects require a scoping decision before migration begins: low-usage custom objects can be archived, or overlapping custom objects can be merged into existing HubSpot objects using a type-identifier custom property. We identify the consolidation options in the discovery phase and present them as a business decision to your team — this is not a technical limitation we can bypass, and it must be resolved before data mapping finalizes.

medium

Salesforce Flows, Process Builder, and Workflow Rules do not migrate and have no direct HubSpot equivalent

Salesforce automation lives in Flow (Record-Triggered, Screen, Autolaunched), Process Builder, and Workflow Rules.

How we handle it

HubSpot Workflows operate on different triggers (property changes, form submissions, deal stage changes) and cannot model Salesforce's field-update logic natively. Apex trigger code has no HubSpot equivalent. We export your Salesforce automation definitions as a structured reference document and can assist with HubSpot workflow rebuild scoping, but the rebuild itself is a separate engagement. Critical automations — territory assignment, SLA timers, approval chains — need to be reviewed by your HubSpot admin before go-live.

medium

Salesforce CreatedDate becomes a custom property — HubSpot sets createdate at import time

HubSpot's createdate timestamp is set when a record is written to the HubSpot API, not when the original record was created in Salesforce.

How we handle it

We preserve the original Salesforce CreatedDate, LastModifiedDate, and Opportunity CreatedDate as custom properties on the HubSpot record (original_create_date__c, original_last_modified_date__c). Historical reporting that relies on createdate will need to reference these custom properties in HubSpot reports. Activity timestamps and close dates are preserved natively since those fields map directly without HubSpot-overwrite behavior. Reports and dashboards using CreatedDate should be updated post-migration to reference the custom property.

How the migration runs

  1. Discover Salesforce schema and map to HubSpot data model

    FlitStack AI extracts the full Salesforce schema via the Tooling API: all standard and custom objects, field-level metadata (API names, data types, pick-list values), record type assignments per Opportunity, and workflow/flow definitions.

    What this step covers

    We cross-reference this against HubSpot's object model to generate the object mapping plan, flagging custom objects exceeding HubSpot's 10-object limit, identifying value-mapping needs for pick-lists, and surfacing Salesforce record-type-to-HubSpot-pipeline splits. This discovery output becomes the migration blueprint before any data moves.

  2. Create HubSpot properties and pipelines matched to the mapping plan

    Before data ingestion, FlitStack AI (or your HubSpot admin) creates all custom properties identified in the field mapping plan: sf_lead_status__c, sf_probability__c, source_system_id__c, original_create_date__c, forecast_category__c, and others.

    What this step covers

    Each Salesforce record type gets a corresponding HubSpot deal pipeline with stages that mirror the Salesforce stage pick-list values. This pre-work ensures the import API can write directly into the correct properties without post-migration field creation gaps.

  3. Resolve owners and validate user email matches

    Salesforce User records are matched to HubSpot users by email address.

    What this step covers

    Unmatched owners are flagged with a resolution report — your team creates HubSpot user accounts for unmatched owners or assigns a fallback HubSpot owner. No Salesforce Opportunity, Contact, or Lead is written to HubSpot without a resolved owner ID. This step runs before the main migration batch to prevent orphaned records.

  4. Migrate in dependency order: Accounts → Contacts/Leads → Opportunities

    HubSpot's association model requires Companies to exist before Contacts can be associated (via associatedcompanyid) and Companies/Contacts to exist before Deals can reference them.

    What this step covers

    FlitStack AI sequences the migration: first Accounts to Companies, then Leads and Contacts to Contacts (with lifecycle stage assignment), then Opportunities to Deals with pipeline and stage mapping. This foreign-key sequencing prevents import failures from dangling references. All objects include source_system_id__c for traceability.

  5. Run sample migration with field-level diff before full commit

    A representative slice of 100–500 records — covering at least one Lead, one Contact, one Account, one Opportunity per Salesforce record type, and a sample of tasks/events/notes — migrates first.

    What this step covers

    We generate a field-level diff report comparing source Salesforce values to destination HubSpot values for every mapped field. Your team reviews the diff to verify lifecycle stage assignment, pipeline routing, owner resolution, and custom property population. No full migration run commits until you sign off on the sample diff.

  6. Execute full migration with delta-pickup window and audit log

    The full Salesforce-to-HubSpot migration executes via Salesforce Bulk API 2.0 for large record sets and REST API for smaller objects.

    What this step covers

    A delta-pickup window of 24–48 hours captures any Salesforce records modified during the cutover. Every operation is logged: record count per object, errors, skipped records, and owner-resolved counts. One-click rollback reverts all HubSpot records to the pre-migration state if reconciliation fails. An audit summary report is delivered post-migration for your records.

Salesforce HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 50,000 recordsTypical, smaller accounts
5–10 days for over 500,000 records or heavy custom-object / multi-record-type setupsLarge or heavily customised accounts

A quote scales with three drivers: Salesforce record volume (Leads + Contacts + Accounts + Opportunities), custom field count on each object, and the number of Salesforce record types requiring separate HubSpot pipeline mapping. Orgs with more than 50 custom fields or five record types fall into the upper range because each record type demands its own pipeline design in HubSpot. Enterprise-tier setups with Salesforce custom objects (mapped to HubSpot Enterprise custom objects, capped at 10 per portal) also extend scope. A representative sample migration with field-level diff is included in every engagement to catch mapping errors before the full run commits. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Salesforce to HubSpot →

Why teams move from Salesforce to HubSpot

  • Salesforce license costs escalated beyond the value delivered for teams that only needed core CRM — $175–$350/user/month plus 8–10% annual uplift and storage overages created an unpredictable invoice. HubSpot's bundled model at $90/user/month for Sales Hub Professional with included API access was a fraction of the TCO for teams under 100 seats.
  • Salesforce's complexity required a dedicated admin or agency retainer for routine tasks — report builds, workflow edits, and user provisioning took days of specialist time. HubSpot's admin interface lets sales operations manage pipelines, properties, and reporting without external support, reducing overhead and accelerating change management cycles for growing teams.
  • Salesforce's modular architecture — requiring separate products for marketing (Pardot), AI (Einstein), and analytics (Tableau) — created a fragmented tech stack that contradicted the unified CRM promise. HubSpot's Sales Hub, Marketing Hub, and Service Hub share a single database eliminating sync failures between clouds.
  • Low Salesforce adoption in the sales team led reps to maintain shadow spreadsheets for pipeline tracking, defeating the purpose of the CRM investment. HubSpot's intuitive interface reduced onboarding time from weeks to days and increased daily active usage across the team.

Questions, answered

Salesforce to HubSpot migration questions

How long does a Salesforce Sales Cloud to HubSpot migration take?

Most Salesforce-to-HubSpot migrations complete in 48–72 hours of clock time for under 50,000 records. Orgs exceeding 500,000 records or containing more than 10 Salesforce custom objects extend to 5–10 days because HubSpot's custom object cap requires consolidation scoping before mapping can finalize. Timeline also varies based on the number of Salesforce record types and custom field complexity. The record-type-to-pipeline mapping planning step is the longest pre-migration activity and runs concurrently with HubSpot property setup to minimize overall project duration.

Will my Salesforce Flows, Process Builder, and workflow rules migrate to HubSpot?

No. FlitStack AI migrates data and schema only — Salesforce Flows, Process Builder, workflow rules, validation rules, and Apex trigger logic do not transfer. They must be rebuilt natively in HubSpot's workflow engine. We export your Salesforce automation definitions as a structured rebuild reference document listing each flow's trigger, conditions, and actions so your HubSpot admin can recreate them. Critical automation gaps (territory assignment, SLA timers, approval chains) should be identified before go-live.

What happens to Salesforce Leads in HubSpot?

Salesforce Leads become HubSpot Contacts with lifecycle_stage set to 'lead' by default. HubSpot has no separate Lead object, so all records from the Salesforce Lead table land as Contacts. The original Salesforce Lead Status is preserved as a custom property (sf_lead_status__c) on each Contact. Salesforce Leads that were converted before export land as Contacts with lifecycle_stage='customer' since conversion implies a related Opportunity was created. Your team decides whether to use HubSpot's lifecycle stage for qualification routing or rely on the preserved sf_lead_status__c property.

Can I migrate Salesforce custom objects to HubSpot custom objects?

Yes, but HubSpot caps custom objects at 10 per portal on the Enterprise tier. If your Salesforce org has more than 10 custom objects, we identify low-usage objects eligible for archival or objects with overlapping data models that can consolidate into existing HubSpot objects using a type-identifier custom property. This is a scoping decision that must happen in the planning phase — not a technical constraint we can override. Objects with many-to-many relationships to other custom objects may require HubSpot junction objects, which we design as part of the mapping plan.

How does Salesforce RecordTypeId map to HubSpot?

Salesforce RecordTypeId does not have a native HubSpot equivalent. We map each Salesforce record type to a separate HubSpot deal pipeline — a Salesforce org with three record types yields three HubSpot pipelines with independent stage sets. Stage probabilities from Salesforce are preserved as a custom number property on the deal (sf_probability__c) because HubSpot does not have a native probability field. Your team designs the HubSpot pipeline stages before migration; we deliver a record-type-to-pipeline mapping plan based on the Salesforce schema extraction.

Does the migration affect my Salesforce account during cutover?

No. FlitStack AI uses scoped read access on Salesforce via the REST and Bulk APIs — your team continues working in Salesforce during the migration. We do not write to Salesforce at any point. A delta-pickup window of 24–48 hours after the initial migration run captures records created or modified in Salesforce during the cutover period so HubSpot reflects the final state of your Salesforce data at go-live. Salesforce remains fully operational throughout.

What happens to Salesforce Campaigns and Campaign Member data?

Salesforce Campaigns and Campaign Members have no direct HubSpot equivalent. We preserve campaign names and member statuses (Sent, Responded, Converted) as custom properties on the HubSpot Contact record. Full campaign membership history requires rebuilding in HubSpot's campaign tool post-migration. We export the Salesforce Campaign and CampaignMember data as a CSV reference file your team can use to recreate campaigns in HubSpot or use for reporting outside the CRM.

How is the Salesforce Owner resolved in HubSpot?

Salesforce User records are matched to HubSpot users by email address. If a Salesforce User has no matching HubSpot user account, their records are flagged and assigned to a fallback HubSpot owner of your choice. We deliver a pre-migration owner-resolution report listing matched owners, unmatched owners, and the fallback assignment so your team can create HubSpot accounts for any unmatched owners before migration runs. No record lands in HubSpot without a resolved owner ID.

Get a quote

Moving from Salesforce to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote