Skip to content
Get a quote

HubSpot to Salesforce migration

We migrate Contacts, Companies, Deals, and Engagements from HubSpot Sales Hub into Salesforce Sales Cloud with the Lead-versus-Contact split resolved up front, Activity history preserved through the Bulk API, and every HubSpot Property mapped to a typed Salesforce field before cutover.

Short answer

FlitStack AI migrates lead or contacts, accounts, opportunities, opportunity stages and record type + sales process from HubSpot to Salesforce, 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: 4-6 weeks.

By

Source HubSpot
DestinationSalesforce
Lead or ContactAccountOpportunityOpportunity StageRecord Type + Sales Process
Mapped field by field · sample run · one-click rollback

What moves from HubSpot to Salesforce?

Moving from HubSpot Sales Hub to Salesforce Sales Cloud is a structural migration, not a record copy.

Read the full summary

HubSpot uses one unified Contact object with a Lifecycle Stage property to track pre-sale through customer; Salesforce splits unqualified prospects into Leads and qualified buyers into Contacts attached to Accounts. We resolve that split during scoping, design the matching Account-to-Contact convert rules in Salesforce, and preserve the original HubSpot Lifecycle Stage as a custom field for audit and reporting. Activity history (calls, emails, meetings, tasks) cannot move through Salesforce's CSV loader — we use the Bulk API 2.0 with chunking and parent-record resolution to preserve the full timeline against the right Contact and Opportunity. Workflows, sequences, and the HubSpot Marketing Contacts billing flag do not migrate; we deliver a written map of every automation requiring rebuild in Salesforce Flow plus a Marketing Cloud Account Engagement (Pardot) integration plan if marketing automation continues to live in HubSpot.

1:N split

Contact → Lead or Contact (split required)

HubSpot Contacts with Lifecycle Stage of subscriber, lead, or marketing qualified lead map to Salesforce Lead.

How it maps

Lifecycle Stage of sales qualified lead, opportunity, customer, evangelist, or other map to Salesforce Contact tied to an Account. We compute the split at migration time using HubSpot's lifecyclestage and hs_lead_status properties, and preserve the original Lifecycle Stage in a custom field hs_original_lifecycle__c on both Lead and Contact for audit.

1:1

Company → Account

HubSpot Company records map directly to Salesforce Account.

How it maps

The HubSpot company domain becomes the Account's Website field and is used as the dedupe key during import. Account is created before any Contact import so that the Lookup relationship is satisfied at the moment of Contact insert.

1:1

Deal → Opportunity

HubSpot Deals map to Salesforce Opportunity.

How it maps

The HubSpot dealstage property maps to Salesforce StageName, and the pipeline assignment maps to a Salesforce Sales Process or Record Type that we configure before migration. Closed-Lost reason and Closed-Won reason from HubSpot custom properties become Salesforce Loss Reason and Win Reason fields.

configuration

Deal Stage → Opportunity Stage

Each HubSpot pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the relevant stage values.

How it maps

Stage probability percentages migrate from HubSpot to Salesforce StageProbability, with rounding to the nearest Salesforce-allowed integer.

configuration

Pipeline → Record Type + Sales Process

HubSpot's multiple deal pipelines (up to 15 on Professional, 100 on Enterprise) map to Salesforce Record Types on Opportunity.

How it maps

Each Record Type gets its own Page Layout and Sales Process so that stage values stay scoped per line of business.

1:1

Lead (Sales Hub Enterprise) → Lead

HubSpot's Lead object (introduced 2023, Enterprise tier only) maps directly to Salesforce Lead.

How it maps

Lead_Status from HubSpot maps to Salesforce Lead Status with a custom field hs_lead_score__c carrying any imported scoring value.

What moves18 objects
HubSpotSalesforce
  • ContactLead or Contactsplit
  • CompanyAccount1:1
  • DealOpportunity1:1
  • Deal StageOpportunity Stagetransformed
  • PipelineRecord Typetransformed
  • LeadLead1:1

+ 12 more in the mapping below

How HubSpot and Salesforce 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.

