1. Home
  2. Salesforce integration
  3. HubSpot and Salesforce

HubSpot's Salesforce connector syncs your core records both ways and spends up to four Salesforce API calls per contact

HubSpot's own Salesforce integration comes with its Professional and Enterprise plans and keeps contacts, companies, deals and tickets in step both ways. Each contact sync can use up to four Salesforce API calls, from the same daily pool as your other tools. We read HubSpot's help center on 18 November 2026 for the rules below, and mark where a custom build takes over.

Checked 18 November 2026

What the HubSpot Salesforce integration syncs

It syncs four pairs of records, and custom objects on Enterprise plans. HubSpot’s planning guide sets out which record matches which. Campaigns are the odd one out: HubSpot says Salesforce campaigns have no direct match in HubSpot.

Scroll the table sideways to see every column.

In Salesforce In HubSpot What HubSpot’s help center says
Lead and Contact Contact Both Salesforce objects sync to HubSpot contacts. With no inclusion segment set, every HubSpot contact syncs to Salesforce.
Account Company Accounts are equivalent to companies.
Opportunity Deal Only deals in HubSpot pipelines mapped to an opportunity record type can sync.
Case Ticket Turning on ticket sync does not pull in old cases. A case syncs when it is created or updated, or through an import.
Campaign No match HubSpot’s campaigns tool serves a different purpose.
Custom object Custom object Enterprise plans only. You create the object in HubSpot first.

Activities have their own two modes. The Timeline sync runs one way, from HubSpot to Salesforce, and lands as Salesforce tasks. The Activity sync runs both ways for tasks, sales emails, calls and meetings.

Old activity does not all come across. Only marketing email events from within 30 days of the contact’s sync go to Salesforce. Form submissions go back one year. And each activity can carry only one contact association, so a meeting with three HubSpot contacts will fail to sync until you trim it to one.

What you need before you connect HubSpot and Salesforce

You need the right plan on both sides and a Salesforce admin login. HubSpot lists the integration for Professional and Enterprise subscriptions of its hubs, such as Sales Hub or Marketing Hub.

On the Salesforce side, HubSpot asks for an edition with API access, or Salesforce Professional. Government Cloud works. Group Edition does not.

  • A system administrator connects it. HubSpot says the person who connects must be a Salesforce system administrator, with API Enabled among their profile rights.
  • That user’s rights become the sync’s rights. If the connected user cannot see leads, leads will not sync. HubSpot says the sync usually needs access to leads, contacts, accounts, opportunities, campaigns, tasks and users.
  • IP rules can block it. If your org limits logins by IP address, set the HubSpot app to Relax IP Restrictions in Salesforce. The Salesforce setting Enforce IP Restrictions on Every Request overrides that and stops the app from connecting.
  • One Salesforce org per HubSpot account. Two HubSpot accounts can share one Salesforce org, but each installs the integration on its own.
  • Records wait for a trigger. Nothing syncs the moment you install. You import your Salesforce records, or let them come over as they change.

HubSpot’s guide says to test your settings first in a Salesforce sandbox, a HubSpot developer test account or a HubSpot sandbox. Under the Two-way rule, a value deleted in one system is deleted in the other too, so one wrong rule on a live org can wipe good data in both.

How many Salesforce API calls the HubSpot sync uses

Up to four calls per contact record, by HubSpot’s count, and the number can vary. Those calls come out of your Salesforce org’s daily pool. Salesforce counts that pool for the whole org, not per user or per tool.

Salesforce says Enterprise Edition gets 100,000 calls a day, plus more for each license, plus any you buy. Your ERP link, your marketing tools and any data warehouse feed all draw on that one pool.

HubSpot gives you a control for this. On the Sync Health tab it shows the calls used in the last 24 hours, the number “Limited by Salesforce”, and a field called “Allocated to HubSpot”. The window rolls.

When the pool runs dry, HubSpot says Salesforce stops taking new API requests. The integration may still look connected while HubSpot cannot get Salesforce data. Syncing usually picks up again on its own when the limit resets, so records lag until then.

Switching on HubSpot’s updated deal sync can raise Salesforce API use for a while, HubSpot says, as it indexes records. A first import of your Salesforce records also uses calls. Set “Allocated to HubSpot” before either one.

