What to Look for in HubSpot-Salesforce Sync: A Buyer's Guide to HubSpot Salesforce Integration Consultants
The connector between HubSpot and Salesforce installs in an afternoon. The decisions behind it (which system owns each field, how a lead becomes an opportunity, who gets it next) decide whether marketing and sales trust the same numbers. This guide shows how to judge the consultants who make those decisions.
Key Takeaways
- The best HubSpot Salesforce integration consultants start with a field-by-field system-of-record decision, not with the install. The connector gives every mapped field one of four sync rules, and those rules decide which team's data wins.
- Lifecycle design is where most integrations quietly fail. Lifecycle stage updates from Salesforce only move forward, depend on opportunity contact roles, and a HubSpot stage change never converts a Salesforce lead.
- Revenue handoff needs an owner model that matches exactly across both systems. Owner sync needs an exact name-and-email match with an active Salesforce user, or records fall back to the integration user.
- A credible consultant can tell you the API budget before go-live. Salesforce counts every integration's calls against one org-wide daily allocation, and HubSpot lets you cap its share.
- Ask for deliverables you can hand to someone else: a field-level mapping spec, a lifecycle and handoff design, and a sync-health runbook.
HubSpot Salesforce integration consultants are specialists who design how HubSpot and Salesforce share records, so that marketing, sales and customer success work from one version of each contact, company and deal. The good ones are judged on three things: how they design the data sync, how they model the lifecycle, and how they engineer the revenue handoff between marketing and sales. Installing the connector is the easy part.
This guide is for revenue operations and CRM leaders at growing and mid-market companies who run marketing in HubSpot and revenue in Salesforce, or are about to. It explains what the native connector actually does, where it leaves decisions to you, and how to tell a consultant who understands those decisions from one who will simply switch everything on.
Do You Need a HubSpot-Salesforce Integration Consultant at All?
You need one when the sync touches revenue reporting, more than one team, or more than the default objects. If you only need contacts to flow one way and nobody reports on sourced pipeline, a capable admin can follow HubSpot's setup guide. Once lifecycle stages, owners, deals and attribution depend on the sync, the design decisions outweigh the install.
Bring in a consultant if marketing and sales disagree on sourced pipeline, you sync deals or opportunities, you use Salesforce leads and contacts side by side, several HubSpot accounts connect to one Salesforce org, Salesforce flows and validation rules already guard your data, or the person who configured the current sync has left without documenting it.
You may not need one yet if you are syncing a small contact base into Salesforce for sales visibility only, you have no deal sync, no shared reporting on marketing-sourced revenue, and a Salesforce admin who will own the mappings. Document the decisions anyway: the shortcuts taken at this stage are what the next consultant gets paid to unwind.
What Do HubSpot Salesforce Integration Consultants Actually Do?
They turn a connector into an operating model. HubSpot builds and maintains the integration itself; a consultant decides how it should behave for your business, configures it, and documents why. In CRM integration consulting, that work falls into four areas, and a proposal that covers only the first is an installation quote, not consulting.
Data sync architecture
Which objects sync, which records qualify, which system owns each field, how duplicates are prevented, and how much of the Salesforce API budget the sync may use.
Lifecycle design
Shared definitions for lead, marketing-qualified, sales-qualified, opportunity and customer, and the exact system event that moves a record between them.
Revenue handoff
Owner mapping, lead assignment, the activity history sales sees at handoff, and the closed-loop data that flows back so marketing can report on revenue, not form fills.
Sync governance
Error monitoring, who fixes what, how new fields get mapped, and a written specification your own team (or another partner) can run without the original consultant.
Keep three things separate when you read a proposal: what the connector does natively, what the consultant will configure or build, and what business outcome you are buying. A consultant who blurs them is either overselling the connector or overselling their own work.
How Does the Native HubSpot-Salesforce Connector Work?
The native connector is HubSpot's own app, installed from the HubSpot Marketplace, that syncs contacts, companies, deals, tickets, activities and custom objects with their Salesforce equivalents. It needs a HubSpot Professional or Enterprise subscription and a Salesforce edition with API access. Any consultant you hire should know this baseline cold, including its limits.
| HubSpot object | Salesforce object | What a buyer should know |
|---|---|---|
| Contacts | Leads or contacts | Always on. Records match by email address, and you choose whether HubSpot creates Salesforce leads or contacts. |
| Companies | Accounts | Switched on separately. Under the standard sync, a company without associated contacts won't create an account. |
| Deals | Opportunities | Needs company sync first. The updated deal sync maps opportunity record types to HubSpot pipelines and can't be reverted. |
| Tickets | Cases | Two-way, with case business processes mapped to ticket pipelines. Existing cases don't import automatically. |
| Activities | Tasks | Timeline sync is one-way to Salesforce; the newer activity sync is two-way for tasks, sales emails, calls and meetings. |
| Custom objects | Custom and selected standard objects | Enterprise subscriptions only, and the HubSpot object must exist before the sync is configured. |
Sources: HubSpot Knowledge Base articles on connecting HubSpot and Salesforce, integration settings, deal sync, case sync, activity sync and custom object sync, checked October 2026. Tier requirements change; confirm against your own subscriptions.
Three setup facts trip teams up early. Records don't sync the moment the integration is installed; they come across by import or as sync triggers fire. Each HubSpot account connects to only one Salesforce org. And HubSpot describes the connector as built for ongoing two-way sync, not one-time migration: running its migration tool and the integration together creates duplicates, because the two use different unique identifiers. A consultant should raise all three before you sign off a plan.
Data Sync: How Should a Consultant Decide Which System Owns Each Field?
A good consultant assigns every mapped field an owner before anything syncs, then sets the matching sync rule. The connector offers four rules per field, and the rule decides whose edit survives. "Two-way on everything" is not a design; it is a decision to let the most recent edit win, in either system, for every field.
| Sync rule | How it behaves | Typical use |
|---|---|---|
| Prefer Salesforce unless blank | HubSpot writes to Salesforce only when the Salesforce field is empty; a Salesforce value always overwrites HubSpot. | Fields sales owns but marketing may capture first, such as phone or job title |
| Always use Salesforce | HubSpot never writes to Salesforce. | Sales-owned data such as rating, territory or qualification fields |
| Two-way | The most recent value wins, and deletions carry across in both directions. | Genuinely shared fields with clear editing rules |
| Don't sync | The field is not synced. | System-specific or sensitive data, and standard mappings you don't want |
Source: HubSpot, map HubSpot properties to Salesforce fields. The updated deal and company syncs add "Always use HubSpot" options; tickets and custom objects use their own rule set.
What to check in a consultant's data sync design
- A system-of-record map. One row per field: owner, sync rule, field types on both sides, and the reason. HubSpot only pairs compatible types (a dropdown to a picklist, a checkbox to a boolean), and it limits each object to 500 mappings.
- A plan for existing values. New mappings don't sync retroactively, and a record's first sync takes the current Salesforce value as the baseline, which can overwrite a newer HubSpot value. Ask how the consultant will backfill and resync without overwriting good data.
- An inclusion segment with a purpose. By default every HubSpot contact syncs to Salesforce. An inclusion segment limits that to records that meet agreed criteria, which keeps unqualified contacts out of the sales queue. Ask what the criteria are and who agreed them.
- A lead-or-contact decision, with its consequences. If HubSpot creates Salesforce leads, HubSpot advises turning off automatic company creation, because leads have no accounts and later conversion can create duplicate HubSpot companies.
- An API budget. Salesforce counts every API call to the org, from every integration and managed package, against one daily allocation. One contact sync can take up to four calls. HubSpot's sync health settings let you cap its share; ask what cap the consultant recommends and why.
The API point is where a specific answer shows real experience. Salesforce's own example: an Enterprise Edition org with 15 Salesforce licenses gets 115,000 API requests per 24 hours, shared by everything that calls the org (Salesforce API request limits). If the sync goes past HubSpot's cap, HubSpot suspends it until calls free up; if the whole org hits its limit, the integration can look connected while it fails to fetch data (HubSpot, suspension errors). Our Salesforce-HubSpot data sync page covers this part of our work.
Lifecycle Design: How Should Lifecycle Stages Work Across Both Systems?
Lifecycle design means agreeing what each stage means, which system sets it, and which event moves a record forward, before the sync is built. The connector's lifecycle behaviour is narrower than most teams assume, so a consultant should design around its rules rather than discover them after go-live.
The rules that matter, from HubSpot's integration settings documentation:
- Lifecycle stage changes driven by Salesforce opportunities move forward only, never back.
- A lifecycle stage change in HubSpot doesn't change Salesforce. Setting a contact to Customer in HubSpot won't convert the Salesforce lead.
- Automatic stage changes need the Salesforce contact linked to the opportunity through contact roles. Opportunities with no contact roles, or linked by a custom relationship field, don't trigger them.
- With HubSpot's lifecycle stage sync setting on, a change from the Salesforce integration applies to every contact associated with the same company (HubSpot, lifecycle stage sync between objects).
On the Salesforce side, lead conversion creates a contact, a new or existing account and, optionally, an opportunity, and it can't be reversed (Salesforce Help, convert leads). That makes conversion the natural point where marketing's lifecycle meets sales' pipeline. Here is an example of the kind of model a consultant should hand you; the stage names and triggers are a design choice, not a connector default.
| Stage | Agreed definition | Set by | Salesforce record |
|---|---|---|---|
| Lead | Known contact, not yet qualified | HubSpot | Not synced (outside the inclusion segment) |
| Marketing qualified | Meets the fit and engagement criteria both teams signed off | HubSpot | Enters the inclusion segment and syncs as a lead |
| Sales qualified | Accepted by sales after first contact | Salesforce lead status | Lead, worked by the assigned owner |
| Opportunity | Lead converted with an opportunity and a contact role | Salesforce conversion | Contact, account and opportunity |
| Customer | Opportunity closed won | Salesforce, synced forward to HubSpot | Closed-won opportunity on the account |
Whatever model you choose, ask the consultant two things. First, how a recycled lead (one sales rejected) is handled, given that Salesforce-driven stages can't move backwards. Second, how contact roles will be enforced on opportunities, because without them the Customer stage never reaches HubSpot and marketing's revenue reporting goes blank.
Revenue Handoff: What Should Happen When a Lead Moves From Marketing to Sales?
A clean handoff gets the right record to the right rep with enough context to act, and sends the outcome back to marketing. In practice that depends on three connector behaviours: owner matching, Salesforce assignment rules, and which activities sync. A consultant who designs the handoff should be able to explain all three in plain terms.
Capture, nurture, score and qualify
Forms, campaigns and engagement build the contact record. The record enters the inclusion segment only when it meets the agreed qualification criteria.
Assign, work, convert and close
Assignment rules route the new lead, the rep sees HubSpot activity on the record, and conversion creates the opportunity. Stage and closed-won outcomes flow back to HubSpot for reporting.
The handoff details to test
- Owner mapping. Owner sync is always two-way and needs an exact match: a HubSpot owner syncs only if they match an active Salesforce user's name and email. Records with no owner get the integration user, because Salesforce requires one (HubSpot, field mappings).
- Assignment rules. When HubSpot creates a new Salesforce lead without a matching owner, Salesforce lead assignment rules apply. When it syncs to an existing lead with an active owner, they don't. Your routing design has to account for both paths.
- Activity context. Timeline sync sends form submissions, email events, meetings, calls and notes to Salesforce as tasks. Repeat email opens and clicks create separate tasks, so a consultant should choose which events reps actually need (HubSpot, activity sync).
- Campaign attribution. Salesforce campaigns associated with a lead or contact sync to a HubSpot contact property, which is one input to closed-loop reporting. The rest comes from deals and lifecycle stages syncing back.
- Leavers. Salesforce won't accept tasks assigned to inactive users, so activity from departed owners fails to sync. Ask how ownership is reassigned when people leave.
This is where marketing and sales automation stops being two tool configurations and becomes one revenue process. If you are building the wider operating model around it, our revenue operations page covers how we connect CRM, automation and reporting across teams.
Where HubSpot-Salesforce Sync Usually Breaks
Most sync failures come from decisions nobody made rather than from the connector itself. Each of the five below is documented by HubSpot or Salesforce, and each is a fair question for a consultant: have you seen it, and how did you prevent it?
Salesforce's own duplicate management is part of this picture. Matching rules identify duplicates and duplicate rules decide whether to block or warn, and in orgs created from Summer '17 the standard lead and contact rules also match across the two objects (Salesforce Help, standard duplicate rules). A consultant should review those rules before the first sync, not after the first error report. Our Salesforce-HubSpot integration checklist is a useful companion before launch.
A Scorecard for Evaluating HubSpot Salesforce Integration Consultants
Score each consultant on evidence, not on the logo slide. The strongest signal is specificity: a consultant who has run HubSpot integration services and Salesforce integration services on live orgs will answer in field names, sync rules and API numbers. Use this table in your shortlist calls.
| Criterion | A strong answer includes | Red flag |
|---|---|---|
| Discovery | An audit of both orgs before scoping: current mappings, error queue, duplicate rules, automation that touches synced objects | A fixed quote before anyone has looked at either system |
| System of record | A field-level mapping spec with an owner, sync rule and reason per field | "We'll set everything to two-way" |
| Lifecycle | Written stage definitions, triggers per system, and a plan for recycled leads and contact roles | Lifecycle treated as a HubSpot-only setting |
| Handoff | Owner matching, assignment paths and which activities sync, tested with real records | No mention of owners until go-live |
| Data quality | Deduplication on both sides before the first sync, and a backfill plan for existing values | "The connector handles duplicates" |
| API and volume | Your org's daily allocation, current usage, and a recommended HubSpot cap | No view of what else calls your Salesforce org |
| Tooling | A reasoned choice between the native connector, an iPaaS and custom work, tied to your volume and logic | The same tool recommended for every client |
| Handover | Documentation and a sync-health runbook your team can run without them | Knowledge that lives only in the consultant's head |
Check credentials too, but weigh them correctly. Partner status with Salesforce and HubSpot shows a consultancy works on both platforms; it does not show they have designed a lifecycle model across them. Ask for an integration case study with the problem, the design decision and the result.
What Questions Should You Ask Before Hiring an Integration Consultant?
Ask questions that only someone who has run the integration on a live org can answer well. Each question below comes with what a good answer sounds like, so non-technical stakeholders can score the call too.
Native Connector, iPaaS or Custom: Which Approach Should a Consultant Recommend?
The right approach depends on how many systems are involved, how much the data must be transformed in transit, and who will maintain it. Most HubSpot-Salesforce integrations start with the native connector; a consultant should recommend something heavier only when your requirements go beyond what it is built to do, and should say which requirement drives the choice.
Native HubSpot-Salesforce connector
Default starting pointBest for: two-system sync of standard objects, with the configuration options HubSpot provides.
Built and maintained by HubSpot, configured through settings rather than code, and covering the object pairs in the table above. Its limits are the ones a consultant should name for you: per-field sync rules rather than transformation logic, owner matching by exact name and email, and custom objects only on Enterprise subscriptions.
Integration platform (iPaaS)
Multi-system flowsBest for: orchestrating HubSpot and Salesforce alongside billing, ERP or product data, or applying business logic between systems.
Platforms such as Workato, MuleSoft or Celigo sit between applications and run flows you define. They suit business systems integration where a deal must also create a billing account or an ERP order, at the cost of another platform to license, build on and monitor. An iPaaS can also run alongside the native connector rather than replace it.
Custom integration
Specific requirementsBest for: data models or rules that neither the connector nor an iPaaS handles cleanly.
Built directly on the HubSpot and Salesforce APIs. It gives full control and full responsibility: the same Salesforce API allocation applies, and someone must own the code after launch. Ask any consultant who recommends it which specific requirement rules out the alternatives.
Twopir Consulting implements the native connector and integration platforms including MuleSoft, Workato, Celigo, Zapier and n8n, so we can recommend the one that fits rather than the one we resell. Our Salesforce-HubSpot integration services page describes our integration delivery.
How Twopir Consulting Approaches HubSpot-Salesforce Integration
We implement, rescue, optimize, and integrate complex CRM and revenue systems. For HubSpot-Salesforce integration, that starts with evidence: we compare how the integration is actually configured with how the business believes it works, then write the fix as a specification. We help growing and mid-market companies solve complex CRM, integration, and business system challenges, and the same approach holds for enterprise teams.
- Advisory is priced separately from the build, so the recommendation isn't decided in advance. Sometimes the answer is configuration changes, not a rebuild.
- We reconcile records, not impressions. Divergence is measured against the actual data on both sides.
- We deliver a field-level mapping specification your admin can implement, along with a target architecture and a prioritised remediation plan.
- We assess tooling without a reseller incentive, across the native connector, HubSpot's data sync, an iPaaS or custom middleware.
- The documents are written for handover, so your internal team or another partner can run what we design.
On one B2B SaaS engagement described on our Salesforce-HubSpot integration consulting page, the audit found 35% of contacts out of sync, produced a mapping document specifying 47 fields, and surfaced three root causes the team didn't know about. That is the kind of finding a diagnostic should produce: a number you can act on, not a feeling that the data is off.
Get a Second Opinion on Your HubSpot-Salesforce Sync
On a 30-minute discovery call, a Twopir architect will walk through your current sync, lifecycle model and handoff, and tell you plainly whether you need configuration changes, a redesign, or nothing at all.
Schedule a Discovery CallThe Bottom Line
The HubSpot-Salesforce connector is capable, but it doesn't decide anything for you. Which system owns each field, which records reach sales, how a lead becomes a customer and who owns it at every step are business decisions, and the sync simply enforces them. Choose HubSpot Salesforce integration consultants who make those decisions explicit, prove them with your own data, and leave them in writing.
- 1
Judge consultants on three things: data sync design, lifecycle design and revenue handoff, not on how quickly they can install the connector.
- 2
Insist on a field-level system-of-record map with a sync rule and a reason for every mapped field.
- 3
Design lifecycle stages around the connector's real rules: forward-only updates from Salesforce, and opportunity contact roles.
- 4
Test the handoff with real records: owner matching, assignment paths and the activity history reps see.
- 5
Know your Salesforce API budget and set HubSpot's share of it before go-live.
Frequently Asked Questions
A HubSpot Salesforce integration consultant designs and configures how the two systems share data. That covers which objects and records sync, which system owns each field, how lifecycle stages and owners move between systems, how leads hand off from marketing to sales, and how sync errors and API usage are monitored after launch.
HubSpot documents that the integration needs a Professional or Enterprise subscription of a HubSpot hub or Smart CRM, and a Salesforce edition with API access or Salesforce Professional. Salesforce Group Edition isn't supported. Custom object sync needs a HubSpot Enterprise subscription. Check HubSpot's current documentation, because tier requirements change.
It depends on how your sales team qualifies. Syncing as leads keeps unqualified records out of accounts, but HubSpot advises turning off automatic company creation in that setup, because leads have no accounts and later conversion can create duplicate HubSpot companies. Syncing as contacts keeps account data aligned but needs firmer qualification before sync.
No. Salesforce opportunity changes can move a HubSpot contact's lifecycle stage forward, never backwards, and only when the contact is linked to the opportunity through contact roles. A lifecycle stage change in HubSpot doesn't change Salesforce, so setting a contact to Customer in HubSpot won't convert the Salesforce lead.
HubSpot says a single contact sync can use up to four API calls per record. Those calls count against your Salesforce org's shared daily allocation, which for Enterprise Edition is 100,000 plus 1,000 per Salesforce license. HubSpot's sync health settings let you cap how much of that allocation the integration may use.
Consider an integration platform such as Workato, MuleSoft or Celigo when HubSpot and Salesforce must exchange data with other systems, such as billing or ERP, or when data needs business logic applied in transit. For two-system sync of standard objects, the native connector is usually the right starting point.
At minimum: a field-level mapping specification with an owner and sync rule per field, written lifecycle stage definitions and triggers, an owner and handoff design, a deduplication and data-loading plan, an agreed API cap, and a sync-health runbook your own team can follow after the consultant leaves.
Twopir Consulting
Twopir Consulting has delivered Salesforce and HubSpot work for 12+ years. We work with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges, including HubSpot-Salesforce sync design, audits and rescues.