DimensionHubSpotSalesforce
Lead vs Contact modelSingle Contact object with Lifecycle Stage propertySeparate Lead and Contact objects with explicit Convert action
Pipeline countStarter 1, Professional 15, Enterprise 100 deal pipelinesUnlimited Opportunity record types and sales processes at all paid tiers
Custom objectsEnterprise tier only ($150/seat/mo + $3,500 onboarding)Available from Professional tier ($80/user/mo) without setup fees
Pricing modelPer-seat plus Marketing Contacts metering on the marketing layerPer-user with edition tiers; storage charges for data over 10 GB org-wide
Workflow automationProperty-triggered Workflows with visual builder, gated at ProfessionalSalesforce Flow with record-triggered, scheduled, and screen flow variants from Professional
App ecosystemApp Marketplace with around 1,700 listingsAppExchange with over 9,000 listings, including ERP and CPQ depth
Activity timeline depthCalls, emails, meetings, tasks as first-class native objectsTask and Event objects with EmailMessage and ContentDocument linked separately

HubSpot to Salesforce field mapping

The 30 most-used fields of 42 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
HubSpotSalesforce
  1. firstnameContact FirstNameLead/Contact
  2. lastnameContact LastNameLead/Contact
  3. emailContact EmailLead/Contact
  4. phoneContact PhoneLead/Contact
  5. mobilephoneContact MobilePhoneLead/Contact
HubSpot fieldSalesforce fieldMappingNote
Contact.firstnameLead/Contact.FirstNamedirectTrim whitespace; Salesforce enforces 40 character limit.
Contact.lastnameLead/Contact.LastNamedirectTrim whitespace; required field on both Lead and Contact in Salesforce.
Contact.emailLead/Contact.EmaildirectLowercase and trim. Used as dedupe key. Salesforce enforces 80 character limit.
Contact.phoneLead/Contact.PhonedirectStrip formatting if Salesforce General Phone Format is enabled; otherwise pass through.
Contact.mobilephoneLead/Contact.MobilePhonedirectPhone format follows same rule as Phone.
Contact.jobtitleLead/Contact.TitledirectSalesforce limit 128 characters; truncate with audit log.
Contact.companyLead.CompanydirectLead.Company is required. For Contacts, Company resolves to AccountId via the Company-to-Account mapping.
Contact.lifecyclestageLead/Contact.hs_original_lifecycle__ctransformPreserved verbatim in a custom field. Drives the Lead-versus-Contact split routing decision.
Contact.hs_lead_statusLead.StatustransformHubSpot values (NEW, OPEN, IN_PROGRESS, OPEN_DEAL, CONNECTED, BAD_TIMING, UNQUALIFIED) map to Salesforce Lead Status picklist values that we configure to match.
Contact.hubspot_owner_idLead/Contact.OwnerIdlookupResolved via Owner-to-User mapping table by email. Unresolved owners parked for admin reconciliation.
Contact.createdateLead/Contact.CreatedDatedirectSalesforce permits setting CreatedDate during data load with the audit field create permission. Without that permission, we set hs_original_create_date__c instead.
Contact.lastmodifieddateLead/Contact.LastModifiedDatedirectSame audit-field permission applies as CreatedDate.
Contact.hs_email_optinLead/Contact.HasOptedOutOfEmail (inverse)transformHubSpot's opt-in is inverted to Salesforce's opt-out: opt-in true becomes HasOptedOutOfEmail false.
Company.nameAccount.NamedirectSalesforce limit 255 characters.
Company.domainAccount.WebsitedirectPrefix with https:// if HubSpot value lacks a scheme. Used as Account dedupe key.
Company.industryAccount.IndustrytransformHubSpot freeform industry strings normalize to Salesforce Industry picklist values. Values without a picklist match route to Other and the original text moves to hs_original_industry__c.
Company.numberofemployeesAccount.NumberOfEmployeesdirectBoth fields are integer; pass through.
Company.annualrevenueAccount.AnnualRevenuedirectSalesforce stores AnnualRevenue as currency in the org's default currency. Confirm currency before migration.
Company.cityAccount.BillingCitydirectHubSpot's single address field maps to Salesforce's billing address by default.
Company.stateAccount.BillingStatedirectValidate against Salesforce State and Country picklists if enabled in the destination org.
Company.countryAccount.BillingCountrydirectCountry picklist validation applies if State and Country picklists are enabled.
Deal.dealnameOpportunity.NamedirectSalesforce limit 120 characters.
Deal.amountOpportunity.AmountdirectCurrency field; ensure the source HubSpot deal currency matches the Opportunity currency on multi-currency Salesforce orgs.
Deal.dealstageOpportunity.StageNametransformHubSpot internal stage IDs (appointmentscheduled, qualifiedtobuy, presentationscheduled, decisionmakerboughtin, contractsent, closedwon, closedlost) map to Salesforce StageName values per the customer-approved stage matrix configured during scoping.
Deal.closedateOpportunity.CloseDatedirectDate field; both systems use ISO date format.
Deal.pipelineOpportunity.RecordTypeIdlookupEach HubSpot pipeline maps to a Salesforce Opportunity Record Type configured before migration. The Record Type controls the available Sales Process (stage values) and page layout.
Deal.hs_deal_stage_probabilityOpportunity.ProbabilitydirectPercent value 0-100. Salesforce computes Probability from StageName by default; we override with the HubSpot stage probability so historical Deals preserve their forecast value.
Deal.hs_priorityOpportunity.hs_original_priority__ctransformHubSpot priority (low, medium, high) preserves in a custom field because Salesforce Opportunity has no native priority equivalent.
Deal.hubspot_owner_idOpportunity.OwnerIdlookupResolved via Owner-to-User mapping by email match.
Engagement (Email).hs_email_subjectEmailMessage.SubjectdirectSalesforce limit 1,000 characters.

