Part 1 of 5 in the HubSpot-Salesforce Integration Series by Vantage Point
If your organization uses HubSpot for marketing and Salesforce for sales, you already know the frustration of disconnected data. Leads generated in HubSpot don't automatically appear in Salesforce. Deal updates in Salesforce don't reflect in HubSpot reporting. Teams waste hours reconciling spreadsheets, and valuable customer insights slip through the cracks.
The native HubSpot-Salesforce connector solves this — but only when configured correctly. A poorly planned integration leads to duplicate records, overwritten fields, and sync errors that erode trust in your data.
This is Part 1 of a 5-part series on mastering the HubSpot-Salesforce integration. In this post, we'll cover the foundational building blocks: sync rules, sync directions, and field mappings. By the end, you'll understand exactly how to configure each element so your data flows cleanly between both platforms.
Series Overview:
Part 1: Sync Rules, Directions, and Field Mappings (this post)
Part 2: Inclusion Lists and Selective Sync Strategies
Part 3: Custom Object Sync and Advanced Mappings
Part 4: Common Sync Errors and Troubleshooting
Part 5: Optimization, Monitoring, and Long-Term Maintenance
The native HubSpot-Salesforce connector is a built-in integration available on HubSpot Professional and Enterprise plans. It connects directly to your Salesforce org via API, enabling real-time, bidirectional synchronization of records between both platforms.
The connector supports these standard objects out of the box:
| HubSpot Object | Salesforce Object | Notes |
|---|---|---|
| Contacts | Leads / Contacts | HubSpot Contacts can sync to either Salesforce Leads or Contacts |
| Companies | Accounts | Mapped by company name or domain |
| Deals | Opportunities | Includes deal stage and pipeline mapping |
| Activities | Tasks / Events | Engagement data like emails, calls, meetings |
| Tickets | Cases | Service-related records (Enterprise only) |
On HubSpot Enterprise plans, you can also sync up to 10 custom objects per account, enabling specialized data models unique to your business.
The integration user's permissions in Salesforce determine which records and fields HubSpot can access. This is a critical security and data governance consideration we'll explore in detail throughout this series.
Sync direction is the single most important configuration decision you'll make. It determines which platform "wins" when the same field is updated in both systems.
1. HubSpot → Salesforce (One-Way)
Data flows only from HubSpot to Salesforce. Updates made in Salesforce are not pushed back to HubSpot.
Best for: Marketing-owned data like lead score, campaign source, lifecycle stage, and form submission data that originates in HubSpot.
2. Salesforce → HubSpot (One-Way)
Data flows only from Salesforce to HubSpot. Updates in HubSpot do not push to Salesforce.
Best for: Sales-owned data like opportunity stage, revenue amounts, close dates, and account ownership that lives in Salesforce.
3. Bidirectional (Two-Way Sync)
Data flows in both directions. The most recently updated value wins when conflicts occur.
Best for: Shared fields like phone number, email address, company name, and contact owner — fields that either team might update.
| Data Type | Recommended Direction | Rationale |
|---|---|---|
| Lead Score | HubSpot → Salesforce | Marketing calculates; sales consumes |
| Lifecycle Stage | HubSpot → Salesforce | Marketing manages the funnel progression |
| Lead Source | Salesforce → HubSpot | Often first captured in Salesforce |
| Deal Stage | Salesforce → HubSpot | Sales owns the pipeline |
| Revenue / Amount | Salesforce → HubSpot | Finance and sales manage revenue data |
| Email Address | Bidirectional | Updated by either team |
| Phone Number | Bidirectional | Updated by either team |
| Contact Owner | Bidirectional | Assignment may happen in either system |
| Mailing Address | Salesforce → HubSpot | Address fields have data type constraints |
Pro Tip from Vantage Point: Start with one-way sync for most fields and only enable bidirectional sync for fields that truly need it. This dramatically reduces conflict scenarios and makes troubleshooting easier.
Field mappings are the rules that connect specific HubSpot properties to specific Salesforce fields. Getting these right is essential for clean data flow.
Standard Mappings are pre-configured defaults that HubSpot provides — common fields like first name, last name, email, and phone that map automatically between platforms. These cover basic contact and company information.
Custom Mappings let you connect any HubSpot property to any Salesforce field, as long as the data types are compatible. This is where most of your configuration work happens.
Not all field types can sync with each other. Here's what works:
| HubSpot Property Type | Compatible Salesforce Field Type |
|---|---|
| Single-line text | Text, Text Area |
| Multi-line text | Text Area, Long Text Area |
| Number | Number, Currency, Percent |
| Dropdown select | Picklist |
| Multiple checkboxes | Multi-Select Picklist |
| Date picker | Date |
| Checkbox (boolean) | Checkbox |
Critical rule: Dropdown and picklist values must match exactly — including capitalization. If HubSpot has "Enterprise" and Salesforce has "enterprise," the sync will fail for that field.
Sync rules determine what happens when a field has different values in HubSpot and Salesforce. They work alongside sync direction to govern data flow.
1. Prefer Salesforce Unless Blank
HubSpot updates the field only if the Salesforce value is empty. Once Salesforce has data, it always takes precedence.
Use case: Default values and enrichment — let HubSpot fill in gaps without overwriting sales-entered data.
2. Always Use Salesforce
Salesforce always wins, regardless of what's in HubSpot. The HubSpot value is overwritten on every sync.
Use case: Data that should be exclusively owned by Salesforce, like territory assignment or account tier.
3. Two-Way (Most Recent Wins)
Both platforms can update the field. The platform with the most recent timestamp wins.
Use case: Shared fields like phone number or email that either team might update.
4. Don't Sync
The field is mapped but sync is completely disabled. Useful for temporarily pausing a field without removing the mapping.
Here's a real-world scenario: A sales rep updates a contact's phone number in Salesforce at 2:00 PM. A marketing coordinator updates the same phone number in HubSpot at 2:15 PM.
Understanding these scenarios is crucial for preventing unexpected data overwrites.
One of the biggest challenges in this integration is the data model mismatch between the two platforms.
This is the most common source of confusion:
When syncing, you must decide: should new HubSpot Contacts create Salesforce Leads or Contacts? Most organizations default to creating Leads, then use Salesforce's lead conversion process to promote them.
Vantage Point's recommendation: Use a HubSpot workflow with a custom field (e.g., "Salesforce Lead ID") to identify which records are Leads vs. Contacts. This prevents duplicate creation and keeps both systems aligned during the lead-to-contact conversion process.
| Scenario | HubSpot Action | Salesforce Result |
|---|---|---|
| New marketing lead | Contact created in HubSpot | Lead created in Salesforce |
| Lead qualifies | Lifecycle stage updated | Lead converted to Contact + Account |
| Deal initiated | Deal created in HubSpot | Opportunity created in Salesforce |
| Company enriched | Company updated | Account updated |
| Support ticket | Ticket created | Case created (Enterprise) |
Setting up the HubSpot-Salesforce integration correctly from the start saves weeks of troubleshooting later. Here are the practices we recommend at Vantage Point based on hundreds of integration implementations.
The native connector syncs in near real-time. When a record is created or updated in either system, the change typically propagates within a few minutes. High-volume environments (100,000+ records) may experience slight delays during peak sync periods.
Yes, HubSpot Enterprise plans support syncing up to 10 custom objects. You'll need to create matching custom objects in HubSpot, configure field mappings, and set association rules. We'll cover this in detail in Part 3 of this series.
Changing sync direction does not retroactively update existing records. It only affects future changes. If you switch from "Always Use Salesforce" to "Two-Way," historical data in HubSpot won't automatically update — only new edits going forward will follow the new rule.
When a Salesforce Lead is converted to a Contact, the native connector updates the HubSpot record to reflect the new Salesforce Contact ID. Use a HubSpot workflow to update the lifecycle stage automatically when conversion occurs. This ensures both systems stay aligned.
Yes, HubSpot can sync with Salesforce Person Accounts, but the mapping is slightly different. Person Accounts combine Contact and Account into a single record in Salesforce, so your field mappings need to account for this merged data model.
The native connector is free with HubSpot Professional/Enterprise and handles standard sync scenarios well. Third-party tools (like MuleSoft, Workato, or middleware platforms) offer advanced features like complex data transformations, custom sync schedules, higher volume support, and multi-system orchestration. Organizations with complex needs often benefit from a hybrid approach.
No, the native connector supports a one-to-one relationship: one Salesforce org per HubSpot portal. If you need multi-org sync, you'll need a middleware solution — which Vantage Point can help architect using platforms like MuleSoft.
The HubSpot-Salesforce integration is one of the most powerful CRM connections available — but its value depends entirely on how well you configure sync rules, directions, and field mappings. Getting these foundational elements right ensures clean data, aligned teams, and reliable reporting.
In Part 2 of this series, we'll dive into inclusion lists and selective sync strategies — how to control exactly which records sync between platforms and prevent data pollution.
Need help with your HubSpot-Salesforce integration? Vantage Point is a certified partner for both Salesforce and HubSpot, with deep expertise in CRM integration, data architecture, and automation. Whether you're setting up a new integration or optimizing an existing one, our team can help you get it right.
👉 Contact Vantage Point to schedule a free integration assessment.
Vantage Point is a certified Salesforce and HubSpot partner specializing in CRM implementation, integration, and optimization. With expertise spanning Salesforce (Sales Cloud, Service Cloud, Experience Cloud), HubSpot CRM, MuleSoft integration, Data Cloud, and AI-powered automation, Vantage Point helps organizations of all sizes build connected, intelligent customer platforms. Learn more at vantagepoint.io.