HubSpot Salesforce Integration: The Complete Guide for US Business Teams (2025)

Can HubSpot Integrate with Salesforce?

Yes — and the question comes up constantly because both tools sit at the center of how most US mid-market companies manage their revenue pipeline. HubSpot and Salesforce are not natively hostile to each other. HubSpot ships a dedicated Salesforce connector through its App Marketplace that works on Professional and Enterprise tiers, and it is used by thousands of US teams running both platforms simultaneously.

The connector handles bidirectional sync for the core CRM objects: Contacts sync to Salesforce Contacts, HubSpot Companies sync to Salesforce Accounts, HubSpot Deals sync to Salesforce Opportunities, and email/call/meeting activities can sync via HubSpot's Salesforce Timeline feature. For most teams running marketing in HubSpot and sales in Salesforce, this covers roughly 80% of what they need.

What the native connector does not handle well — and where teams often get surprised:

• Custom objects: Custom object sync requires HubSpot Enterprise. If you are on Professional, custom objects in either system simply do not sync.
• Real-time sync: The connector polls on a 15-minute cycle, not in real time. If a rep updates a deal stage in Salesforce, HubSpot will not reflect it for up to 15 minutes. For most marketing automation use cases this is fine; for live pipeline reporting it creates lag.
• Complex workflow triggers: You cannot trigger Salesforce Process Builder or Flows directly from HubSpot sync events. The sync updates field values, which can then trigger Salesforce automation, but you have to design for this indirectly.
• Salesforce Campaigns: HubSpot lists do not map cleanly to Salesforce Campaign Members. This is a recurring frustration for teams trying to track marketing attribution inside Salesforce reports.

None of these are dealbreakers, but they are things to plan around before you flip the switch.

Integrate vs. Migrate — Which Is Right for Your Team?

This is the question that actually matters for most companies in the 10–100 employee range, and the answer is not the same for every team. Here is the decision framework we walk clients through.

Keep both tools and integrate them

This is the right call when your marketing team owns HubSpot deeply — email nurturing, landing pages, lead scoring, attribution — and your sales team lives in Salesforce. The two systems serve genuinely different buyers of software inside your org. Forcing one team to abandon their tool to satisfy the other almost always creates resentment and data quality problems.

You should also stay integrated (rather than consolidate) if marketing attribution is a business priority. HubSpot's attribution reporting is materially stronger than Salesforce's out of the box. If your VP Marketing is using HubSpot to prove pipeline contribution, pulling them out of it costs real insight.

Migrate HubSpot to Salesforce

This makes sense when: your sales team barely uses HubSpot (it was set up for marketing but sales adopted Salesforce), Salesforce is clearly your system of record for all revenue data, and you are paying for HubSpot without capturing much value. The migration to Salesforce also becomes compelling when you need features HubSpot cannot match — CPQ, territory management, complex approval hierarchies, or tight ERP integration.

Migrate Salesforce to HubSpot

The opposite scenario: a small team (typically under 20 reps) found themselves on Salesforce because someone bought it years ago, but the CRM has become a burden — too complex to configure, too expensive per seat, and underused because the UI intimidates the team. HubSpot's Sales Hub is a legitimate alternative for teams with a straightforward pipeline. If you are paying $150/seat/month for Salesforce Enterprise and your reps are logging calls in a spreadsheet because Salesforce feels heavy, this is worth evaluating seriously.

Setting Up the HubSpot Salesforce Integration: What to Expect

The initial installation is not the hard part. Here is what the process actually looks like:

