Introduction
Sales and marketing teams running both HubSpot and Salesforce is one of the most common (and most frustrating) setups we encounter. Marketing qualifies leads in HubSpot, sales closes them in Salesforce, and somewhere in between, data falls through the cracks. "We just need our CRMs to talk to each other" is a phrase we hear on discovery calls almost every week.
The HubSpot and Salesforce integration eliminates the manual handoffs, duplicate contacts, and mismatched deal stages that slow your revenue engine. When connected properly, lead data flows seamlessly between both platforms, giving marketing visibility into closed deals and sales full context on every prospect's journey.
At flowmondo, we've built Salesforce and HubSpot integrations for revenue teams across consulting, SaaS, and professional services. With 2,900+ solutions delivered and deep expertise across HubSpot integrations, Salesforce integrations, and broader CRM integration services, we know exactly where the setup guides end and real-world complexity begins.
Here are some quick examples of common automations people build.
HubSpot to Salesforce
• When a contact becomes an MQL in HubSpot, automatically create or update a Lead in Salesforce with full engagement history
• When a HubSpot form is submitted, create a new Contact or Lead in Salesforce and assign to the correct sales rep
• When a deal stage changes in HubSpot, update the corresponding Opportunity stage in Salesforce
• When a HubSpot list is updated, sync the segment to a Salesforce Campaign for targeted outreach
Salesforce to HubSpot
• When an Opportunity closes in Salesforce, push closed-loop revenue data back to HubSpot for accurate ROI reporting
• When a Salesforce Contact's owner changes, update the HubSpot contact owner to keep assignment in sync
• When a custom field is updated in Salesforce, mirror the change in HubSpot to keep both CRMs consistent
• When a Salesforce Account is created, generate a matching Company record in HubSpot with all associated contacts
Multi-Step Workflow
• Lead scoring chain: When a contact hits a score threshold in HubSpot, create a Salesforce Lead, notify the assigned rep via Slack, and log the event in Google Sheets for pipeline tracking
Connecting HubSpot and Salesforce unlocks practical automation across your entire revenue cycle. Here are the use cases we build most often for clients running both CRMs.
CRM Data Migration
Migrate your CRM data without losing a single record or relationship.
Teams consolidating from Salesforce to HubSpot (or vice versa) need to move years of contacts, opportunity history, and custom field data without losing relationships.
Build a structured migration workflow that extracts records, transforms field values to match the target schema, deduplicates, and loads data in batches with validation.
Clean, complete data in the target CRM from day one. No lost records, no broken associations.
Deal Stage and Lifecycle Sync
Align your pipeline stages so marketing and sales never contradict each other.
When a deal progresses in Salesforce, HubSpot doesn't know. Marketing continues sending top-of-funnel content to prospects deep in a sales conversation, damaging the buyer experience.
Sync Salesforce Opportunity stages back to HubSpot deal stages and lifecycle properties in real time. Trigger appropriate nurture sequences or suppress marketing emails based on deal position.
Prospects receive relevant communications at every stage. Sales and marketing alignment improves measurably.
Bidirectional Contact and Company Sync
One contact record. Two CRMs. Always in sync.
Both CRMs hold contact records, and without a reliable sync, the same person ends up with different details in each system. "Our sales team kept updating contacts in Salesforce and marketing had no idea" is a common discovery call confession.
Set up a bidirectional sync that keeps contact fields consistent across both platforms. Include conflict resolution rules so the most recently updated record wins, with logging for audit trails.
A single source of truth across both CRMs. No more conflicting data or hours spent reconciling spreadsheets.
Closed-Loop Revenue Attribution
Close the loop between marketing spend and actual revenue.
Marketing has no visibility into which campaigns generate revenue. "We had no idea which campaigns were actually driving revenue until deals closed" is something we hear constantly. Salesforce holds the closed-won data, but it never reaches HubSpot.
When an Opportunity closes in Salesforce, push the revenue amount, close date, and deal stage back to HubSpot. Map it to the original campaign or source that generated the lead.
Marketing can prove ROI by campaign and channel. Budget decisions are based on actual revenue data rather than vanity metrics.
Automated Lead Handoff from Marketing to Sales
Get qualified leads into sales hands in seconds, not hours.
Marketing qualifies leads in HubSpot, but sales reps manually import them into Salesforce. Leads sit in limbo for hours, and hot prospects go cold before anyone follows up.
When a contact reaches MQL status in HubSpot, automatically create a Lead in Salesforce with engagement history, score, and source attribution. Assign to the correct rep based on territory or round-robin rules.
Lead response times drop from hours to minutes. Sales reps get full marketing context without leaving Salesforce.
From discovery call to implementation in days, not months.
Book a call
Speak with a friendly and knowledgable integration expert and explain your use-case.
Get insights
Based on what you have told your integration pro about your use-case, you will receive expert analysis and clear next steps.
Say go
We will scope and estimate your custom solution and provide you with our detailed design and implementation plan. You just say the word, and we will deliver.
Several platforms handle this integration. Here's how each one works, with honest guidance, based on 2,700+ solutions delivered on which suits different needs. Spoiler alert: We can help you with any of these options.
Integrate HubSpot and Salesforce with Native HubSpot Connector
- Zero additional cost on the right HubSpot tier
- Simple setup within HubSpot's settings interface
- Native support for inclusion/exclusion lists
- Revenue data pass-back for attribution reporting
- Limited custom object support
- Basic conflict resolution with little control
- No conditional logic or branching within sync rules
A solid starting point for basic use cases. Most teams we work with outgrow it within 6-12 months as Salesforce customisation increases. Main gaps: custom object limitations and no conditional sync logic.
HubSpot's built-in Salesforce integration on Professional and Enterprise tiers with contact sync, company sync, and revenue data pass-back.
Teams already on HubSpot Professional or Enterprise who need basic contact and deal sync without adding another platform.
Use this if your sync needs are straightforward (standard contacts, companies, deals). Move to Make or Zapier when you need custom objects or more control over conflict resolution.
Integrate HubSpot and Salesforce with n8n
- Self-hosting gives complete control over data flow and storage
- Highly flexible with custom code nodes for edge cases
- Can handle complex Salesforce custom objects directly
- No per-connector pricing premium
- Requires technical confidence to set up and maintain
- Smaller template library for this pair than Zapier or Make
- Less polished UI for non-technical users
n8n shines when your Salesforce instance is heavily customised. Code nodes handle custom objects and Apex trigger responses directly. Self-hosting means CRM data never passes through a third-party cloud.
Open-source workflow automation with nodes for both HubSpot and Salesforce. Self-hostable for full data control, or available as n8n Cloud.
Technical teams wanting full control over integration infrastructure, or organisations with strict data residency requirements.
The right choice for technical teams with customised Salesforce instances who want self-hosted control. Not the fastest path for non-technical users, but offers the most flexibility.
Integrate HubSpot and Salesforce with Make
- Router modules enable bidirectional sync in a single scenario
- Superior data transformation tools for field mapping and value conversion
- Operations-based pricing is significantly cheaper at scale
- Built-in error handling with detailed execution logs
- Steeper learning curve than Zapier
- Scenario design for bidirectional CRM sync requires planning
- Some advanced Salesforce features need careful module configuration
Make handles this pair exceptionally well. Router and filter modules let you build bidirectional sync as a single scenario with loop prevention built in. For teams syncing thousands of records, the pricing model is substantially more cost-effective than Zapier's.
Visual scenario builder with routers, advanced data transformation, and comprehensive modules for both platforms. Strong for complex multi-step workflows.
Revenue ops teams needing bidirectional sync with conditional logic, field transformations, and high-volume processing.
Our top recommendation for most HubSpot-Salesforce integrations, especially when bidirectional sync, custom field mapping, or high record volumes are involved.
Integrate HubSpot and Salesforce with Zapier
- Fastest time-to-value for simple workflows
- Huge template library for this CRM pair
- Intuitive interface with minimal learning curve
- Reliable error notifications and retry logic
- Bidirectional sync requires multiple Zaps, increasing complexity
- Task-based pricing becomes expensive at high volumes
- No built-in deduplication logic
- Limited data transformation capabilities
Zapier's HubSpot and Salesforce connectors are mature. The main limitation is bidirectional sync: you need separate Zaps per direction with careful filter configuration for loop prevention. Watch task consumption closely for high-volume syncs.
Extensive trigger and action library for both HubSpot and Salesforce. Hundreds of pre-built templates for common CRM sync scenarios.
Teams wanting the fastest setup for simple one-way automations like pushing new HubSpot contacts to Salesforce.
Zapier is the right choice for quick, reliable one-way syncs. Less suited for complex bidirectional workflows or high-volume scenarios where task costs add up.
Limitations and Gotchas
Bidirectional Sync Loops
In a bidirectional sync, updating a contact in HubSpot triggers a Salesforce update, which triggers a HubSpot update, creating an infinite loop. This can burn through API limits and automation credits within minutes.
Implement loop prevention using timestamp comparisons or a dedicated "sync source" field. In Make, use a filter checking whether the change originated from the integration itself. In Zapier, add a filter step comparing last modified vs last sync timestamps. We build this into every bidirectional CRM integration we deliver.
Duplicate Record Creation
When syncing customers or invoices between QuickBooks and Salesforce, there is a risk of creating duplicate records if the automation does not check for existing matches before creating new ones. This is particularly common during the initial sync or when records are created simultaneously in both platforms.
Always include a lookup step before any create action. Search QuickBooks for an existing customer by email or company name before creating a new one. In Make, use a search module followed by a router that branches based on whether a match was found. In Zapier, use a "Find" step before the "Create" step and enable the "Create if not found" option where available.
Field Type and Picklist Mismatches
HubSpot and Salesforce handle certain fields differently. Picklist values may not match ("Qualified Lead" vs "SQL"). Date formats, currency fields, and multi-select picklists can cause sync failures or silent data corruption.
Create a comprehensive field mapping document before building anything. Map every picklist value explicitly. Use transformation steps in Make or code nodes in n8n to convert values during sync. Test multi-select picklists thoroughly: they're a known pain point across all platforms.
Salesforce API Rate Limits
Salesforce enforces daily API call limits based on your edition. A high-frequency bidirectional sync can burn through these limits quickly, especially during initial data loads. Once you hit the ceiling, all API-dependent integrations stop.
Use batch processing for bulk operations and schedule large syncs during off-peak hours. Monitor your Salesforce API usage dashboard daily during the first two weeks. Make's operations model processes multiple records per operation, reducing API consumption.
How flowmondo can help you
Connecting two enterprise CRMs is a different challenge from linking a form to a spreadsheet. Field mapping alone can take hours when you're dealing with custom objects, picklist values, and lifecycle stage logic. We handle the entire process: scoping your data model, building the integration, testing edge cases, and setting up error monitoring.
Our team holds certifications across multiple integration platforms and has delivered 2,900+ automation solutions for 975+ businesses. We specialise in complex CRM integrations where data integrity is non-negotiable.
For teams already running both HubSpot and Salesforce, the fastest path to a working integration is a 30-minute discovery call. We'll map your data flow, recommend the right platform, and give you a clear timeline. Book a free call and let's get your CRMs talking properly.
Stop Paying Two CRM Licences to Get Half the Picture. Let's Fix That This Week.
Method used
App(s) involved
Overview
We developed reporting dashboards in Airtable to provide BB7 with real-time visibility across invoicing and forecasting workflows. The system tracks sync success rates, highlights errors, and surfaces trends for proactive resolution. This monitoring layer reduced time spent diagnosing issues and gave stakeholders confidence in data accuracy and performance.
Frequently asked questions
Everything you need to know about Zapier.
Still have questions?
Speak with one of our experts.
How do I connect HubSpot to Salesforce?
The fastest route is using an integration platform like Zapier, Make, or n8n. Each offers pre-built connectors for both HubSpot and Salesforce. HubSpot also offers a native Salesforce integration on its Professional tier and above. For complex requirements involving custom objects or bidirectional sync, working with an integration specialist typically saves weeks of trial and error.
What can I automate between HubSpot and Salesforce?
Common automations include syncing leads and contacts bidirectionally, updating deal and opportunity stages across both CRMs, pushing closed-loop revenue data from Salesforce back to HubSpot for marketing attribution, and keeping custom field values in sync. You can also automate campaign member syncing, activity logging, and lead assignment routing.
Do I need coding knowledge to integrate HubSpot and Salesforce?
No. Zapier and Make are fully no-code platforms. n8n is low-code and offers more flexibility for technical users. HubSpot's native Salesforce connector also requires no coding. The real complexity lies in mapping your data model correctly: understanding which fields correspond, how lifecycle stages align, and what happens when records conflict.
What are the limitations of connecting HubSpot and Salesforce?
Key limitations include Salesforce daily API call limits (which vary by edition), custom object mapping complexity, picklist value mismatches, and duplicate record creation if deduplication rules aren't configured. HubSpot's native integration also restricts which field types sync and doesn't support all custom object relationships.
Which is better for HubSpot and Salesforce: Zapier or Make?
For simple one-way syncs, Zapier is faster to set up. For complex bidirectional syncs with conditional logic and field transformations, Make offers significantly more control with its visual scenario builder and router modules. Make's execution model also handles high-volume record processing more cost-effectively.
How long does it take to set up a HubSpot Salesforce integration?
A basic one-way lead sync can be set up in under an hour. Full bidirectional integration with custom field mapping and deduplication typically takes 1-3 days with an experienced team. Complex setups involving custom objects and historical migration may take 1-2 weeks. Working with a specialist significantly reduces setup time.