Connecting HubSpot and Salesforce looks simple in the marketing screenshots — install a package, click connect, done. In practice, the order you do things in decides whether the integration runs cleanly for years or floods both systems with duplicate and mismatched records on day one.
This guide walks through installing and setting up the native HubSpot-Salesforce integration in the right sequence: what to check before you start, how to install the connector, how to configure field mappings and sync rules, why selective sync and inclusion lists matter, and the setup pitfalls that cause the most rework. It applies to businesses in any industry running both platforms.
The HubSpot-Salesforce integration is HubSpot's native data sync connector that keeps contacts, companies, deals, and activities aligned between the two CRMs. It matters for any organization where marketing runs in HubSpot and sales runs in Salesforce and the two need to share the same records. This article helps you decide what to set up first — prerequisites, connector install, field mappings, sync rules, and a selective inclusion list — and why sandbox-first testing prevents a messy initial sync. Vantage Point plans and implements these connections through CRM and integration work on both platforms.
The HubSpot-Salesforce integration is a native, supported connector — sometimes called HubSpot data sync — that synchronizes records between the two CRMs. It maps HubSpot contacts, companies, and deals to Salesforce leads/contacts, accounts, and opportunities, and keeps selected fields and activities aligned in the direction you choose.
It is installed as a managed package on the Salesforce side and configured from HubSpot. No middleware or custom API code is required for standard objects, which makes it the default starting point for most HubSpot + Salesforce setups.
The integration itself is reliable. Most failed implementations are not connector problems — they are sequencing problems. Teams enable the sync before deciding which records should flow, and within minutes both systems fill with leads, duplicates, and overwritten fields.
Getting the order right protects you from the four most common failures:
A disciplined setup sequence — tested in a sandbox first — prevents nearly all of these.
Follow these steps in order. Do not enable the production sync until the earlier steps are confirmed.
Before installing anything, verify:
Install the HubSpot integration package into a Salesforce sandbox, connect it via OAuth, and add the HubSpot Visualforce module to the relevant lead, contact, account, and opportunity page layouts. Validating here means a misconfiguration never reaches live records.
Map the object relationships before turning on any data flow:
| HubSpot object | Salesforce object | Typical sync direction |
|---|---|---|
| Contact | Lead or Contact | Bidirectional |
| Company | Account | Bidirectional |
| Deal | Opportunity | Often HubSpot → Salesforce or bidirectional |
| Activities / tasks | Activities | One-way into the system of record |
For each mapped field, choose the sync behavior deliberately:
Keep the initial mapping set lean. Map the fields the business actually uses, confirm they sync correctly, then expand. For deeper guidance on directions and conflict handling, see our companion guide on HubSpot-Salesforce sync rules and field mappings.
This is the single most important control. In HubSpot, create an active list that defines exactly which contacts are allowed to sync to Salesforce, and set it as the integration's inclusion list. Only records that meet your criteria flow across — for example, marketing-qualified leads rather than every contact in the database. Without an inclusion list, the default behavior can sync far more than you intend.
Once mappings and the inclusion list are validated in the sandbox:
After go-live, review the integration's sync health and error logs. Watch for records failing on required fields, validation rules, or duplicate conflicts, and resolve mapping issues before they accumulate.
| Pitfall | What happens | How to avoid it |
|---|---|---|
| No inclusion list | Unqualified records flood Salesforce | Build a HubSpot active list and set it as the inclusion list before enabling sync |
| Wrong "preferred" system | Good data gets overwritten | Choose the system of record per field and set conflict rules intentionally |
| Picklist mismatches | Values rejected or duplicated | Align picklist values and field types across both platforms first |
| Skipping the sandbox | Errors hit live data | Install and test in a Salesforce sandbox before production |
| Syncing dirty data | Duplicates spread to both systems | Deduplicate and standardize before the initial sync |
| Mapping everything at once | Hard to diagnose failures | Start with core fields and objects, then expand |
If your team is planning or troubleshooting this connection, Vantage Point can assess your HubSpot and Salesforce setup and build a practical, low-risk implementation plan.
Vantage Point is a senior-led, US-based, employee-owned consultancy and HubSpot Gold Partner that implements HubSpot and Salesforce together every day. We treat the integration as a data and process project, not just a package install.
Our VALUE Methodology keeps the work focused on the outcomes that matter to your sales and marketing teams. To understand how the two CRMs structure data differently before you map fields, read our guide on HubSpot and Salesforce data model differences. If your team is evaluating the connector, an integration and implementation assessment is the fastest way to confirm the right setup before you go live.
It is HubSpot's native data sync connector that keeps records aligned between HubSpot and Salesforce. It maps contacts, companies, deals, and activities between the platforms and syncs selected fields in the direction you configure, without custom code for standard objects.
You need a HubSpot paid tier that includes the Salesforce connector, a Salesforce edition with API access (Enterprise and Unlimited include it; Professional usually needs the API add-on), and admin permissions in both systems. A Salesforce sandbox is strongly recommended so you can test before touching live data.
An inclusion list is a HubSpot active list that defines exactly which contacts are allowed to sync to Salesforce. It is the main control for preventing unqualified or junk records from flooding Salesforce. Setting it before enabling the sync is one of the most important setup steps.
Yes. Installing the connector and testing field mappings and the inclusion list in a Salesforce sandbox lets you catch picklist mismatches, overwrites, and validation errors before they reach production records. Skipping this step is a leading cause of messy initial syncs.
Confirm prerequisites, install the package in a sandbox, decide which objects to sync, configure field mappings and directions, set an inclusion list, clean existing data, then enable the production sync one object at a time. Doing these out of order is what creates duplicates and overwrites.
For each bidirectional field you designate a preferred system that wins when values differ. Fields that only one platform should own can be set to one-way sync. Choosing these rules deliberately prevents the connector from overwriting good data.
It can if matching logic, picklist values, or field types are misaligned, or if dirty data is synced as-is. Deduplicating both systems before the initial sync and aligning field values during setup prevents most duplicates. Reviewing sync error logs after go-live catches the rest.
No, not for standard objects. The native connector handles contacts, companies, deals, and activities directly. Middleware is only needed for complex, high-volume, or multi-system scenarios that go beyond what the native sync supports.