Salesforce vs. HubSpot: How a Salesforce-HubSpot Integration Connects Marketing and Sales

Salesforce and HubSpot serve different parts of the revenue operation, but many organizations use both. HubSpot handles marketing engagement and lead generation while Salesforce manages CRM, sales, and revenue operations. The business value comes from connecting those functions without forcing either platform to take over work better suited to the other.

A Salesforce-HubSpot integration connects marketing activity to sales execution, gives teams shared visibility into customer information, and creates a more reliable path from engagement to revenue. The important decisions happen before the connection is configured: which system owns each record, what information needs to move, how qualified leads reach sales, and where the native connector stops being enough.

This article covers where each platform fits, what moves between them, and when connecting the two is beneficial for the organization.

‍

Executive Takeaways

• Salesforce and HubSpot serve different halves of the same revenue operation. Running both is a defensible architecture, not a failure to consolidate.
• Integration design starts with business process and system ownership, not with field mapping.
• Each platform gets only the data it needs to do its job. Syncing everything creates governance work without creating value.
• Routing rules turn a synced lead into an owned lead. Without them, the handoff stops at the record.
• Integration does not clean up duplicate data. It moves duplicates into the other system and keeps both copies alive.
• Governance is what keeps the connection accurate after the launch project ends.

‍

Salesforce vs. HubSpot: What Does Each Platform Do Best?

Salesforce and HubSpot approach revenue operations from different starting points. HubSpot centers marketing engagement and inbound growth. Salesforce provides a broader CRM foundation for sales, customer relationships, reporting, forecasting, and revenue operations.

Where HubSpot Fits

HubSpot is designed around marketing, customer engagement, and inbound growth. Marketing teams use the platform to manage campaigns, capture leads, build forms and landing pages, send email campaigns, manage content engagement, and track how prospects interact with marketing activities.

HubSpot earns its place when marketing owns demand generation end-to-end and needs the campaign, the form, and the engagement record in one system. Its limits show up later in the funnel, in complex sales processes, forecasting, and multi-team reporting.

Where Salesforce Fits

Salesforce provides a broader CRM foundation for managing leads, accounts, contacts, opportunities, sales processes, forecasting, reporting, and customer relationships. Its flexibility also supports more complex workflows, integrations, and business processes across sales and revenue operations.

For organizations with complex sales structures, multiple teams, sophisticated reporting requirements, or processes that extend beyond traditional CRM functions, Salesforce serves as the central system for managing customer and revenue information.

Where They Overlap

Both platforms store contacts, both send email, both run workflow automation, and both report on pipeline. That overlap makes system ownership a business decision. For every overlapping capability, one system has to be the one that decides.

What Is a Salesforce-HubSpot Integration?

A Salesforce-HubSpot integration is a configured data connection between the two platforms that keeps their records aligned: HubSpot contacts map to Salesforce leads and contacts, HubSpot companies map to Salesforce accounts, and HubSpot deals map to Salesforce opportunities. Marketing engagement, campaign activity, and lifecycle stages travel alongside those records. Four business rules define the connection: which records sync, in which direction, on what trigger, and which system wins when the two disagree.

The company mapping comes with conditions, and the conditions are Salesforce conditions. HubSpot will not create a Salesforce account when the company has no associated contacts, when none of its contacts qualify for your inclusion segment, or when every associated contact is syncing to a Salesforce lead rather than a contact. Route inbound to leads by default, as most organizations do, and the accounts never appear.

The return on that connection shows up in four places.

‍

What a Salesforce-HubSpot Integration Is Actually Worth

The business value of integration comes from connecting processes that otherwise depend on manual handoffs, disconnected information, or duplicate work.

1. Better visibility across the customer journey. Sales representatives see relevant marketing engagement alongside CRM information, while marketing teams connect campaigns with downstream sales activity and pipeline. Leadership gets a clearer view of how marketing activity contributes to revenue.

2. Faster lead response. When qualified leads move into Salesforce automatically and routing rules assign them to the appropriate representative, sales teams spend less time waiting for manual handoffs and more time following up with prospects.

