Two CRMs, one connector, and an edition requirement on both sides.
HubSpot Professional or Enterprise, and a Salesforce edition with API access
Contacts, Companies, Deals, Activities, Custom objects, two-way sync.
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.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Contacts and Leads | Both ways | The default object, and the one where duplicate rules on the Salesforce side matter most. |
| Companies and Accounts | Both ways | Company sync has its own settings and its own matching behaviour. |
| Deals and Opportunities | Both ways | Stage mapping between two pipelines that were not designed together is most of the setup work. |
| Activities | Both ways | Emails, calls and meetings, which is how each side stops looking half-empty. |
| Custom objects | Both ways | 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. |
Every row in that table moves in both directions, which is rarer than the feature lists suggest. Nothing here is a one-way copy you have to design around.
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. |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: five field mappings and three documented exclusions, each one's note, and the four vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The Lead and Contact line is the one to resolve on a whiteboard rather than in a settings screen, because every duplicate this integration produces is downstream of it.
Three HubSpot editions against three Salesforce ones, and what each pairing gives you. Pick the two you own and the grid marks the answer.
Pick an edition on each side.
| 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 |
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.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
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.
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.
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.
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.
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.
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.
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.
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.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/hubspot-salesforce/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-salesforce.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyThe 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.
WhyThe 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.
WhyWith 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.
WhyNo 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.
WhySalesforce 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.
WhyHubSpot 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.
WhyCustom 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.
WhyMappings 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.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2023 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
Hubspot has no concept of a Lead, it is considered a Contact. SF has Leads and Contacts. Thats a reasonable indication of what you're in for. The integration does it's best but you have two systems with a lot of nuanced duplication.
r/salesforce·August 2023·14 points
The most useful sentence anybody has written about this pair, and it is the first row of the field table above. The reply underneath it, from somebody who had run the integration for nearly a decade, calls it a great breakdown of the pain points.
Is anyone else out there living this nightmare? Recently made the switch to using both, after HubSpot served as our only CRM for 7 years. We only moved because leadership liked Salesforce reporting more. Now that we're split, with our Marketing org living in HubSpot and sales living in Salesforce [...]
r/salesforce·August 2026·24 points
Worth reading before the project rather than after it. The integration is good enough that running both is survivable, which is exactly how organisations end up doing it for a reason as thin as a reporting preference.
I literally had a configuration change, so it started syncing Salesforce Leads and Contacts to HubSpot contacts [...] HubSpot's logs show I only changed it back. I have screenshots of it before being off, no records of any of us changing it.
r/salesforce·August 2026·5 points
One account, unverified, and worth knowing anyway: this integration has enough switches that a change nobody remembers making is plausible. Screenshot your mapping settings after go-live, which costs a minute and settles the argument.
Got into work this morning to discover Salesforce is no longer a connected app in our account. Went to the marketplace to re-install and it's not available there either.
r/hubspot·September 2026·12 points
HubSpot staff confirmed it in the thread as a known issue with the app unavailable in the marketplace while they restored access. A one-off rather than a pattern, but it is the reminder that a native app is somebody else's deployment: check the vendor status page before your own change log.
Search out Lauren Ryan on LinkedIn. She is a Hubspot Saleforce integration expert. Thats is her whole business model.
r/hubspot·September 2024·5 points
A market signal rather than an endorsement. People make a living on this pair alone, which tells you where on the effort scale to put it: closer to a migration than to an install.
The threads are not really about the integration. They are about running two CRMs, which is what this integration makes possible and does not make advisable. The practitioners who have lived with it describe the same three things: an object model that does not line up, a configuration surface big enough to drift on its own, and a dependency on one vendor's uptime. Nobody in these threads regrets connecting the two systems; several regret having two.
Taken together the threads argue for deciding the Lead and Contact rule and the system of record first, and treating the connector as the easy part, which on this pair it genuinely is.
This is the only pair in the directory where both sides are a system of record, and that is the whole difficulty. Every other integration here has an obvious owner: the CRM owns the contact and the other tool contributes to it. Here, two tools both believe they own the contact, the account and the opportunity, and the connector will do exactly what you tell it including the incoherent parts.
So the work is not technical. It is deciding, object by object, which side wins, and then writing that down somewhere the next admin will find it. Three decisions cover most of it:
Write the three answers down before the install. The connector will implement whatever you decide, including the incoherent version, and it will not tell you which one you chose.
Everything about this pair also takes longer than the documentation implies, because the slow parts are human rather than technical:
None of that is hard and all of it is scheduling, which is the argument for starting the access requests in the week you decide rather than the week you build.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, Salesforce and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
HubSpot Professional or Enterprise on the hub you are syncing, and a Salesforce edition with API access. Salesforce Group Edition is not supported at all. Selective sync, which is how you stop Salesforce flooding HubSpot, requires a Salesforce Enterprise licence and HubSpot states it is not supported by their own support team.
Contacts and leads, companies and accounts, deals and opportunities, and activities, out of the box. Enterprise adds up to ten custom object syncs. Below that, custom objects do not travel, which is worth knowing before you design a motion around one.
Days rather than hours, and almost none of it is technical. The slow parts are the Salesforce permissions (Modify Metadata, Download AppExchange Packages, Customize Application), the sandbox test and the change window. Plan around the admin queue rather than around the setup guide.
Decide object by object before you map a single field, because the connector will faithfully implement whatever confusion you hand it. Contacts usually go to HubSpot because marketing creates them; opportunities usually go to Salesforce because that is where the forecast lives. Activities are the ones that get argued about, and that argument is cheaper before the install.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.