A successful HubSpot-Salesforce integration is decided long before anyone maps a single field. The discovery, data-governance, and planning work you do up front determines whether the integration becomes a durable revenue asset or expensive technical debt.
This guide covers the strategic phase of a HubSpot-Salesforce integration: the discovery questions to ask, how to choose a source of truth for each object, the architecture decisions that shape everything else, how to handle GDPR consent and privacy in a two-CRM sync, and how to scope and sequence a phased rollout.
It is written for revenue operations leaders, CRM admins, and marketing and sales operations teams who are planning a two-system setup and want to avoid the rework that comes from skipping discovery.
HubSpot-Salesforce integration planning is the discovery and governance phase that defines what data flows between the two CRMs, in which direction, and under what rules — before any configuration begins. It matters for any organization running both platforms, because integration decisions touch lead routing, reporting accuracy, data privacy, and Salesforce API consumption. This article helps you run a structured discovery, choose a source of truth per object, plan GDPR-compliant consent and deletion handling, and scope a phased rollout. Vantage Point is relevant because we are a senior-led, US-based, employee-owned firm and HubSpot Gold Partner that runs integration discovery workshops and plans two-CRM architectures for mid-market teams.
HubSpot-Salesforce integration planning is the structured discovery and design work that defines how two CRMs will share data before any sync is turned on. It answers three questions for every record type: what data exists, what job each data point does, and which direction it should flow.
Planning is not configuration. It is the decision-making layer that configuration depends on. Skip it, and you inherit duplicate records, conflicting fields, broken reporting, and avoidable Salesforce API strain — problems that are far cheaper to prevent than to unwind after go-live.
Running HubSpot and Salesforce together is now common: marketing operates in HubSpot, sales and service operate in Salesforce, and leadership wants one trustworthy view of the customer. The native HubSpot integration can deliver that, but only when the rules are set deliberately.
Three pressures make up-front discovery more important than ever:
A short, disciplined discovery phase protects all three.
Use a simple, repeatable discovery structure. We organize it around three questions — challenges and goals, timeline and impact, and budget and authority — so the plan ties directly to business outcomes rather than feature checklists.
Start with the problem in the team's own words. A typical answer: "Marketing and sales are misaligned, and we want the integration to improve handoffs and communication." Capture the current pain, the desired end state, and any plans already in motion.
Establish urgency and the cost of inaction. When does this need to be live, what breaks if it slips, and what broader processes (lead routing, renewals, reporting) does it touch?
Confirm who funds the work and who makes the final call. A common answer: "We plan to invest next quarter, and the Salesforce admin will make the technical decisions." Knowing the decision-maker prevents stalled approvals later.
During the discovery call, your job is to explain how the integration works, walk through the field-mapping process, and highlight the role of the integration user. It is not to start implementing. Discovery is for understanding and planning, not building.
The single most important planning decision is the source of truth: which system is authoritative for each object and field. Decide this object by object — there is rarely one global answer.
| Object | Common source of truth | Why |
|---|---|---|
| Contacts / Leads | Often HubSpot for marketing data; Salesforce for sales-owned fields | Marketing captures and enriches early; sales owns qualified-stage data |
| Companies / Accounts | Often Salesforce | Account hierarchy and ownership usually live in the system of record for sales |
| Deals / Opportunities | Salesforce | Pipeline, forecasting, and close data are sales-owned |
| Marketing activity & engagement | HubSpot | Email, form, and campaign data originate in HubSpot |
| Lifecycle / stage data | Define explicitly per field | Both systems track stages differently; pick one owner to avoid conflicts |
A practical default for conflicting fields is "prefer Salesforce unless blank," which protects heavily customized Salesforce data while still letting HubSpot fill gaps. Choose the rule per field based on which team actually owns that data.
Before configuration, document the plan in a mapping spreadsheet. For each data point, capture:
The spreadsheet is a field-level plan, not an ownership chart. Deciding who maintains the integration is a separate governance (RACI) conversation, handled alongside discovery rather than inside the mapping sheet.
A few constraints shape the whole design and should be settled during planning:
For the build mechanics that follow this planning phase, see our companion guide on installation and order of operations.
GDPR — the General Data Protection Regulation — applies to any organization marketing to or processing data about EU residents, regardless of where the company is located. In a two-CRM environment, compliance is harder because personal data lives in both systems, and obligations must be honored in both.
Plan these privacy flows during discovery, not after:
Treat consent and deletion as first-class mapping items in the planning spreadsheet. For a deeper compliance walkthrough, see our GDPR compliance and CRM implementation guide, and align the design with your broader compliance and security requirements.
Do not try to sync everything on day one. Phase the rollout so each stage is verifiable:
The strategic payoff is concentrated in the HubSpot capabilities that get stronger with more connected data: reporting, segmentation, and workflows. Phasing protects those outcomes by proving each stage before the next.
Vantage Point is a senior-only, US-based, employee-owned consultancy and HubSpot Gold Partner that specializes in mid-market CRM. Because we work across both platforms, we plan integrations from the perspective of how HubSpot and Salesforce actually behave together — not one side in isolation.
Our HubSpot-Salesforce integration discovery workshop produces a source-of-truth map, a field-level sync plan, a GDPR consent-and-deletion design, and a phased rollout you can execute with confidence. We pair that with advisory and change management and system integration and data migration support so the plan survives contact with real data and real users.
If your team is planning a two-CRM setup, a short discovery workshop is the fastest way to de-risk the build. Reach out to scope an integration strategy session with Vantage Point.
Use a structured framework that captures challenges and goals, timeline and consequences, and budget and authority. This ties the integration to business outcomes and identifies the decision-maker early, so the plan reflects real priorities rather than a generic feature list.
Do not start implementing. The discovery call is for explaining how the integration works, walking through the mapping process, and clarifying the integration user role — not for configuring the sync. Building before the plan is documented is the most common cause of integration rework.
For each data point it should capture what HubSpot property or Salesforce field exists, what job that data point performs, and which direction it will sync. Deciding who maintains the integration is a separate governance conversation, not part of the field-mapping sheet.
Yes. GDPR applies to any organization that markets to or processes personal data about EU residents, regardless of where the company is located. A US-based business with EU contacts in its CRM must honor consent, access, and deletion obligations.
Plan deletion so a right-to-be-forgotten request propagates to both HubSpot and Salesforce. Map how a delete in one system is reflected in the other, so personal data does not silently reappear through the sync. Decide this during discovery, not after go-live.
Decide object by object based on which team owns the data. Sales-owned objects like Opportunities usually master in Salesforce, while marketing engagement data masters in HubSpot. For conflicting fields, a common rule is "prefer Salesforce unless blank," which protects customized Salesforce data while letting HubSpot fill gaps.
Reporting, segmentation, and workflows gain the most, because they become more powerful as more connected, accurate data flows in. This is the strategic reason to plan the integration carefully and phase the rollout so those capabilities are built on trustworthy data.
Phasing lets you clean data first, validate core objects, and add scope gradually so you can verify each stage. It also prevents large data bursts from straining shared Salesforce API limits, which are consumed by every connected application, not just HubSpot.