3. More complete customer data. Connected systems reduce duplicate entry and give teams access to information that would otherwise sit in separate platforms, spreadsheets, or manual reports.

4. Less administrative work. Automated synchronization and workflows reduce repetitive tasks such as manual data entry, record updates, notifications, and lead assignment.

These four benefits compound only when routing and ownership rules are right. Connect two systems on top of an undefined handoff, and you deliver bad leads faster.

‍

When Does a Salesforce-HubSpot Integration Make Sense?

A Salesforce-HubSpot integration makes sense when each platform already supports an important part of the revenue operation and the organization needs those functions to work together.

Common situations include:

• Marketing and Sales use different platforms
• HubSpot is deeply embedded in marketing operations
• Salesforce is the primary CRM
• Marketing needs visibility into sales outcomes
• Sales needs marketing engagement data
• Manual lead handoffs are slowing response times
• Leadership needs better visibility across the revenue funnel
• The organization wants to preserve existing investments in both platforms

Integration will not fix any of the following, and it will surface them faster:

• Contact and account data is already duplicated or incomplete in one or both systems
• Lead qualification criteria are undefined, so there is nothing to automate
• Neither platform has been named the system of record for the customer
• Salesforce routing rules do not reflect how territories are actually run
• No one owns the integration after go-live

Before connecting the systems, leadership should establish what problem the integration needs to solve and how success will be measured.

‍

Does Your Situation Qualify?

Integration is the right investment when at least three of these are true:

1. Qualified leads sit between form submission and first sales touch long enough that prospects go cold.
2. Someone reconciles marketing and sales numbers by hand before every leadership meeting.
3. Sales reps ask marketing for engagement history instead of reading it in Salesforce.
4. Marketing cannot report which campaigns produced closed revenue without exporting from both systems.
5. The same person exists as separate records in both platforms, and no one is certain which is current.

With that settled, the mechanics come down to three decisions: what syncs, who owns it, and where leads go next.

‍

How the Salesforce-HubSpot Connection Actually Works

A Salesforce-HubSpot integration starts with explicit decisions about data ownership, field mapping, synchronization rules, and business workflows.

Data Synchronization

Direction is set per object and per field, with exceptions the connector enforces on its own. Owner is the clearest one. HubSpot documents that the Owner mapping can only be mapped two-way between HubSpot and Salesforce, and warns that your account may display a different rule than the one actually in force.

‍

Field Mapping and Data Ownership

Because the two systems hold different information, every synced field needs an explicit mapping and an explicit owner. Field mapping determines how information in one system corresponds to information in the other. Data ownership determines which system has authority over a particular record or field.

For example, an organization might establish Salesforce as the authoritative system for account ownership and opportunity information while HubSpot remains the primary system for marketing engagement data.

‍

Lead Routing Between HubSpot and Salesforce

Lead routing is where the integration either delivers or quietly fails.

HubSpot engagement → qualification → Salesforce → routing → sales representative → follow-up

For example, a prospect can engage with a HubSpot campaign, meet defined qualification criteria, and then enter Salesforce for sales follow-up. Salesforce routes the lead according to rules such as geography, company size, industry, lead score, product interest, territory, or existing account ownership.

Ownership is where a Salesforce routing investment quietly becomes decorative, and HubSpot documents the sequence precisely. It publishes this as contact owner assignment behavior, and notes separately that owner assignment differs for contacts, companies, and deals without documenting the other two. For contacts, it runs in this order.

