What Is the HubSpot Salesforce Connector?
The HubSpot Salesforce connector is HubSpot’s native managed package — installed directly into your Salesforce org — that enables bidirectional data sync between HubSpot and Salesforce. It syncs contacts, companies, deals, tickets, and activities at a fixed 15-minute interval. It requires a HubSpot Professional or Enterprise subscription and a Salesforce edition with API access.
The connector is distinct from the broader concept of a HubSpot-Salesforce integration. An integration describes the data relationship between the two platforms. The connector is the specific technical component that makes that relationship function — a package installed in Salesforce, configured and monitored from HubSpot.
What the HubSpot Salesforce Connector Actually Is
Most guides use “integration” and “connector” interchangeably. They are not the same thing, and the distinction matters for troubleshooting and administration.
The connector refers to HubSpot’s Salesforce managed package (current version: v3.0.1). When installed, it creates several components inside your Salesforce org: custom fields, workflow triggers, and the interface layer that allows HubSpot and Salesforce to pass data. The installation, configuration, and ongoing management all happen from HubSpot’s side — not from Salesforce.
HubSpot Embed is the companion in-record panel. When a Salesforce user opens a contact or lead record, the HubSpot Embed panel shows that contact’s HubSpot activity — email opens, form submissions, page views. Note: HubSpot’s legacy Visualforce module is being deprecated. If your org is still running the Visualforce version, HubSpot recommends uninstalling it and switching to HubSpot Embed.
The integration is the broader data architecture: which records sync, in which direction, under which conditions, and how field values map between HubSpot properties and Salesforce fields. The connector enables the integration; it doesn’t define it.
Prerequisites: What You Need Before Installing
The HubSpot Salesforce connector has specific requirements on both sides. Attempting installation without meeting all of them produces either a hard failure or a partially-functioning integration that silently drops data.
HubSpot requirements
- A HubSpot Professional or Enterprise subscription on any Hub (Marketing, Sales, Service, Data, or Content). The free and Starter tiers do not support the Salesforce connector.
- Account Access permissions in HubSpot for the user performing the installation.
Salesforce requirements
- A Salesforce edition with API access — this includes Enterprise, Unlimited, Developer, and Performance editions, plus Salesforce Professional with the API add-on.
- Salesforce Group Edition is not supported.
- Salesforce Government Cloud is supported.
- The installing user must be a Salesforce System Administrator.
- The installing user’s profile must have all of the following permissions enabled:
- API Enabled
- View Setup and Configuration
- Modify All on any object you plan to sync (Accounts, Campaigns, Contacts, Leads, or Opportunities)
- Modify Metadata permission (required to display the HubSpot Embed panel on Salesforce records)
- Download AppExchange Packages (required for connector package installation — the most common cause of the “Insufficient Privileges” installation error)
Multiple HubSpot accounts
If your organisation runs multiple HubSpot accounts, they can all connect to a single Salesforce org. Each connection is managed separately from within each HubSpot account.
Object Sync Inventory: What Syncs and How
| Object | Direction | Notes |
|---|---|---|
| Contacts | Bidirectional | Core of the integration; primary record type |
| Companies ↔ Accounts | Bidirectional | Requires an associated Contact to prevent duplicates |
| Deals ↔ Opportunities | Bidirectional | Lifecycle stage mapping required |
| Tickets ↔ Cases | HubSpot → Salesforce | Limited bidirectional support |
| Activities (emails, calls, meetings) | HubSpot → Salesforce | Logged against the associated Contact |
| Campaign and list membership | HubSpot → Salesforce | Used for campaign influence reporting |
| Task creation | Bidirectional | Workflow-triggered tasks sync in both directions |
| Custom objects | Limited bidirectional | Requires Professional or Enterprise; expanded in 2026 but not feature-complete |
Sync frequency: The connector checks for new or updated sync-eligible data every 15 minutes. This interval is fixed — it cannot be reduced or made real-time through any configuration change within the native connector. Records do not sync automatically on installation; they sync based on triggers (new record creation, field updates, lifecycle stage changes) or a manual sync command.
Initial sync duration: Depends on database size and your Salesforce API allocation. A database of 50,000 contacts typically takes several hours for the initial sync to complete.
What does not sync natively: Products, Line Items, Price Books, and complex multi-level object relationships do not sync through the native connector. These require either Operations Hub custom code workflows or a third-party integration tool.
Step-by-Step Setup and the Lead/Contact Decision
Installation steps
Step 1. In HubSpot, click the Marketplace icon in the top navigation bar, select HubSpot Marketplace, search for Salesforce, and click Install.
Step 2. Authenticate with your Salesforce credentials. You must be a Salesforce System Administrator with all required permissions enabled (see Prerequisites above).
Step 3. Make the Lead/Contact decision (see section below — do not skip this).
Step 4. Configure inclusion lists. These determine which HubSpot records are eligible to sync to Salesforce. Without an inclusion list, all contacts sync, which can overwhelm your Salesforce org with early-funnel records that sales don’t need to see.
Step 5. Configure field mappings. Map HubSpot properties to Salesforce fields. Verify type compatibility before saving — field type mismatches are the leading cause of sync errors post-installation.
Step 6. Test in your Salesforce sandbox before enabling the production connection. Confirm a small set of records syncs correctly and that field values appear in the expected locations in both systems.
Step 7. Enable the connection for your full dataset. Monitor the sync error log in HubSpot (Settings > Integrations > Salesforce > Sync errors) for the first 48 hours.
The Lead/Contact architecture problem
This is the most consequential decision in the setup and the one most guides bury or skip.
Salesforce uses two separate objects to represent people: Leads and Contacts. Leads are unqualified prospects. When a Lead is qualified by sales, Salesforce converts them into a Contact plus an associated Account and Opportunity. Contacts in Salesforce are people who have a formal relationship with an Account.
HubSpot uses one object: Contacts. There is no Lead object in HubSpot.
When a HubSpot contact syncs to Salesforce for the first time, the native connector must create a Salesforce record. You must choose: does it create a Lead or a Contact? The native connector creates one or the other — not both concurrently.
If you choose Lead creation: Marketing-qualified records go to Salesforce as Leads, which matches the typical MQL handoff process. When sales qualifies the Lead and converts it in Salesforce, the record becomes a Contact. The HubSpot sync continues correctly post-conversion. This is the most common and most appropriate configuration for marketing-led growth teams.
If you choose Contact creation: All syncing records arrive in Salesforce as Contacts, requiring an associated Account. This suits teams where every HubSpot record is already a known customer. Without the Account association, deduplication breaks and the connector creates duplicate records.
The practical implication: If you choose Lead creation and a contact already exists in Salesforce (as a Contact, not a Lead), the connector uses HubSpot-Salesforce Contact associations to deduplicate. Without those associations, the connector creates duplicates. Establish your deduplication rules before the first sync runs.
Connector Limitations: What It Cannot Do
The following limitations apply to the native HubSpot Salesforce connector as of 2026. Understanding them before implementation prevents the most common post-setup failures.
No real-time sync. The 15-minute interval is baked into the connector architecture. It cannot be shortened. If your sales process depends on immediate data availability — for example, auto-routing a lead the moment it hits a threshold score — the native connector will introduce a 0–15-minute lag. Real-time sync requires a third-party tool with webhook-based triggers or a custom API integration.
Salesforce Group Edition is not supported. If your Salesforce org is on Group Edition, the connector cannot be installed. You need to upgrade the Salesforce edition or use a third-party tool.
Custom object support is limited. As of early 2026, HubSpot expanded its custom object sync capabilities but it does not match what third-party tools offer. If custom objects are central to your Salesforce data model — particularly custom object relationships and parent-child hierarchies — evaluate whether the native connector’s current custom object support meets your actual requirements before committing to it.
No complex data transformation. The connector maps fields one-to-one. It does not concatenate fields, apply conditional logic, reformat values, or transform data types during sync. If your field values need processing before landing in the destination system, you need Operations Hub custom code workflows or a third-party integration layer.
Field type constraints. Not all Salesforce field types are compatible with HubSpot property types. Mismatched types cause sync errors. The most common incompatibilities: Salesforce restricted picklists mapped to HubSpot open text fields, multi-select picklists synced to single-value dropdowns, and formula fields treated as writable properties.
Sync errors are not retroactive. When a sync error occurs, the affected record is not re-queued automatically when you fix the underlying problem. After resolving a field mapping error or permission issue, you must manually trigger a re-sync for the affected records.
Decision Framework: Native Connector vs. Third-Party vs. Custom API
The native connector is the right starting point for most teams. It is also regularly the wrong long-term answer as data models grow. Here is how to assess which approach fits your situation.
Use the native connector when
- You are syncing standard objects only: contacts, companies, deals, and activities
- Your contact database is under 100,000 records
- A 15-minute sync interval has no meaningful business impact on your processes
- Your Salesforce data model is standard — no complex custom object hierarchies
- You need to be operational quickly (the native connector installs in 2–4 hours for standard configurations)
Consider a third-party tool (Workato, MuleSoft, Skyvia, Stacksync) when
- Custom objects are central to your data model. If your Salesforce org has custom objects that hold critical business data — product registrations, project records, subscription details — and those need to sync to HubSpot, evaluate third-party tools before committing to the native connector.
- Real-time sync is a process requirement. Sales routing, lead scoring triggers, or SLA-based workflows that depend on immediate data availability need webhook-based triggers that third-party tools provide.
- You need multi-system orchestration. If HubSpot and Salesforce are two of several systems — ERP, support platform, e-commerce — and data needs to route between all of them, a middleware integration platform is the appropriate architecture.
- You need conditional field-level sync logic. Sending different values to Salesforce based on record conditions, or routing records differently based on their properties, requires a tool that supports sync rules and conditional mapping.
Consider a custom API integration when
- Your integration requirements are unique enough that no commercial tool models them
- You need full audit-level control over every data movement
- Your engineering team has the capacity to build and maintain it
- The integration volume or frequency exceeds what managed tools handle cost-effectively
The financial case for starting native: the HubSpot Salesforce connector is included with Professional and Enterprise HubSpot subscriptions — there is no additional connector fee. Third-party integration platforms add $200–$2,000/month depending on data volumes and features. Start native, monitor closely, and migrate to a third-party tool only when you hit a specific constraint that the native connector demonstrably cannot solve.
Common Connector Failures and Fixes
“Insufficient Privileges” during installation Cause: The Salesforce user installing the connector does not have the Download AppExchange Packages permission. Fix: Enable the Download AppExchange Packages permission on the user’s Salesforce profile, then retry installation.
Company records not syncing or creating duplicates Cause: HubSpot company sync requires an associated Contact record. Companies without an associated Contact create duplicate Account records because the deduplication logic relies on Contact-Account association data. Fix: Ensure all syncing companies have at least one associated HubSpot contact. Audit for companies without contact associations before enabling company sync.
Contact field not updating in Salesforce Cause: Either the Salesforce field has field-level security restrictions that prevent the integration user from writing to it, or the HubSpot property mapped to it is read-only. Fix: Check Salesforce field-level security for the integration user profile. Check whether the HubSpot property is system-managed (hs_ prefix properties are frequently read-only).
Initial sync stalled or incomplete Cause: Salesforce API call limits exceeded. Large databases consume significant API allocations during initial sync. Fix: Check Salesforce API usage in Setup > System Overview. If limits are reached, sync resumes automatically the following day when the limit resets. Consider increasing API limits (Enterprise/Unlimited editions have higher allocations) or running the initial sync in batches using inclusion lists.
Records not appearing in Salesforce Cause: The contact is not meeting your inclusion list criteria. Fix: In HubSpot, open the contact record and check whether the Salesforce sync panel shows “Not in sync” and the reason. Adjust the inclusion list criteria or manually add the record.
Frequently Asked Questions
What is the HubSpot Salesforce connector?
The HubSpot Salesforce connector is HubSpot’s native managed package, currently at version 3.0.1, that installs in your Salesforce org and enables bidirectional data synchronisation between HubSpot and Salesforce. It requires a HubSpot Professional or Enterprise subscription and a Salesforce edition with API access. It syncs at a fixed 15-minute interval.
Does the HubSpot Salesforce connector work in real time?
No. The native connector syncs on a fixed 15-minute interval that cannot be changed. Records do not push immediately on creation or update. For real-time sync, you need either a third-party integration platform with webhook support or a custom API integration.
What HubSpot subscription do I need for the Salesforce connector?
HubSpot Professional or Enterprise on any Hub — Marketing, Sales, Service, Data, or Content. The connector is not available on HubSpot Free or Starter plans.
Does the HubSpot Salesforce connector support custom objects?
Partially. As of 2026, HubSpot has expanded custom object sync support, but it does not cover complex custom object hierarchies or multi-level relationships. If custom objects are central to your Salesforce data model, evaluate whether the current native connector support meets your specific requirements before deciding against a third-party tool.
Should HubSpot create Leads or Contacts in Salesforce?
Choose Lead creation if your team uses the Lead object for initial prospect management and converts Leads to Contacts after qualification — this is the standard MQL handoff model. Choose Contact creation if all syncing records are already known customers with associated Accounts. The native connector creates one or the other, not both.
Which Salesforce editions are not supported?
Salesforce Group Edition is not supported by the HubSpot Salesforce connector. All other editions with API access are supported, including Salesforce Government Cloud.
How long does the initial sync take?
Initial sync duration depends on your database size and Salesforce API allocation. A database of 50,000 contacts typically takes several hours. After the initial sync, records sync based on triggers (new creation, field updates, lifecycle stage changes) at 15-minute intervals.