HubSpot Salesforce Integration: What Actually Syncs

Yes. HubSpot provides a built-in, native Salesforce integration that requires no third-party middleware (like Zapier or Make). Per HubSpot documentation, setup involves installing the HubSpot integration package in Salesforce, connecting OAuth credentials with a dedicated integration user, and configuring sync rules. Data flows bidirectionally: marketing engagement, form submissions, and email analytics push from HubSpot to Salesforce Leads and Contacts, while sales pipeline stages, opportunity amounts, and closed-won status sync back to HubSpot to inform attribution and lifecycle marketing.

The integration operates across four core object pairings: Contacts to Leads/Contacts, Companies to Accounts, Deals to Opportunities, and Activities to Tasks. On the push side (HubSpot to Salesforce), records sync based on enrollment triggers or inclusion lists. On the pull side (Salesforce to HubSpot), updates stream automatically or via polling intervals (typically 10 to 15 minutes). A critical architectural detail: Salesforce requires Accounts for Contacts, so syncing a HubSpot Contact will automatically trigger Account creation or matching in Salesforce, which can create orphaned records if domain deduplication is not enforced at the gate.

The single most common operational mistake is allowing all HubSpot contacts to sync to Salesforce. Every synced record and field update consumes Salesforce API calls, and marketing contacts who simply downloaded an ebook should not become Salesforce Leads. Best-practice RevOps architecture uses a HubSpot Enrollment Inclusion List: only contacts that hit an MQL threshold, request a demo, or match target account criteria enter the sync queue. This preserves Salesforce API quotas, cuts storage costs, and keeps sales reps focused on qualified pipeline.

For every mapped field, HubSpot offers three sync behaviors: 'Prefer Salesforce unless blank', 'Always use Salesforce', and 'Two-way (most recently updated wins)'. The danger lies in 'Two-way': an outdated form submission from an old lead can overwrite a phone number or job title verified by an AE just hours earlier. Critical sales fields (Lead Status, Owner, Lifecycle Stage) must always be set to 'Prefer Salesforce', while marketing attribution fields (Original Source, Campaign Name) should be locked to 'Always use HubSpot'.

Connectors move fields; they do not extract commitments. When an AE finishes a demo or a CSM wraps a renewal call, they owe three deliverables: updated deal stages in Salesforce, follow-up cadence enrollment in HubSpot, and an executive recap. Standard syncs force reps to re-type notes across both systems. Mindlyft's A.S.T.R.A. listens to the call recording, drafts the Salesforce Opportunity fields, schedules the HubSpot sequence, and generates the customer email for 1-click human approval before anything writes to production.