Who wins when HubSpot and Salesforce disagree

You decide, field by field. HubSpot’s planning guide lists five sync rules, from always using Salesforce’s value to always using HubSpot’s. With the Two-way rule, the most recent update from either side wins.

HubSpot’s own example is a good start. Sync only marketing qualified leads to Salesforce. Make Salesforce the source of truth for sales fields. Send opportunity revenue back to HubSpot for reporting.

HubSpot sets these field rules:

  • Owner must match exactly. The Owner mapping can only run two-way, and the owner value has to be the same in both systems.
  • 500 mappings per object. That is HubSpot’s limit for field mappings on each object.
  • No backfill. Values that existed before you created a mapping do not sync on their own. You resync the records or run an import.
  • User fields stay put. Custom HubSpot properties of the user field type cannot map to Salesforce.
  • Deletes and merges stop at HubSpot. Deleting a HubSpot deal leaves the Salesforce opportunity in place, and that setting cannot be edited. Merging two HubSpot deals does not merge anything in Salesforce.
  • The deal sync switch is final. Once you move to HubSpot’s updated deal sync, you cannot go back to the standard one.

Where HubSpot’s connector stops and a custom build starts

The connector stops at quotes, at custom objects below Enterprise and at your ERP. Those need code on the vendors’ APIs.

Quotes and line items. HubSpot’s custom object sync can carry some Salesforce standard objects to HubSpot custom objects. Its list includes OpportunityLineItem, Order, OrderItem, Pricebook2 and PricebookEntry. When we read that list on 18 November 2026, Quote and QuoteLineItem were not on it. Salesforce has had the Quote object since API version 18.0. On HubSpot’s side, creating a quote through the API needs a Revenue Hub Professional or Enterprise plan, and each new quote starts as a draft. HubSpot says accounts created before 3 September 2025 may keep access to legacy quotes. So a quote that must exist in both CRMs is a custom job.

Custom objects on lower plans. Custom object sync needs Enterprise. On Professional, a custom object in Salesforce has no built-in path to HubSpot.

Your ERP. Neither CRM’s connector reaches your ERP. A won deal that must become a sales order needs its own link from Salesforce or from HubSpot. Our team has built HubSpot to ERP integrations.

A custom build has its own limits. HubSpot gives a private app on Professional 190 requests per 10 seconds and 625,000 a day per account. Enterprise gets 1,000,000 a day. If your service misses a HubSpot webhook, HubSpot retries it up to 10 times over 24 hours. On the Salesforce side, the same daily pool applies to your code as to HubSpot’s connector.

HubSpot sorts sync errors by type and resyncs 100 at a time

HubSpot sorts sync errors by type on the Sync Health tab, with a card for each. For errors from Salesforce automation, flows or validation rules, HubSpot recommends working with your Salesforce admin.

Once you fix the cause, you can resync 100 errors at a time from HubSpot. More than that needs an import from Salesforce, or an update to a mapped property.

Plan both moves before you touch the integration.

A new Salesforce production org means about one hour with the integration turned off, HubSpot says. Contacts keep their link to Salesforce leads and contacts. The links between companies and accounts, and between deals and opportunities, are lost.

Leaving Salesforce for good is a different job. HubSpot says to use Smart Transfer for a one-time move, not the integration. Our team takes Salesforce and HubSpot implementation end to end, with data moved and teams trained, so either direction can be one project.

HubSpot’s legacy Visualforce package is on its way out

Check which HubSpot package your Salesforce org runs. HubSpot released Connector Package v3.0.1 in March 2022. HubSpot also says its older managed package, with the legacy Visualforce window, is being deprecated, and it recommends HubSpot Embed instead.

HubSpot says its integration is not affected by Salesforce retiring legacy API versions. Other tools in your org may be. Salesforce is retiring the SOAP login() call in its Summer ’27 release, so ask the vendor of every older tool how it signs in.

Both CRMs now speak MCP, the standard agents use to reach other software

The sync moves records. Agents act on them. MCP, short for Model Context Protocol, is a standard way for AI tools to use other software.

