---
name: hubspot-salesforce-integration
description: Connect HubSpot and Salesforce: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies, deals, activities, custom objects. Use when the user wants to set up, audit or troubleshoot HubSpot and Salesforce together, or asks why data is not moving between them.
---

# HubSpot and Salesforce

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-salesforce-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** HubSpot Professional or Enterprise, and a Salesforce edition with API access

**What moves:** contacts, companies, deals, activities, custom objects, both ways.
**How it is built:** native, marketplace app. **Effort:** days.

## The short version

The most capable connector HubSpot ships and the one that punishes a sloppy setup hardest. Contacts, companies, deals and activities sync out of the box, and Enterprise adds up to ten custom object syncs. Selective sync, which is how you stop Salesforce flooding HubSpot, needs a Salesforce Enterprise licence and is explicitly not supported by HubSpot's own support team. Group Edition is not supported at all.

## Check the plan before anything else

Rows: HubSpot tier. Columns: Salesforce edition. Most of the reports that this integration is broken are a pairing from this grid that was never going to work.

| HubSpot tier | Group | Professional | Enterprise or Unlimited |
|---|---|---|---|
| Free or Starter | Not supported | Not supported | Not supported |
| Professional | Not supported | Two-way sync | Sync and selective sync |
| Enterprise | Not supported | Sync and custom objects | All three |

- **Not supported.** Either HubSpot is below Professional, where the integration is not offered, or the Salesforce org is on Group Edition, which HubSpot documents as unsupported. Government Cloud, by contrast, is supported.
- **Two-way sync.** Two-way sync on contacts, companies, deals and activities, with a direction you set per field mapping. This is the integration almost everybody means.
- **Sync and selective sync.** The same sync, plus the option of controlling which Salesforce records come across at all. Selective sync needs a Salesforce Enterprise licence and is built out of sharing rules rather than a setting.
- **Sync and custom objects.** The same sync, plus custom objects in both directions. Custom object sync is a HubSpot Enterprise feature, so this one is gated on the HubSpot side.
- **All three.** Sync, custom objects and selective sync together, which is also the only combination where both vendors stop being the constraint and your own data model is.

Counted off that grid, of nine pairings: five give you not supported, one gives you two-way sync, one gives you sync and selective sync, one gives you sync and custom objects, one gives you all three.

Each gate sits with a different vendor, which is why this pair gets scoped wrong: the custom objects question is answered by your HubSpot contract and the selective sync question by your Salesforce one.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Contacts and Leads | Two-way sync | The default object, and the one where duplicate rules on the Salesforce side matter most. |
| Companies and Accounts | Two-way sync | Company sync has its own settings and its own matching behaviour. |
| Deals and Opportunities | Two-way sync | Stage mapping between two pipelines that were not designed together is most of the setup work. |
| Activities | Two-way sync | Emails, calls and meetings, which is how each side stops looking half-empty. |
| Custom objects | Two-way sync | HubSpot Enterprise only, and each direction is configurable per mapping. The HubSpot object needs at least one required field or it cannot sync at all. |

## Which field lands where

The mapping has a shape problem underneath it that no settings screen fixes: HubSpot has one record type where Salesforce has two. Everything else follows from that.

| In HubSpot | In Salesforce | What to know about the match |
|---|---|---|
| Contact | Lead or Contact | HubSpot has no Lead object, so one HubSpot contact has to land on one side of a Salesforce distinction HubSpot does not make. Decide the rule before go-live, because this is where the duplicates come from. |
| Company | Account | Its own settings and its own matching behaviour, separate from contact sync. |
| Deal | Opportunity | Stage mapping between two pipelines designed separately is most of the configuration work on this pair. |
| Activity | Task or Event | Emails, calls and meetings, which is what stops each side looking half empty to the team that lives in the other one. |
| Custom object | Custom object | HubSpot Enterprise only. Direction is configurable per mapping and per association, and the HubSpot object must have at least one required field. |

**What does not cross:**