What to watch for in a HubSpot to Salesforce migration

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

high

Lead vs Contact split has no automated answer

HubSpot's single Contact object with a Lifecycle Stage property does not have a direct Salesforce equivalent.

How we handle it

Salesforce expects unqualified prospects to live as Leads and qualified buyers as Contacts attached to Accounts. We define the split rule during scoping based on the customer's Lifecycle Stage matrix, run it as the first transform during migration, and preserve the original Lifecycle Stage in a custom field on both Lead and Contact for audit. Migrations that skip this design step end up with Contacts that have no Account (orphaned) or Leads that should have been converted on day one.

high

HubSpot Workflows do not migrate to Salesforce Flow

HubSpot Workflows and Salesforce Flow are different automation models.

How we handle it

HubSpot uses property-triggered branching with built-in delays and CRM actions; Salesforce Flow uses record-triggered, scheduled, and screen variants with different action types and limits. We do not migrate Workflows as code. We deliver a written inventory of every active HubSpot Workflow with its trigger, conditions, actions, and recommended Salesforce Flow equivalent, and the customer's admin or a Salesforce partner rebuilds them post-migration. Sequences (sales engagement cadences) do not migrate either.

high

Activity history exceeds CSV loader capacity

Salesforce's Data Loader and Data Import Wizard are not suitable for large engagement migrations.

How we handle it

A mid-market HubSpot account typically has hundreds of thousands of email, call, meeting, and task records. We use the Salesforce Bulk API 2.0 with batch chunking, parent-record lookup resolution (WhoId, WhatId, AccountId), and exponential backoff on API limit responses. Without Bulk API, migrations either time out or silently drop activity records, breaking the historical timeline that sales reps rely on.

medium

Salesforce field-level security and validation rules can block import

Salesforce orgs commonly enforce validation rules (required formats, conditional requireds, picklist whitelists) and field-level security that the migrating user must explicitly bypass during data load.

How we handle it

We coordinate with the customer's Salesforce admin to grant the migration user Modify All Data and the relevant Bulk API permission, and we either temporarily disable validation rules during load or extend them with a migration-context check. Skipping this step results in 5-30 percent record rejection on the first import attempt.

medium

Marketing Contacts billing flag has no Salesforce analog

HubSpot's Marketing Contacts billing model (a flag that determines whether the contact counts against the marketing-priced contact tier) has no direct Salesforce equivalent.

How we handle it