HubSpot says Agent Hub comes with every Starter, Professional and Enterprise edition, with ready-made prospecting, customer and data agents. Salesforce shows its own sales agent qualifying an inbound lead and updating an opportunity in Agentforce.

Agentforce can reach other systems through MCP servers, and Salesforce says A2A lets it work with other vendors’ agents. HubSpot runs its own remote MCP server at mcp.hubspot.com, which agents can use to read and edit records such as contacts, companies, deals and tickets. An agent that works across both CRMs still needs a build that decides which system owns each field and who approves a change.

Our team has built Salesforce agents in Agentforce and as custom agents through Salesforce’s API. We have also built HubSpot agents on Anthropic’s Claude. See Salesforce AI agents and HubSpot AI agents.

How we would plan your HubSpot and Salesforce sync

We start with HubSpot’s own planning steps and add the parts its connector does not cover.

  1. Field plan. For each field, we write down the owner system and the sync rule. That is HubSpot’s own advice.
  2. Sandbox first. We connect a Salesforce sandbox and test every rule, then switch to production.
  3. API budget. We set “Allocated to HubSpot” so your ERP link and other tools keep enough calls.
  4. Custom pieces. Quotes, ERP orders or agents get built on the vendors’ APIs, after the core sync is clean.

For the other ways to connect Salesforce, see Salesforce integration routes. The first call is free.

Questions

Does the HubSpot Salesforce integration sync both ways?

Yes. HubSpot built it for ongoing two-way sync. You still choose a rule for each field, so one side can always win. A few parts run one way only. The Timeline sync sends HubSpot events to Salesforce as tasks. And when you delete a HubSpot deal, the Salesforce opportunity stays, which you cannot change.

How many Salesforce API calls does the HubSpot integration use?

HubSpot says one contact sync can take up to four API calls per record, and the number varies. Those calls come from your Salesforce org's daily pool, which Salesforce counts for the whole org. In HubSpot you can see the calls used in the last 24 hours and set how many go to HubSpot. Set that number before the first big import.

Which CRM is better, HubSpot or Salesforce?

If you keep both, HubSpot's own planning guide gives the pattern: marketing qualifies leads in HubSpot, only those leads go to Salesforce, Salesforce owns the sales fields, and opportunity revenue flows back to HubSpot for reporting. So the better question is which system should own each field. Answer that first, then map the fields.

Does HubSpot CRM have AI?

Yes. HubSpot says Agent Hub comes with every Starter, Professional and Enterprise edition. It names a prospecting agent, a customer agent and a data agent as ready-made. HubSpot also runs a remote MCP server, an open door that outside AI tools can use to read and edit HubSpot records such as contacts, companies and deals.

Can we sync Salesforce custom objects to HubSpot?

Yes, on Enterprise plans only. You first create the matching custom object in HubSpot. Then you map it in the Salesforce settings. Lookup fields on Salesforce custom objects cannot be mapped as fields. That data has to go through the association setting instead. Test it in a sandbox before you turn it on in production.

We want to leave Salesforce for HubSpot. Should we use the integration?

No. HubSpot says the integration is for ongoing two-way sync, and it points a one-time move to HubSpot Smart Transfer. If you used Smart Transfer before, turn its sync off before you turn the integration on: the two match records by different IDs, and running both creates duplicates. Our team takes HubSpot CRM implementation end to end, so the move, the setup and the training can be one project.

What drives the cost of a HubSpot Salesforce integration?

Plans first, then build work. HubSpot lists the integration for Professional and Enterprise hubs, and Salesforce needs an edition with API access, or Professional. Custom object sync needs HubSpot Enterprise. Creating quotes through HubSpot's API needs Revenue Hub Professional or Enterprise. Anything the connector does not cover, such as quotes or an ERP link, is a custom build with its own API limits. We publish no prices; vendors set their own plan prices.

Do we need an official HubSpot or Salesforce partner to set this up?

Not for this work. What decides a sync like this is a team that knows both systems from the inside and builds on their published APIs. Our team has set up Salesforce and HubSpot end to end, and has built agents in both. You license each system from its vendor or a reseller. We take the setup, the field plan, the data move and any custom build.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Talk to us about your HubSpot and Salesforce sync

Bring your field list and tell us which system should own each field. The first call is free.

Book a HubSpot and Salesforce call