- A record with no valid email address. HubSpot documents that these do not sync, which reads as a broken rule rather than a missing field.
- Anything historic, if you meant to migrate rather than to sync. HubSpot points one-time moves at Smart Transfer and says to turn its syncs off if you used it before.
- A field mapping whose Salesforce internal name changed. Mappings survive a move to a new production org only where the internal name matches on both sides.

## Connect it, in this order

**Who has to do it:** A HubSpot user with Account Access, and a Salesforce system administrator. The Salesforce half is the long half.
**How long:** A day for the connection and the first mappings. Weeks if your two pipelines were designed separately, which they were.

### 1. Check the Salesforce edition before anything else

*Where:* Salesforce: Company Information

You need an edition with API access, or Salesforce Professional. HubSpot documents Government Cloud as supported and Group Edition as not supported, so a Group org ends the project here rather than at the install screen.

### 2. Decide who the connected user will be, and treat it as a design decision

*Where:* Salesforce: Users

Whatever that user can see is what the integration can see. HubSpot states it plainly: if the connected user cannot view the lead object, leads do not sync, and HubSpot cannot create or update leads either. A departing admin's account is the wrong choice, and swapping later requires a user with permissions equal to or greater than the old one, in the same production org.

### 3. Give that user the four profile permissions

*Where:* Salesforce: profile, administrative permissions

API Enabled, View Setup and Configuration, Modify All on every object you intend to sync, and Modify Metadata. Three of the four are easy to miss because the install does not fail, it just syncs less than you asked for.

### 4. Install the app from the HubSpot marketplace

*Where:* HubSpot: Marketplace, search Salesforce

Click Install, and tick "Yes, this will connect to a sandbox" if that is what you are doing. Getting this checkbox wrong points a production sync at test data, or the reverse.

### 5. Log in as the connected user

*Where:* The HubSpot pop-up window

Enter that user's Salesforce credentials rather than your own. The account you authenticate with becomes the connected user, which is why step two came first.

### 6. Assign the permission set the managed package adds

*Where:* Salesforce: Permission Sets

HubSpot Integration Permissions only exists after the HubSpot managed package is installed in the org, so it cannot be assigned in advance however well prepared you are.

### 7. Map properties to fields, and set a direction on each one

*Where:* HubSpot: Connected Apps, Salesforce

Each mapping is two-way, always Salesforce, or always HubSpot. This is where the project actually lives: stage mapping between two pipelines nobody designed together is most of the work, and a mapping set to two-way on a field each side computes differently will fight itself forever.

### 8. Only then decide whether you need selective sync

*Where:* Salesforce: sharing settings

It needs a Salesforce Enterprise licence, a dedicated integration user on a cloned System Administrator profile, a new role at the top of the hierarchy, organisation-wide defaults set to Private and sharing rules that expose exactly the records you want. HubSpot publishes the method and says its support team does not cover it.

The thing to take from that order is that six of the eight steps are Salesforce work, and the one decision that shapes everything afterwards is which user you connect as.

## How to check it worked

- Log in as the connected user and open each object you expect to sync. Anything that user cannot see is a silent gap rather than an error.
- Create a record in Salesforce and wait a quarter of an hour. The Salesforce to HubSpot sync runs every 10 to 15 minutes, so a record that has not appeared in two minutes is not evidence of anything.
- Create one record with no email address and confirm it does not arrive. That is documented behaviour, and knowing it saves a day of debugging later.
- Change one mapped field on each side and check which value wins. That tests your direction settings rather than the connection.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| One object syncs and another does not | The connected user cannot see it. HubSpot performs every action through that user's permissions, so an object outside their profile is invisible in both directions. | Log in as the connected user and look. Then add Modify All on that object to their profile rather than widening the integration settings. |
| Everything broke after somebody changed the connected user | The replacement has narrower permissions, or belongs to a different Salesforce production org. | Give the new user permissions equal to or greater than the old one, in the same org. Treat the connected user as infrastructure rather than as somebody's login. |
| Records sync once, then stop | With selective sync, a record has to keep meeting the sharing rule. HubSpot warns specifically that records the integration itself creates in Salesforce will stop syncing unless they also match the criteria. | Write the sharing rule so records created by the integration satisfy it, then test with a form submission rather than with a hand-made record. |
| A record never arrives in HubSpot at all | No valid email address. HubSpot documents that those do not sync. | Check the email field before suspecting the mapping. If you need the record anyway, it has to arrive by another route. |
| The sync looks slow or stuck | Salesforce to HubSpot runs on a cycle of roughly 10 to 15 minutes. It is not instant and is not supposed to be. | Wait a cycle before investigating. If it is still missing after that, go to the connected user's permissions first. |
| Salesforce API limits are being eaten | HubSpot sets its API usage from your Salesforce limit, and a single contact sync can take up to four API calls per record, varying with what changed. | Size the limit against your Salesforce allowance rather than against record count, and use an inclusion list or selective sync to stop syncing records nobody needs. |
| Custom objects will not sync | Custom object sync is HubSpot Enterprise only, and the HubSpot object needs at least one required field. | Check the tier first, then the required field. Both are cheaper to check than the mapping screen is to debug. |
| Field mappings disappeared after a Salesforce migration | Mappings survive a move to a new production org only where the Salesforce field keeps the same internal name. | Match internal names before the cutover, or plan to rebuild the mappings and budget for it. |