Sales Cloud uses per-user licensing instead of per-contact. If the customer also uses HubSpot Marketing Hub or moves marketing automation to Salesforce Marketing Cloud Account Engagement (Pardot) or Marketing Cloud, we map opt-in status to HasOptedOutOfEmail and CampaignMember Status. Email subscription preferences migrate to Salesforce subscription management or Pardot Prospect equivalents.

How the migration runs

  1. Discovery and edition selection

    We audit the source HubSpot portal across tier (Starter/Professional/Enterprise), custom properties, custom objects, pipeline count, active sequences, active workflows, and engagement volume.

    What this step covers

    We pair this with a Salesforce edition decision: Professional ($80/user) covers most custom-object-free migrations; Enterprise ($165/user) is required if the customer needs record-triggered Flow at scale, advanced reporting types, or Process Builder; Unlimited ($330/user) only if 24x7 support and unlimited custom apps are required. The discovery output is a written migration scope and a Salesforce edition recommendation.

  2. Schema design and Lead-Contact split rule

    We design the destination schema in Salesforce.

    What this step covers

    This includes provisioning custom objects (with __c API names matched to HubSpot custom object names), custom fields (with type-mapped Salesforce field types), Record Types (one per HubSpot pipeline), Sales Processes (stage whitelist per Record Type), Page Layouts (per Record Type), and the Lead-Contact split rule based on the customer's Lifecycle Stage matrix. Schema is deployed via Salesforce metadata API or change set into a Sandbox org first for validation.

  3. Sandbox migration and reconciliation

    We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-like data volume.

    What this step covers

    The customer's RevOps lead reconciles record counts (Contacts in, Leads in, Accounts in, Opportunities in, Activities in), spot-checks 25-50 random records against the HubSpot source, and signs off the schema and mapping before production migration begins. Any mapping corrections happen here, not in production.

  4. Owner reconciliation and User provisioning

    We extract every distinct HubSpot Owner referenced on Contact, Company, Deal, and Engagement records and match by email against the Salesforce destination org's User table.

    What this step covers

    Owners without a matching User go to a reconciliation queue. The customer's Salesforce admin provisions any missing Users (active or inactive depending on whether the original HubSpot user is still active). Migration cannot proceed past this step because OwnerId references are required on most standard objects.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Users (manual provisioning, validated), Accounts (from HubSpot Companies), Contacts (with AccountId resolved), Leads (with the Lifecycle Stage split applied), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Products and Pricebook entries (if migrating quoting), Line Items, Quotes, Activity history (Tasks, Events, EmailMessages, Notes via Bulk API 2.0), Custom Objects (last, because they often have lookups to standard objects).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and Workflow rebuild handoff

    We freeze HubSpot writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.

    What this step covers

    We deliver the Workflow and Sequence inventory document to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's sales team. We do not rebuild HubSpot Workflows as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.

HubSpot Salesforce
  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 · SalesforceRollback 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

4-6 weeksTypical, smaller accounts
10-16 weeksLarge or heavily customised accounts

A quote scales with record volume, custom object count, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for HubSpot to Salesforce →

Why teams move from HubSpot to Salesforce

  • Teams outgrow HubSpot's pipeline ceiling. Starter is capped at one Deal pipeline and Professional at fifteen, which forces multi-line-of-business companies onto Enterprise at $150 per seat plus a $3,500 onboarding fee. Salesforce Sales Cloud at Professional ($80/user) supports unlimited record types and sales processes, removing the pipeline cliff that triggers the switch.
  • Custom objects are Enterprise-only in HubSpot. Reviewers on G2 and Capterra cite this as the reason mid-market teams move when their data model requires a custom record type (Projects, Subscriptions, Vehicles, Properties). Salesforce supports custom objects from Professional tier without setup fees, which lowers the total cost of ownership for data-model-heavy use cases.
  • Salesforce's AppExchange has over 9,000 listings versus HubSpot's roughly 1,700. Companies needing native CPQ, ERP, contract lifecycle management, or revenue intelligence integrations (DocuSign CLM, Conga, Apttus, Workday, NetSuite, SAP) move to Salesforce because the integrations are first-party or AppExchange-certified rather than third-party Zapier-routed.
  • Enterprise revenue operations teams cite Salesforce's reporting engine as more flexible for multi-dimensional pipeline analysis across territories, product lines, custom fiscal periods, and non-standard attribution models. HubSpot's reporting suits inbound and marketing-sourced analysis but constrains complex slicing without exporting to a data warehouse.
  • Marketing Contacts billing surprises drive churn at scale. Reviewers consistently note that all imported contacts default to marketing-billed status unless explicitly flagged, multiplying the monthly bill 3-4x for teams with large contact databases. Salesforce's per-user model is more predictable for large sales teams even at higher per-seat prices.