1. Owner is not an ordinary mapped field. HubSpot warns that your account may display “Prefer Salesforce unless blank” for the Owner mapping while the mapping can only ever be two-way. There is no “Salesforce wins” setting to reach for.
2. The match test is name and email together, against an active Salesforce user. Any Salesforce owner reaches HubSpot. Only a HubSpot owner matching an active Salesforce user’s name and email address exactly reaches Salesforce.
3. New Salesforce lead, matching HubSpot owner already set. HubSpot documents that the owner is written straight onto the lead and your Salesforce lead assignment rules do not run. The lead exists, it has an owner, nothing errors. That is what a failed routing project looks like from the inside.
4. New Salesforce lead, no matching owner. Only then do Salesforce lead assignment rules apply. Your rules are the fallback path.
5. Sync onto an existing Salesforce lead that already has an active owner. Assignment rules do not apply and the Salesforce owner is kept on the first sync. Connecting HubSpot will not re-route your existing book of business.
6. Every sync after the first. Last write wins, in both directions. A rep reassigning in HubSpot overwrites Salesforce, and a manager reassigning in Salesforce overwrites HubSpot.
7. The one Salesforce veto. An owner HubSpot cannot match is reverted rather than rejected: the Owner ID field resets to the last value from Salesforce. The record looks assigned. It is assigned to whoever had it before.
8. Nothing arrives unowned. Salesforce requires an owner, so an unassigned HubSpot record that creates a new Salesforce record is owned by the integration user. Filter a list view to that user before you believe your funnel numbers.

On the Salesforce side, assignment rules exist only for cases and leads, so a contact arriving from HubSpot has no assignment-rule fallback available at all. And Salesforce’s own default runs against the sequence above. We tested it in a clean org: a lead created over the REST API with no assignment rule header was routed by the active assignment rule even though the write supplied an owner explicitly. For HubSpot’s documented behavior to hold, the connector has to be suppressing assignment rules on its own writes. So if your rules did not fire on a connector-created lead, that is not something you misconfigured.

Without defined routing, an integration can move a lead into Salesforce without ensuring that anyone takes ownership of it. Leads that arrive without an owner do not get worked, and the pipeline never records the loss.

Each of those is a business decision, and the order you make them in matters.

‍

Six Steps to a Salesforce-HubSpot Integration

A successful Salesforce-HubSpot integration starts with business requirements rather than technical configuration. Before deciding what data to sync or how to build the workflows, define what the organization needs the connection to accomplish.

1. Define the business objective. Identify the specific operational problem the integration needs to solve, such as improving lead response, connecting marketing activity to pipeline, or reducing manual data entry.
2. Define system ownership. Determine which platform owns leads, contacts, accounts, opportunities, marketing engagement, and sales ownership.
3. Map the data. Identify which information needs to move between platforms and which information should remain within its source system.
4. Define workflows and routing. Establish how qualification, lead assignment, lifecycle transitions, notifications, and other connected processes should work.
5. Establish governance. Assign responsibility for monitoring, data quality, changes, errors, and future enhancements.
6. Measure the outcome. Track metrics such as lead response time, MQL-to-SQL conversion, duplicate rates, data completeness, marketing-sourced pipeline, and manual hours eliminated.

‍

What an Integration Project Takes

Scope drives effort. Installing the native connector across standard objects with a short field map is a different project from one with custom matching rules, routing logic, and historical data cleanup. Four variables move the estimate: the number of custom fields in scope, the condition of the existing data, the number of routing rules, and whether records have to be deduplicated before the sync is switched on.

Budget for three things organizations routinely underestimate: data cleanup before go-live, a monitoring plan for failed syncs, and a named owner for the integration after the project closes.

Once these decisions are made, the next step is determining what information actually needs to move between the platforms.

‍

What Data Should You Sync Between HubSpot and Salesforce?

What belongs in each system depends on which team is accountable for the outcome. A typical split:

The connector supports more than this. What the table shows is what most organizations should turn on.

The right integration does not synchronize everything. It synchronizes the information each system needs to perform its role.

Sending every available field, activity, and record between platforms increases the amount of information teams must maintain and govern. A focused data strategy creates a cleaner connection and makes it easier to identify problems when something goes wrong.

‍

Common Challenges With a Salesforce-HubSpot Integration

Integration introduces another layer into the technology environment, which makes planning and governance important.