• Install the connector. Navigate to the HubSpot App Marketplace, search for Salesforce, and install. You will need a HubSpot account with admin access and a Salesforce account with System Administrator profile.
• Authenticate Salesforce. The connector uses OAuth to connect to your Salesforce org. You can point it at a sandbox first (recommended) or production directly. Always start with a sandbox.
• Map objects. The connector defaults to Contact↔Contact, Company↔Account, Deal↔Opportunity. You review and confirm these mappings. This step sounds simple and takes about 20 minutes — the field mapping that comes next is where the real time goes.
• Configure sync direction. For each object, you choose: HubSpot to Salesforce only, Salesforce to HubSpot only, or bidirectional. Most teams use bidirectional for contacts and unidirectional (Salesforce to HubSpot) for deals/opportunities, since Salesforce is typically the system of record for pipeline.
• Set inclusion lists. Not every contact in HubSpot should sync to Salesforce, and not every Salesforce contact should appear in HubSpot. Inclusion lists let you filter: for example, only sync HubSpot contacts who have become Marketing Qualified Leads, or only sync Salesforce contacts assigned to US territories.
• Test with 5 records before going live. Create 5 test contacts in HubSpot and 5 in Salesforce (with distinct, fake email addresses). Enable sync for those records only. Verify that fields populate correctly on both sides, that ownership maps correctly, and that no duplicates are created. Only expand to your full dataset after the test passes.

The setup itself — excluding field mapping — takes a half day for a competent admin. Most teams get tripped up during field mapping, which we cover in the next section.

HubSpot Salesforce Field Mapping: The Part That Takes Longest

Field mapping is where the HubSpot Salesforce integration setup goes from “afternoon project” to “this is taking two weeks.” Here is why, and how to move through it faster.

Standard fields map automatically. First name, last name, email, phone, company name, deal name, deal amount, close date — these all have direct equivalents in both systems and the connector maps them by default. You review and approve; most teams have no issues here.

Custom fields require manual mapping. If your Salesforce org has custom fields — Lead Source detail, Territory, Product Interest, NPS Score, anything your team added over the years — none of those map automatically. You need to either create equivalent properties in HubSpot and map them, or decide that certain Salesforce fields do not need to sync. For orgs that have grown organically over 5+ years, this list can run to 40–80 fields. Auditing which ones actually matter takes time.

Data type mismatches cause silent failures. This is the most painful category. If a field is a picklist in Salesforce and a free-text property in HubSpot, the sync will either fail silently or push invalid values. Common mismatches:

• Salesforce picklist (with controlled values) vs. HubSpot single-line text — the text value will sync to Salesforce but fail validation if it does not match a picklist value exactly
• Salesforce checkbox vs. HubSpot boolean — usually maps correctly, but watch for null vs. false differences
• Salesforce date vs. HubSpot date — timezone handling can cause off-by-one-day errors on close dates, which creates reporting confusion
• Salesforce currency field vs. HubSpot number — decimal precision sometimes differs; $10,000.00 vs. $10,000 can trigger false “field changed” sync events

The HubSpot Salesforce two-way sync adds another wrinkle: when sync is bidirectional, you need to decide which system wins on conflict. If a contact's phone number is updated in HubSpot at the same time it is updated in Salesforce, which value survives? The connector's default is “most recently updated wins,” but you can configure field-level overrides (e.g., Salesforce always wins for Deal Amount, HubSpot always wins for Email Opt-Out Status).

Our recommendation: build a field mapping spreadsheet before you touch the connector. Column A: HubSpot property name. Column B: Salesforce field API name. Column C: data type in HubSpot. Column D: data type in Salesforce. Column E: sync direction. Column F: conflict resolution. This document becomes your source of truth and saves hours of back-and-forth debugging.

Common HubSpot Salesforce Integration Problems (And How to Fix Them)

Once the integration is live, these are the five problems that surface most often — and the specific fixes that actually work.

1. Duplicate records

Cause: The same contact exists in both systems before sync is enabled. When sync activates, the connector cannot match them (because the email addresses differ slightly, or one uses a personal email and the other uses a work email), so it creates a second record in each system.

Fix: Run a dedup pass in both HubSpot and Salesforce before enabling sync. In HubSpot, use the built-in Duplicates tool (Contacts > Actions > Manage Duplicates). In Salesforce, use Duplicate Management rules or a third-party tool like Cloudingo or DemandTools. Standardize email addresses as your primary match key. Only enable sync after both systems are clean.

2. Sync loops

Cause: System A updates a record, which syncs to System B, which triggers an update in System B (from an automation rule), which syncs back to System A, which triggers another update. This loop can run thousands of times and generates huge sync queues.