## What breaks, from the vendors' own docs

- **Editions gate it on both sides.** Available on Professional and Enterprise across the HubSpot hubs. On the Salesforce side you need an edition with API access, or Salesforce Professional. Group Edition is not supported, and that is a hard stop rather than a workaround.
- **Selective sync is Enterprise and unsupported.** Filtering which Salesforce accounts reach HubSpot requires a Salesforce Enterprise licence, and HubSpot states it is not supported by their Customer Support team. It also assumes deep familiarity with your Salesforce org. Budget for a consultant or accept the full sync.
- **The install needs real Salesforce permissions.** Modify Metadata, Download AppExchange Packages and Customize Application. In most organisations that is a Salesforce admin doing it, on their schedule, which is usually the reason this project takes days rather than hours.
- **Two systems of record is the actual problem.** The connector will faithfully sync whatever confusion exists between two pipelines nobody reconciled. Decide which side owns each object and each stage before you map a single field, because the integration will not decide it for you.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

### Salesforce

- **Base:** `https://{instance}.my.salesforce.com/services/data/v60.0`
- **Auth:** OAuth 2.0 through a connected app. **API access is an edition feature**: editions without it cannot run any of this.

| Call | Request | What it does |
|---|---|---|
| `PATCH /sobjects/Contact/{id}` | `{ "RC_Title__c": "VP Sales" }` | Update a record. Custom fields carry the __c suffix. |
| `POST /composite/sobjects` | `{ "allOrNone": false, "records": [...] }` | Batch up to 200. `allOrNone: false` so one bad row does not roll back the batch. |
| `GET /query?q=SELECT+Id,Email+FROM+Contact+WHERE+Title=null` | - | SOQL for the filtered slice. |

**Rules that will cost you time if you skip them:**

- **Validation rules, required fields, duplicate rules and Apex triggers all apply to your writes.** A completed run is not a successful write. Read the per-record errors.
- **The daily API allocation is shared across the whole org**, set by edition and licence count. A row-by-row job competes with every other integration; the symptom of exhausting it is other people's integrations failing.
- Test in a sandbox with ten records before production. The rules you will hit were written years ago by somebody who has left.
- Installing anything usually needs Modify Metadata, Download AppExchange Packages and Customize Application. That is an admin on their own schedule.

Docs: https://developer.salesforce.com/docs/apis

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- HubSpot knowledge base: connect HubSpot and Salesforce: https://knowledge.hubspot.com/salesforce/install-the-hubspot-salesforce-integration
- HubSpot: Salesforce selective sync: https://www.hubspot.com/salesforce-selective-sync
- HubSpot knowledge base: manage your Salesforce integration settings: https://knowledge.hubspot.com/salesforce/manage-your-salesforce-integration-settings
- HubSpot knowledge base: sync custom objects between HubSpot and Salesforce: https://knowledge.hubspot.com/salesforce/set-up-and-use-salesforce-custom-object-sync
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-salesforce-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-salesforce-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
