Salesforce & HubSpot Sync
When marketing runs on HubSpot and sales runs on Salesforce, data silos kill your pipeline. Our bi-directional sync service connects both platforms with field-level precision, intelligent conflict resolution, and real-time monitoring. We configure contact, company, deal, and activity sync so every team works from the same data without manual imports, CSV exports, or reconciliation spreadsheets. Whether you need a simple contact sync or a full-scale enterprise data bridge with custom object mapping, we deliver configurations that stay reliable through every platform update.
HubSpot
Contacts
Deals
Companies
Activities
Custom Objects
Workflows
Salesforce
HubSpot
Contacts
Deals
Companies
Activities
Custom Objects
Workflows
By The Numbers
Syncs Configured
Data Accuracy
Records Synced
Avg. Setup Time
Why Sync Salesforce & HubSpot
Most growing organizations end up with marketing on HubSpot and sales on Salesforce. Marketing generates leads through HubSpot forms, landing pages, email campaigns, and content. Sales manages pipeline, quotes, and close in Salesforce. Without sync, these teams operate in separate data universes, leading to missed handoffs, duplicated records, conflicting reports, and revenue leakage that compounds every quarter.
- Unified Lead Handoff — Leads captured in HubSpot flow to Salesforce automatically with full engagement history, lead score, and source attribution intact
- Closed-Loop Reporting — Revenue data from Salesforce flows back to HubSpot so marketing can attribute campaigns to actual closed-won deals and optimize spend
- Single Source of Truth — Contact, company, and deal data stays consistent across both platforms without manual imports, exports, or reconciliation
- Team Productivity — Reps work in the platform they prefer without worrying about missing data or stale records in the other system
Bi-Directional Data Flow
Our sync configurations support true bi-directional data flow between Salesforce and HubSpot. Contacts created in either platform automatically appear in the other with all mapped properties synced. Updates flow in both directions based on your conflict resolution rules. This eliminates the need for manual data entry in either system and ensures that marketing and sales always have access to the same, current contact and company information regardless of where it was created or last updated.
Revenue Attribution
Closed-loop reporting is one of the most valuable outcomes of Salesforce-HubSpot sync. When deals close in Salesforce, the revenue data flows back to HubSpot and attributes to the original marketing campaign, content asset, ad click, or email sequence that generated the lead. Marketing teams can finally prove ROI on specific campaigns, channels, and content pieces with real revenue data instead of proxy metrics like MQLs or click-through rates.
Contact Lifecycle Continuity
Lifecycle stage mapping between HubSpot and Salesforce ensures that contacts progress through your funnel consistently across both platforms. When a HubSpot MQL is accepted by sales and converted to an opportunity in Salesforce, the HubSpot lifecycle stage updates to reflect the change. When deals close or are lost in Salesforce, HubSpot lifecycle stages and list memberships update accordingly, triggering the right nurture or win-back workflows automatically.
Activity History Sync
Sales reps in Salesforce see the full HubSpot engagement timeline including email opens, page visits, form submissions, and content downloads directly on the contact record. Marketing teams in HubSpot see Salesforce activity including logged calls, meetings, tasks, and email correspondence. This complete activity picture eliminates blind spots and gives both teams the context they need to have relevant conversations at every stage of the customer journey.
Sync Architecture
Our sync configurations are built on four pillars that ensure data accuracy, consistency, and reliability across both platforms.
Field Mapping
We map every relevant property between HubSpot and Salesforce with precision. Standard fields like name, email, phone, and company map directly. Custom properties in HubSpot map to custom fields in Salesforce with data type conversion where needed. Picklist values are aligned across both platforms. We document every mapping in a shared specification so your team has complete visibility into what syncs, in which direction, and how values are transformed between platforms.
Conflict Resolution
When the same record is updated in both platforms simultaneously, conflict resolution rules determine which value wins. We configure conflict rules at the field level so you can specify that HubSpot is the source of truth for marketing properties while Salesforce governs sales-owned fields. Time-based resolution uses the most recently updated value. We also support custom conflict logic for fields that require business-specific decision rules beyond simple timestamp comparison.
Filtering & Segmentation
Not every record should sync between platforms. We configure inclusion and exclusion filters so only relevant records flow across the bridge. Filter criteria can include lifecycle stage, lead score threshold, record type, owner, geography, or any custom property. This prevents test records, unqualified leads, and internal contacts from cluttering the other platform. Filters run on every sync cycle and automatically include or exclude records as their properties change.
Monitoring & Alerts
After go-live, we deploy monitoring that tracks sync health in real time. Dashboards show sync volume, error rates, queue depth, and latency metrics. Automated alerts fire when sync errors exceed thresholds, when records fail validation, or when the sync queue backs up beyond acceptable limits. We investigate root causes for any sync failures and resolve them before they impact your team’s data quality or workflow reliability.
Before & After Sync
The difference between disconnected CRMs and a properly synchronized stack is night and day.
Before Sync
- Manual CSV exports between platforms every week
- Duplicate contacts with conflicting data in each system
- Marketing cannot attribute campaigns to closed revenue
- Sales reps miss engagement context from HubSpot activities
- Lifecycle stages out of sync, causing wrong nurture sequences
- Hours spent on data reconciliation and cleanup each month
- No single source of truth for pipeline or forecast reporting
- Lead handoff delays cost opportunities while data is in transit
After Sync
- Real-time bi-directional sync eliminates manual data transfers
- Deduplication rules prevent and merge duplicate records automatically
- Closed-loop attribution connects marketing spend to actual revenue
- Full HubSpot engagement timeline visible on Salesforce contact records
- Lifecycle stages map and update across platforms automatically
- Zero hours spent on manual data reconciliation or CSV imports
- Unified pipeline reporting across both platforms from a single data set
- Instant lead handoff with full context the moment a lead qualifies
Common Sync Scenarios
Every sync configuration is tailored to your specific data model and business processes. Here are the most common scenarios we configure between Salesforce and HubSpot.
Lead & Contact Sync
Contact and lead sync is the foundation of every Salesforce-HubSpot integration. We map HubSpot contacts to Salesforce leads or contacts based on your lead management model. When a new contact is created in HubSpot through a form submission, import, or manual entry, the sync creates a corresponding lead or contact in Salesforce with all mapped properties. Updates flow bi-directionally based on conflict resolution rules. We configure lifecycle stage mapping so HubSpot MQLs convert to Salesforce leads, and Salesforce lead conversions update HubSpot lifecycle stages automatically. Deduplication rules prevent duplicate records based on email address or custom match criteria.
Deal & Opportunity Sync
Deal sync connects HubSpot deals to Salesforce opportunities so both platforms reflect the same pipeline data. We map deal stages between HubSpot and Salesforce pipelines, sync deal amounts, close dates, and associated contacts, and configure which platform is the source of truth for pipeline management. When a deal stage changes in Salesforce, the HubSpot deal updates accordingly, and vice versa. Associated contact roles map between platforms so both teams see who is involved in each deal. Revenue data syncs back to HubSpot for closed-loop marketing attribution and campaign ROI reporting.
Company & Account Sync
Company sync ensures that organizational data stays consistent across both platforms. HubSpot companies map to Salesforce accounts with properties like industry, revenue, employee count, and custom fields syncing bi-directionally. When a new company is created in either platform, the sync creates a matching record in the other system. Account hierarchy in Salesforce can map to parent-child company relationships in HubSpot. Account owner assignments sync so the right sales rep is always associated with the right account in both platforms. Domain-based matching prevents duplicate company records.
Activity & Task Sync
Activity sync gives both teams visibility into the other platform’s engagement history. HubSpot email opens, link clicks, page visits, form submissions, and meeting bookings appear on the Salesforce contact timeline as activities. Salesforce logged calls, completed tasks, sent emails, and meeting notes appear on the HubSpot contact timeline. This bi-directional activity visibility eliminates the blind spots that cause awkward duplicate outreach, missed context in conversations, and incomplete customer history. We configure which activity types sync and how they display in each platform.
Custom Object Sync
For organizations with custom objects in Salesforce or custom objects in HubSpot (Enterprise tier), we configure sync between custom data models that extend beyond standard contacts, companies, and deals. Common examples include syncing product usage records, subscription data, project milestones, or partner records between platforms. Custom object sync requires careful property mapping, relationship association rules, and sync direction configuration. We build and test custom object sync in sandbox environments before production deployment to ensure data integrity and correct relationship mapping.
Native vs Custom Sync
There are multiple approaches to syncing Salesforce and HubSpot. We evaluate the best fit based on your data complexity, volume, and business requirements.
HubSpot Native Salesforce Integration. HubSpot offers a built-in Salesforce integration that handles bi-directional contact, company, deal, and activity sync out of the box. The native integration is the fastest path to basic sync and is included with HubSpot Professional and Enterprise tiers. It supports field mapping, inclusion lists, and basic conflict resolution. For many organizations with straightforward sync requirements, the native integration delivers everything needed. We configure the native integration with optimized field mappings, smart inclusion filters, and proper lifecycle stage mapping to maximize its effectiveness.
Operations Hub Data Sync. For organizations using HubSpot Operations Hub, the Data Sync feature provides an alternative sync engine with real-time bi-directional sync, custom field mapping, and built-in deduplication. Operations Hub Data Sync supports more granular conflict resolution and sync filtering than the standard native integration. It also extends to other platforms beyond Salesforce, making it a better choice for organizations that need to sync multiple systems through a single, consistent framework.
Custom Middleware Sync. For complex requirements that exceed the capabilities of native integrations, we build custom sync solutions using middleware platforms like MuleSoft, Zapier, Make, or custom application code. Custom sync supports advanced transformation logic, complex conditional routing, multi-step data processing, and custom object sync that native integrations cannot handle. Custom sync is appropriate for organizations with high data volumes, complex business rules, or requirements for syncing data types that native integrations do not support. We design custom sync architectures with fault tolerance, retry logic, and comprehensive error handling.
Sync Configuration Options
Every sync is configured with these core settings to match your specific data model and business rules.
Sync Direction
Each property mapping is configured with a sync direction: HubSpot to Salesforce, Salesforce to HubSpot, or bi-directional. This allows you to designate the source of truth on a per-field basis. Marketing-owned properties like lead source and campaign data typically sync from HubSpot to Salesforce, while sales-owned fields like deal stage and close date sync from Salesforce to HubSpot. Bi-directional sync is used for shared fields where either team may update the value.
Inclusion & Exclusion Filters
Filters control which records sync between platforms. Inclusion filters specify criteria that records must meet to be synced, such as minimum lead score, specific lifecycle stages, or assigned owner. Exclusion filters prevent specific records from syncing, such as test contacts, internal employees, or competitors. Filters evaluate dynamically, so records automatically start or stop syncing as their properties change. This keeps both platforms clean and prevents unnecessary data transfer.
Lifecycle Stage Mapping
Lifecycle stages in HubSpot and lead statuses in Salesforce must be aligned for consistent funnel reporting. We create a mapping table that defines how each HubSpot lifecycle stage corresponds to Salesforce lead status or opportunity stage. When a contact progresses through the funnel in either platform, the corresponding stage updates in the other system automatically. This ensures that marketing and sales reports reflect the same funnel metrics and that contacts receive the right nurture content based on their current stage.
Deduplication Rules
Duplicate records are one of the most common problems in multi-CRM environments. We configure deduplication rules that match records based on email address, domain, company name, or custom match criteria before creating new records. When a potential duplicate is detected, the sync merges property values according to your conflict resolution rules instead of creating a new record. We also run initial deduplication before enabling sync to clean up existing duplicates and establish a clean baseline for ongoing sync operations.
Sync Deliverables
Every Salesforce & HubSpot sync engagement includes these deliverables.
- Complete field mapping specification with sync direction and data types
- Conflict resolution rules documented at the field level
- Inclusion and exclusion filter configuration
- Lifecycle stage and pipeline mapping between platforms
- Initial data deduplication and cleanup before sync activation
- Configured and tested sync in production with validation report
- Sync monitoring dashboard with error tracking and volume metrics
- Operational runbook with troubleshooting procedures for common sync issues
- Admin training session (recorded) on managing sync settings and resolving errors
- 30-day hypercare period with active monitoring and immediate issue resolution
Related Services
Frequently Asked Questions
The native HubSpot-Salesforce integration is sufficient for most organizations with standard sync requirements including contacts, companies, deals, and activities. We recommend starting with the native integration and configuring it properly with optimized field mappings and filters. If you need custom object sync, complex transformation logic, advanced conditional routing, or data volumes that exceed native capacity, we build a custom sync solution using middleware or custom application code. We evaluate your specific requirements during discovery and recommend the approach that best balances cost, complexity, and capability.
We configure conflict resolution rules at the field level. For each synced property, you designate which platform is the source of truth, or whether the most recently updated value should win. Marketing-owned fields like lead source and engagement data typically give HubSpot priority. Sales-owned fields like deal stage and close date typically give Salesforce priority. For shared fields, timestamp-based resolution uses the most recent update. We document every conflict rule in the field mapping specification so your team has complete clarity on how data conflicts are resolved.
No, when configured properly. We implement deduplication rules that match existing records by email address, domain, or custom criteria before creating new records. We also run an initial deduplication process before activating sync to clean up any existing duplicates. The sync engine checks for matching records on every cycle and merges data into existing records rather than creating duplicates. If a duplicate is detected after sync is active, monitoring alerts notify your team so it can be resolved immediately.
Yes. Custom object sync is available for organizations with HubSpot Enterprise tier and Salesforce custom objects. We map custom object properties, configure relationship associations, and set sync direction and conflict rules specific to each custom object type. Common examples include syncing product usage records, subscription data, partner information, or project milestones between platforms. Custom object sync requires thorough sandbox testing before production deployment to ensure data integrity and relationship mapping accuracy.
The native HubSpot-Salesforce integration syncs data within a few minutes of a change occurring. Operations Hub Data Sync provides near-real-time sync with updates flowing within seconds. Custom middleware sync can be configured for real-time event-driven sync using webhooks and platform events, or scheduled batch sync on intervals you define. The appropriate sync frequency depends on your use case. Lead handoff workflows benefit from real-time sync, while reporting data may only need hourly or daily sync cycles.
The native HubSpot-Salesforce integration requires HubSpot Professional or Enterprise in any Hub (Marketing, Sales, Service, or Operations). On the Salesforce side, Professional Edition or above is required for API access. Salesforce Enterprise and Unlimited editions provide higher API limits and support for Platform Events. HubSpot Operations Hub adds advanced Data Sync capabilities, custom-coded actions, and data quality features. We evaluate your current editions during discovery and advise on any tier upgrades that would benefit your sync configuration.
Before activating ongoing sync, we run an initial data migration to populate both platforms with a consistent baseline. We export records from both platforms, deduplicate and merge them based on match criteria, resolve conflicting property values according to your rules, and import the clean dataset into both systems. This ensures that sync starts from a clean, consistent state rather than layering new sync logic on top of existing data inconsistencies. The initial migration is thoroughly tested in sandbox before production execution.
Configuration of the native HubSpot-Salesforce integration with field mapping, filters, lifecycle stage mapping, and monitoring typically costs $2,500 to $5,000 depending on the number of properties and complexity of your data model. Custom middleware sync solutions for advanced requirements range from $5,000 to $15,000. Initial data cleanup and deduplication before sync activation is quoted separately based on data volume. We provide fixed-price quotes after the discovery phase so there are no surprises.
Every sync deployment includes monitoring dashboards and automated alerts. When sync errors occur, alerts fire immediately with error details and affected records. Common causes include API limit exhaustion, validation rule failures, required field violations, and permission issues. Our monitoring identifies the root cause and we resolve errors before they compound into larger data quality problems. The 30-day hypercare period ensures that any post-launch issues are addressed immediately with priority response.
Yes. Every sync engagement includes a 30-day hypercare period with active monitoring and immediate issue resolution. Beyond that, we offer monthly support retainers that include proactive monitoring, error resolution, platform update testing for both Salesforce and HubSpot releases, sync performance optimization, and priority response times. We also provide ad-hoc support for adding new field mappings, adjusting filters, or extending sync to additional object types as your business needs evolve.
Ready to unify your Salesforce and HubSpot data?