Fix: Use inclusion lists to control exactly which records sync, and audit your automation rules in both systems. If a Salesforce Workflow Rule updates a field every time a record is modified, and that same field syncs to HubSpot, you have a loop. The fix is usually either to exclude that field from sync, or to make the Salesforce automation conditional so it only fires when a human changes the record, not when a sync changes it.

3. Missing data after sync

Cause: A required field in Salesforce is not mapped from HubSpot. Salesforce rejects the record silently (or with an error that HubSpot logs but does not surface prominently).

Fix: Export your Salesforce required fields list and cross-reference it against your field mapping document. Any Salesforce required field that is not mapped from HubSpot must either be given a default value in Salesforce or be populated via HubSpot before sync is triggered.

4. Contact owner mismatch

Cause: HubSpot and Salesforce use different user IDs for the same person. The rep in Salesforce is “jsmith@company.com” but in HubSpot they were added with their personal email. The connector cannot match ownership, so records land as unowned or are assigned to the wrong user.

Fix: Before enabling sync, map HubSpot users to Salesforce users explicitly in the connector's User Mapping settings. Every user in both systems should have the same primary email address. This is worth enforcing as an IT policy before you start the integration project.

5. Activities not syncing

Cause: HubSpot email, call, and meeting logs are not syncing to Salesforce activity timelines. This is often because the Salesforce Timeline feature in HubSpot has not been enabled, or the user running the sync does not have the right Salesforce profile permissions to write to Task and Event objects.

Fix: Enable Salesforce Timeline in HubSpot Settings > Integrations > Salesforce > Activity Sync. Confirm the integration user in Salesforce has Create/Edit access on Task and Event objects. Note that activity sync runs on a separate cycle from record sync and may lag by up to 30 minutes.

HubSpot to Salesforce Migration: When It Makes Sense and What It Costs

A full HubSpot to Salesforce migration is a bigger project than most teams expect. Here is an honest breakdown of when to do it, what it involves, and what it costs.

When to migrate

The signal that it is time to migrate from HubSpot to Salesforce is usually one of three things: your sales team is already primarily working in Salesforce and HubSpot has become an orphaned marketing database, you are outgrowing HubSpot's sales features (no CPQ, no territory management, no ERP integration, limited forecasting), or you are consolidating systems after an acquisition and the acquiring company runs Salesforce.

What the migration involves

A realistic HubSpot to Salesforce migration covers six phases:

• Data audit: Export everything from HubSpot — contacts, companies, deals, activities, notes, emails. Assess data quality: duplicate records, invalid emails, missing required fields, contacts with no associated company. This audit typically uncovers 15–30% of records that need cleaning before they can land in Salesforce.
• Field mapping documentation: Every HubSpot property that you want to preserve needs a destination Salesforce field. Standard fields are straightforward. Custom HubSpot properties may require creating new custom fields in Salesforce.
• Owner mapping: Map every HubSpot contact owner (by email) to the correct Salesforce user. Departed employees need to be reassigned.
• Dedup before migration: Clean duplicates in HubSpot before export. It is much harder to merge duplicates after they land in Salesforce.
• Test migration in sandbox: Load a representative subset (500–1,000 records) into your Salesforce sandbox and validate against your field mapping document. Check every field type, all picklist values, and activity history.
• UAT and go-live: Run user acceptance testing with 3–5 reps in the sandbox. Address issues. Schedule the production migration during a low-activity window (Friday evening is common for US teams). Freeze HubSpot data changes during the cutover window.

After go-live: execute your HubSpot decommission plan. This means disabling HubSpot automation that may still be sending emails, archiving the HubSpot account (do not delete it immediately — keep it for 30–60 days as a reference), and training the team on Salesforce workflows.

HubSpot to Salesforce migration checklist

• Data audit complete (contacts, companies, deals, activities)
• Field mapping document finalized and signed off
• Owner mapping table complete (HubSpot user → Salesforce user)
• Dedup pass completed in HubSpot pre-export
• Salesforce sandbox custom fields created and validated
• Test migration (500 records) completed in sandbox
• UAT sign-off from 3+ end users
• Production migration scheduled (low-traffic window)
• HubSpot automation disabled or paused pre-cutover
• Go-live validation checklist completed post-migration
• HubSpot decommission plan in place (archive, not delete)