Duplicate records are the failure mode with the most specific mechanics behind them. HubSpot’s native Salesforce connector matches leads and contacts by email address. Salesforce works from a different definition of the same person. Its standard lead matching rule pairs First Name and Last Name into every clause of a seven-part equation, compares Email as an exact string at a threshold of 100, and will also call two records a match on name and phone with no email involved, so the same pair of records can be one person in HubSpot and two people in Salesforce. When several Salesforce leads or contacts share one email, the first sync takes whichever record Salesforce returns first, in no particular order. After that, HubSpot syncs with whichever of those records was most recently updated in Salesforce. An edit to a duplicate moves the sync to a record nobody chose and overwrites the HubSpot contact. HubSpot’s guidance is to merge the duplicates in Salesforce first. Integration does not clean up the duplicates you already have. It keeps both copies alive and syncs to the wrong one.

Those rules also behave differently for an integration than they do for your reps. Salesforce activates the standard lead rule by default with an Action on Create of Allow, which alerts a rep and lets them save the duplicate anyway. A connector gets no alert and no choice: Salesforce documents that when records are added or edited through its APIs, duplicate rule settings are overridden so that no alert is shown and users cannot save records, and the REST API’s Duplicate Rule Header defaults allowSave to false. We reproduced that in a sandbox, where a second identical lead created over REST came back rejected with DUPLICATES_DETECTED carrying the rule’s own alert text. The warning your team tuned for reps reaches the integration as a hard rejection unless the connector sets allowSave to true.

Conversion is the gap in that coverage. Salesforce documents that duplicate rules do not run when leads are converted to accounts or contacts unless Use Apex Lead Convert is enabled, so at the most consequential moment in the funnel the rules you configured sit out, and conversion falls back to a thinner matching pass of its own.

Conflicting data creates another risk. If Salesforce and HubSpot contain different information for the same record, the organization needs a defined rule for which system controls the data.

Unclear ownership creates similar problems. Teams need to know who owns the integration, who manages data quality, and who approves changes to synchronization rules.

Poor lead routing undermines the value of the integration. A qualified lead reaching Salesforce does not help the business if the lead is assigned incorrectly or sits without an owner. Routing rules connect the data transfer to an accountable sales workflow.

Multi-currency needs a decision before go-live. HubSpot documents that the integration “cannot convert between currencies when syncing currency values” and that “only the number value will sync between Salesforce and HubSpot, and no exchange rates will be applied.” A figure that crosses as a bare number, into a system carrying its own currency on deals and its own exchange rates, is a reporting decision someone has to make deliberately rather than discover in a board deck.

HubSpot reaches the same conclusion in its own troubleshooting documentation, where the resolution guidance for its Custom code sync error category reads: “Since these errors are originating in Salesforce, it’s recommended that you work with your Salesforce admin to resolve the issue in your custom code in Salesforce.”

‍

Do You Need a Custom Integration, or Will the Native Connector Work?

HubSpot builds and maintains a native Salesforce connector. Install it, authenticate both systems, and choose which objects and fields sync. Nothing moves yet. HubSpot’s documentation is explicit that records do not sync automatically once the integration is set up. Someone still has to run the import and decide what triggers a sync from there.

It requires HubSpot Professional or Enterprise and is not available on Free or Starter. The Salesforce side has its own gate. Salesforce documents API access as enabled by default in Enterprise, Performance, Unlimited and Developer Edition, and available to Professional Edition orgs as an add-on purchased through the Your Account app or an account executive. Send a request to an org without it and Salesforce returns API_DISABLED_FOR_ORG. HubSpot will not connect to Group Edition at all. The connected user has to be a Salesforce system administrator carrying API Enabled, View Setup and Configuration, Modify All on whichever of accounts, campaigns, contacts, leads and opportunities you intend to sync, Download AppExchange Packages, Customize Application, and, if you want the HubSpot Embed window or deal sync, Modify Metadata. That user’s permissions are the ceiling on everything the integration can do, including whether an object syncs at all.

