HubSpot to Salesforce migration.

Why the HubSpot → Salesforce migration goes wrong

HubSpot and Salesforce share a CRM vocabulary but disagree about meaning. The bidirectional native sync is great for ongoing operations and terrible for a one-time migration. Six places it quietly breaks:

• Lifecycle stage mapping. HubSpot's Lifecycle Stage and Lead Status drive every revenue report. Salesforce uses Lead.Status, Contact + AccountId, Opportunity stage. The mapping has to be deterministic, monotonic (don't move a contact backwards), and handle the "MQL became SQL became Customer" transitions cleanly.
• Deal pipelines and stages. HubSpot lets you have multiple pipelines with different stages. Salesforce Opportunity stages are global with record-type-scoped pick-lists. The mapping must preserve close-rate analytics or sales forecasting breaks post-migration.
• Association labels. HubSpot's labeled associations (Primary Contact, Decision Maker, Influencer) don't map to Salesforce's Opportunity Contact Roles cleanly. The mapping has to preserve revenue-attribution logic or commissions misfire.
• Custom property collisions. HubSpot custom properties don't have global IDs, just internal-names that can collide on import. The discovery pass has to surface collisions before they overwrite.
• Email engagement history. Opens, clicks, replies, HubSpot's engagement timeline drives sales prioritization. Salesforce has the same data as Tasks + EngagementEvent + Pardot/Marketing Cloud objects. Most tools drop it. Sales loses two years of "this account is warm" signal.
• Workflow + sequence state. Contacts in mid-flight in HubSpot workflows or sequences have implicit state. Stopping the flows cleanly before extract, then re-enrolling deterministically post-import, is the difference between zero double-emails and a Monday-morning spam complaint.

Deliverables

• Workspace archive at completion. Your data, packaged. HubSpot API extracts, lifecycle/deal stage transforms, association label decisions, every dry-run trace, every gate decision.
• Signed audit chain. Every record movement chained via SHA-256, sealed every 256 leaves with Ed25519. Your auditor (or revenue ops lead) verifies the chain on her own laptop. Protocol published →
• Salesforce-aware mapping. Lead/Contact/Account/Opportunity graph populated coherently. Engagement history preserved as Tasks or EngagementEvent rows. Pipeline analytics still work.
• Replay manifest. Every migration is replayable. The revenue-ops review conversation that used to take six weeks runs in forty minutes.