Questions, answered

HubSpot to Salesforce migration questions

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

Most migrations land between four and six weeks for accounts under 25,000 Contacts and 5,000 Deals with no custom objects and a clean Lifecycle Stage matrix. Migrations with custom objects, multi-pipeline Deal structures, large engagement histories (over 500,000 activity records), or multi-org destinations move to ten to sixteen weeks because of Bulk API time, Flow rebuild scope, and Lead-versus-Contact reconciliation.

Do my HubSpot Workflows, Sequences, and Forms migrate to Salesforce?

No. HubSpot Workflows and Salesforce Flow are structurally different automation models, and Sequences are a sales engagement cadence feature that has no direct Salesforce Sales Cloud equivalent. We do not migrate them as code. We deliver a written inventory of every active Workflow and Sequence with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent (or a Sales Engagement Cadence equivalent if the customer licenses Sales Engagement). The customer's admin or a Salesforce partner rebuilds them post-migration. Forms similarly do not migrate; we recommend Salesforce Web-to-Lead or a customer portal Experience Cloud form as the replacement.

Can we keep HubSpot Marketing Hub while moving Sales to Salesforce?

Yes. A hybrid stack is one of the most common patterns we migrate. HubSpot Marketing Hub continues to handle inbound, email marketing, and lead capture; Salesforce Sales Cloud handles the sales process from Lead conversion onward. We configure the HubSpot-to-Salesforce native sync (a HubSpot-built bidirectional integration) during migration so that new HubSpot Leads flow into Salesforce Leads, and Salesforce Contacts and Opportunities sync back to HubSpot for marketing attribution. The customer continues paying for HubSpot Marketing Contacts at the marketing layer while moving sales seat licensing to Salesforce.

Do we lose historical engagement data (calls, emails, meetings, tasks)?

No. We migrate the full engagement history through the Salesforce Bulk API 2.0 with parent-record resolution. Emails land as EmailMessage records linked to Tasks; calls land as Task with TaskSubtype=Call and CallDurationInSeconds preserved; meetings land as Event records; tasks land as Task. Activity timeline ordering is preserved by setting ActivityDate to the original HubSpot timestamp. Notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity.

How do we handle the HubSpot Marketing Contacts billing flag during migration?

The Marketing Contacts flag is HubSpot-specific and has no Salesforce analog because Salesforce Sales Cloud uses per-user licensing instead of per-contact. We preserve the flag value in a custom field hs_marketing_contact__c on the migrated Lead or Contact so that if the customer later returns to a marketing automation tool (Salesforce Marketing Cloud Account Engagement, Marketing Cloud, or another platform), they can re-segment. Email opt-in and opt-out preferences migrate to Salesforce HasOptedOutOfEmail and to CampaignMember Status if the customer maintains campaign membership history.

Can FlitStack AI also handle the HubSpot Marketing to Salesforce Marketing Cloud Account Engagement (Pardot) migration?

Yes. We treat the Marketing Hub to Marketing Cloud Account Engagement (Pardot) migration as a parallel scope. Pardot uses a Prospect data model that sits alongside Salesforce Lead and Contact, with Visitor Activities replacing HubSpot's lifecycle interaction history. We migrate Prospects, Lists (to Pardot Lists), Forms (to Pardot Forms), and Email Templates (with Engagement Studio rebuild documented separately because Engagement Studio is a different cadence model from HubSpot Workflows). We do not rebuild HubSpot landing pages as Pardot landing pages; that work is handled by a marketing implementation partner.

Get a quote

Moving from HubSpot to Salesforce?

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

Get a quote