Login IP restrictions are the other thing to settle before kickoff. HubSpot connects from dynamic IP addresses that cannot be added to an allowlist, so HubSpot documents that if your Salesforce account uses login IP restrictions it may not be able to connect, and that when the setting it calls Enforce IP Restrictions on Every Request is selected, the integration will not be able to connect. That checkbox sits under Session Settings in Setup, labeled Enforce login IP ranges on every request, and it only bites where profiles actually carry login IP ranges. An org with the box ticked and no ranges defined has nothing to enforce.

For an organization with a clean data model and clean records, the native connector is the right answer and the project ends there.

The connector stops being sufficient when:

• Records have to be matched on something other than email, or existing accounts and contacts must be checked before a new lead is created
• The sync has to make a decision, route, transform, suppress, or defer, rather than copy a value
• A custom object has to reach both Salesforce leads and contacts
• Salesforce relationships beyond contact-to-account carry part of the process
• A third system is in scope and the integration has to arbitrate between more than two sources
• Salesforce ownership, territory, or sharing rules determine where a record should land

The connector does sync Salesforce custom objects, with conditions attached. It requires a HubSpot Enterprise subscription rather than the Professional tier the base connector needs. Lookup fields on a custom object cannot be used in a field mapping, and HubSpot routes that data through the association setting instead, which forces the relationship to be modeled deliberately in Salesforce. And a custom object syncs to Salesforce contacts or to leads, never both, which forces that choice before a lead has converted.

Two other options exist. Middleware such as MuleSoft, Workato, or n8n adds routing and transformation logic between the platforms without custom code, and is the usual answer when a third system is involved. A custom integration built in Salesforce is warranted when the logic already lives there, and the matching rules are specific to your data.

Start with the native connector. Move up only when a named requirement breaks it.

‍

Salesforce-HubSpot Integration FAQ

Can Salesforce and HubSpot be integrated?

Yes. Salesforce and HubSpot can be connected so selected customer, marketing, lead, and sales information moves between the platforms according to defined synchronization and workflow rules.

What data syncs between HubSpot and Salesforce?

Common synchronized data includes leads, contacts, accounts, opportunities, lifecycle stages, campaign membership, ownership, and selected activity data.

Should Salesforce or HubSpot be the source of truth?

It depends on the field, not the platform. Salesforce often serves as the primary system for CRM, account, opportunity, and sales ownership information, while HubSpot serves as the primary system for marketing engagement. Organizations should define ownership field by field where necessary.

How does lead routing work between HubSpot and Salesforce?

Lead routing connects qualification criteria with Salesforce assignment rules. Criteria include geography, company size, industry, territory, product interest, lead score, or existing account ownership. The workflow should establish both assignment and accountability.

Does integrating Salesforce and HubSpot eliminate duplicate data?

No. Integration can reduce manual duplication, but it does not automatically resolve existing data-quality problems. Matching rules, field ownership, and data governance are necessary to maintain accurate records across both platforms.

Do you need a Salesforce consultant to integrate HubSpot and Salesforce?

Not always. If the native connector covers your requirements and your Salesforce data is clean, an internal admin can install and configure it.

The work that justifies outside help sits on the Salesforce side of the connection: matching rules that prevent duplicate leads against owned accounts, assignment and territory logic, sharing implications, and keeping forecast and pipeline reporting intact once marketing data starts arriving. A HubSpot partner will optimize the HubSpot end. Making records land correctly in a Salesforce org with years of process already built into it is a different problem.

That is the pattern we build: matching inbound records against owned Salesforce accounts, routing them under live territory and sharing rules, and keeping pipeline reporting intact while a second system writes into the org. Our territory management framework routes more than 150,000 records a year across leads, accounts, and opportunities, and cut routing corrections by 90%.

‍

Need Help Connecting Salesforce and HubSpot?

Most of the difficulty in a Salesforce-HubSpot integration sits on the Salesforce side: matching rules, ownership, routing, sharing, and reporting integrity. That is the work we do. Across 100+ completed projects, we evaluate the current environment, define what should move between the platforms, and build the routing and governance that holds up as the business changes. Our client satisfaction rating on that work is 100%.

Let’s Chat →

‍