Installing the HubSpot-Salesforce integration takes minutes — but deciding what syncs, in which direction, and who wins a conflict is the work that determines whether you end up with one clean source of truth or two CRMs fighting each other. You install the integration through HubSpot's connector by authenticating your Salesforce account, then configuring the sync settings and field mappings that control exactly what flows between the two systems. The install is the easy 20%; the sync rules are the 80% that decide whether your data stays trustworthy. Here's the practitioner's read on doing it right the first time.
Confirm your permissions, your Salesforce edition, and a clear plan for which system owns which data — before you connect anything. You'll need admin access in HubSpot and a Salesforce edition that allows API access, plus the Salesforce credentials to authenticate. More important than the technical checklist is the decision nobody wants to make first: which system is the source of truth for contacts, for accounts, for opportunities. Worked example: a team installs the connector without deciding this, lets everything sync both ways, and within a week a rep's edit in Salesforce overwrites a marketing update in HubSpot — and vice versa — until no one trusts either record. Decide ownership first, then install.
You add the Salesforce integration from HubSpot's app marketplace, authenticate your Salesforce account, install HubSpot's managed package in Salesforce, and run the guided setup. The flow walks you through connecting the accounts, installing the package that lets the two systems talk, and choosing your initial sync settings. Take the guided setup slowly — the defaults it offers are a starting point, not a finished configuration. The connector will offer to begin syncing contacts and other objects; resist the urge to turn everything on at once. Start with one object, confirm it behaves, then expand. A staged install is far easier to debug than a big-bang sync that floods both systems on day one.
Map only the fields you truly need, set a clear sync direction for each, and decide which system wins when both change the same field. For every mapped field you choose: does it sync both ways, or one way, and if a value differs in each system, which one is authoritative. This is where data discipline lives. Worked example: you set lifecycle-driving fields to sync HubSpot-to-Salesforce one way (marketing owns them), opportunity amounts to sync Salesforce-to-HubSpot one way (sales owns them), and only a handful of shared fields to sync both ways with a clear winner. Mapping every field bidirectionally feels thorough but creates exactly the conflicts you're trying to avoid. Less mapping, clearer rules.
Test on a small inclusion list first, watch the sync logs, and expand only once you trust the behavior. HubSpot lets you control which records sync using an inclusion list, so you don't have to expose your entire database on day one. Start with a small, safe set of records, push a few changes from each side, and confirm they land correctly with no surprise overwrites. Check the sync activity and error logs — they tell you when a field failed to map or a record bounced. Only after a clean test do you widen the inclusion list. The teams that skip the test phase are the ones who spend the following month untangling duplicates and overwritten data.
The HubSpot-Salesforce integration is one of the most useful connections in B2B — and one of the easiest to break, because the install is trivial and the governance is hard. Two-way sync on everything is the single most common mistake we clean up; it turns two systems into a tug-of-war. The right setup is mostly one-way rules with a few deliberate exceptions, a small inclusion list to start, and a written agreement on which team owns which field. Get the governance right and the integration quietly does its job for years. Get it wrong and you'll be reconciling records forever.
Planning or fixing a HubSpot-Salesforce sync? Book a 30-minute portal audit — we'll tell you straight whether your sync rules will hold up, and what to fix before they cause damage. For the bigger picture, see how we approach CRM and platform integrations.
Which Salesforce editions support the HubSpot integration?
You need a Salesforce edition that allows API access, since the sync runs over the API. Confirm your edition and API limits before installing, as heavy syncs consume API calls.
Can I control which records sync instead of syncing everything?
Yes — HubSpot's inclusion list lets you sync only the records that match your criteria. Starting with a small inclusion list is the safest way to roll out the integration.
What happens if the same field is edited in both systems?
The outcome depends on your sync direction and conflict settings. That's why you decide per field which system is authoritative, rather than letting everything sync both ways and hoping for the best.
Will installing the integration create duplicate records?
It can if your data isn't clean first — duplicates in either system tend to multiply across the sync. Deduplicate before you connect, and start with a small inclusion list so you can catch issues early.