Migrate from Salesforce Sales Cloud to HubSpot

Salesforce Leads have no direct HubSpot equivalent — HubSpot has one Contact object. 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.

Salesforce Contacts migrate directly to HubSpot Contacts. 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.

Salesforce Accounts map 1:1 to HubSpot Companies. 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.

Salesforce Opportunities map to HubSpot Deals. 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.

Each Salesforce record type becomes a separate HubSpot deal pipeline. 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.

Salesforce's Account Contact Relations support N:N contact-to-account associations natively. 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.

Salesforce Tasks with Type='Email' migrate as HubSpot email activities on the contact timeline. The original Subject, Body (plain text), and ActivityDate are preserved. Salesforce Tasks with IsTask=true and no Type map to HubSpot generic activities. HTML email bodies are converted to plain text for the HubSpot activity record.

Salesforce call tasks migrate to HubSpot call activities. The Call Duration (DurationInSeconds) and Call Type (Inbound/Outbound) map to HubSpot's call duration and call direction properties. Subject and original owner are preserved on the activity record. All call metadata including disposition notes are transferred to maintain complete communication history.

Salesforce Events map to HubSpot meeting activities with the original StartDateTime, EndDateTime, Subject, and location preserved. The Event's WhatId (related-to record) maps to the equivalent HubSpot association. Recurring events are imported as a series of individual HubSpot meeting activities, one per occurrence.

Salesforce Notes migrate to HubSpot notes on the contact or company timeline. Content (Body) is preserved. Salesforce Files attached to records are downloaded and re-uploaded to HubSpot's file storage; the HubSpot file URL is associated with the original record. File size limits (25MB per Salesforce file) are respected during re-upload.

Salesforce User records are resolved by email match to existing HubSpot users. Unmatched owners are flagged before migration runs; your team either creates HubSpot user accounts first or assigns those records to a fallback HubSpot owner. No Salesforce Opportunity or Contact lands in HubSpot without a resolved owner.

Salesforce custom objects map to HubSpot Enterprise custom objects 1:1. HubSpot caps custom objects at 10 per portal — if your Salesforce org exceeds this, we identify low-usage custom objects for consolidation into existing HubSpot objects or archival before migration begins. This is a scoping decision that must happen in the planning phase.

Salesforce Campaigns and Campaign Members have no direct HubSpot equivalent. HubSpot stores campaign membership through lists and the marketing contact model. We preserve campaign names and member statuses as a custom reference property on the Contact record; full campaign history requires rebuilding in HubSpot's campaign tool post-migration.

Salesforce Opportunity Contact Roles migrate as deal-contact associations in HubSpot. The Role field value (e.g., Decision Maker, Technical Buyer) maps to the HubSpot contact's association label on the deal. Multiple roles per contact are preserved, and all role variations attached to a single opportunity are transferred to maintain complete buying committee context.

Salesforce field history tracking records (e.g., stage changes, amount changes) migrate as time-stamped custom properties on the HubSpot deal. For stage history specifically, we populate Stage_History__c as a multi-value text property listing the sequence of stages with dates. This preserves the complete audit trail of all field modifications made within Salesforce for compliance and historical analysis.