Timeline and cost

Realistic timeline for a HubSpot to Salesforce migration: 4–8 weeks. Smaller teams with cleaner data can land closer to 4 weeks. Teams with 50,000+ contacts, years of custom properties, and complex activity history should budget 8 weeks minimum.

HubSpot to Salesforce migration cost ranges from $4,000 to $15,000 for a managed engagement with a Salesforce partner. The range is wide because cost scales with: total record volume, number of custom fields requiring mapping, whether you need historical activity/email data migrated (activities are the hardest to migrate cleanly), and whether your Salesforce org needs customization to receive the data. A basic contacts/companies/deals migration for a team under 30 employees with reasonably clean data lands in the $4,000–$7,000 range. A complex migration with full activity history and significant Salesforce configuration work lands at $10,000–$15,000.

Salesforce to HubSpot Migration: When Salesforce Is Overkill

The reverse migration — moving your CRM data from Salesforce into HubSpot — is less common but increasingly relevant as more small US businesses discover they bought Salesforce for the brand name and are paying for complexity they do not use.

When it makes sense

Consider migrating from Salesforce to HubSpot when: your team is under 20 reps and does not need territory management, CPQ, or multi-business-unit hierarchy. The Salesforce license cost per seat ($75–$300/month depending on edition) is straining your budget relative to what you are getting. Your team members find Salesforce confusing and adoption is poor — reps are logging deals inconsistently, managers cannot trust the pipeline data. Your marketing team already runs HubSpot heavily and having two systems creates friction.

HubSpot Sales Hub Pro runs $90/seat/month (as of 2025) and includes pipeline management, sequences, meeting scheduling, and basic forecasting. For a 10-person sales team, the cost difference vs. Salesforce Professional ($80/seat/month, but always sold with implementation overhead and add-ons) is smaller than people expect — but the adoption difference is often dramatic.

Cost and timeline

Salesforce to HubSpot migrations tend to be faster and less expensive than the reverse, because HubSpot is more forgiving about data format and does not have the same field validation strictness as Salesforce. Typical cost: $2,000–$8,000. Typical timeline: 3–6 weeks. The lower cost reflects simpler data ingestion on the HubSpot side; the variance still comes from data volume, number of custom fields, and whether you are migrating historical activity data (emails, calls, notes) or just the contact/account/deal records.

Our Recommended Stack for US Teams with 10–100 Employees

There is no universal right answer, but after working with dozens of US companies in this size range, here is how the decision usually shakes out:

Use both (HubSpot Marketing Hub + Salesforce Sales Cloud)

Best for teams where marketing and sales are distinct functions with separate headcount. Your marketing team needs HubSpot's email, landing pages, forms, attribution, and lead scoring. Your sales team needs Salesforce's pipeline management, Salesforce CPQ, or an ERP integration. The integration cost ($1,500–$5,000 to set up, low ongoing maintenance) is easily justified if both tools are actively used. Typical team profile: 30–100 employees, dedicated marketing team of 3+, sales team of 5–20 reps.

Use Salesforce only

Best for sales-led companies with complex deal structures. You need Salesforce if: you have a CPQ requirement, you have multiple product lines with territory-based routing, you are integrating with an ERP (NetSuite, SAP, Sage), or you have a deal approval workflow with multiple layers. In these cases, Salesforce Marketing Cloud or Pardot (now Marketing Cloud Account Engagement) is a reasonable marketing solution to keep everything in one ecosystem. Typical team profile: 40–100 employees, product pricing complexity, existing Salesforce investment that is actually being utilized.

Use HubSpot only

Best for smaller teams with a straightforward sales process. If you have fewer than 20 reps, your deals do not require CPQ, you do not have complex territory rules, and your marketing team is the same people as your sales team (common at 10–25 employee companies) — HubSpot alone is the right call. The total cost of ownership is lower, adoption tends to be higher, and the integrated marketing + sales reporting in a single platform is genuinely useful at this stage. Typical team profile: 10–35 employees, founder-led sales, or a small team where everyone wears multiple hats.