HubSpot has become the platform of choice for mid-market and growth-stage companies standardizing marketing, sales, and service on a single CRM. But most teams use a fraction of it, as a marketing tool with sales bolted on, and miss the RevOps value of running the full customer lifecycle on one connected system. The platform is rarely the limit. The architecture, the automation, and the operating discipline behind it are.
We implement and optimize the full HubSpot suite, Marketing Hub, Sales Hub, and Service Hub, with the advanced workflow and automation that makes it run, and we build the HubSpot and Salesforce integration cleanly when both platforms run side by side. The deeper work is RevOps: designing the lifecycle, the data, and the reporting so HubSpot becomes the operating system for revenue, not just a campaign tool.
The usual failures: a marketing-first setup that never grows into sales and service, so the customer lifecycle stays fragmented; automation layered on without governance until no one can untangle it; and a HubSpot and Salesforce sync that quietly conflicts, so the two systems disagree about the truth. We architect the lifecycle and the integration so the whole revenue motion runs on one consistent system.
We run both the Salesforce and the HubSpot practices, so when both platforms are in play we integrate them honestly instead of forcing one. As a Salesforce consulting, implementation and integration partner with deep RevOps experience, we build HubSpot for the full lifecycle, which is where its real value has always been.
The engagements we run most often on HubSpot, from first implementation through optimization.
Marketing automation, lifecycle nurture, lead scoring, attribution, and campaign reporting at scale.
Pipeline architecture, forecasting, sequences, deal stages, and quoting workflows.
Ticketing, knowledge, conversations, customer feedback, and service playbooks.
Production integration when HubSpot and Salesforce run side by side, including bi-directional sync, conflict resolution, and reporting.
HubSpot CMS implementations and migrations, for marketing-led websites that integrate tightly with the CRM.
Operations Hub setup for data sync, custom code workflows, and data quality management.
Engagements are measured by movement on the numbers that matter. These are the directions of travel we commit to.
Predictable phases. Clear deliverables. No surprises.
One to two working sessions to map your current state, business goals, and gaps. We come out with a written scope and recommendation.
Documented architecture, realistic timeline, and transparent commercial proposal. No surprises and no hidden scope.
Configuration, development, integrations, data migration, and QA, with weekly demos and on-the-fly adjustments.
Training, change management, hypercare, and ongoing optimization. We do not disappear at go-live.
Consultant-level analysis from the consultants delivering the work.
When it makes sense to keep HubSpot for marketing and Salesforce for sales, how HubSpot's Salesforce connector decides what syncs, field ownership and sync rules, API usage, lifecycle stages and when to consolidate instead.
Read the full post →HubSpot’s native connector installs a managed package in Salesforce and links one Salesforce org to one HubSpot account. It syncs contacts, leads, companies, deals, tasks and supported custom objects in both directions. Setup needs a Salesforce admin with API access and permission to modify metadata. Plan the install with whoever owns your org’s change process, not marketing alone.
Every mapped property carries a rule that decides which system wins: prefer Salesforce unless blank, always use Salesforce, two-way, or don’t sync. These rules are how you settle conflicts when both teams edit the same field. Choosing them deliberately per field, instead of accepting defaults, prevents marketing updates from quietly overwriting values sales reps entered a minute earlier.
An inclusion segment, which HubSpot previously called an inclusion list, limits which HubSpot contacts are pushed into Salesforce. Without one, every contact syncs, including students, competitors and newsletter subscribers who will never buy. Most teams let only marketing-qualified or sales-ready contacts through, which keeps Salesforce focused on people reps should actually work and protects your Salesforce storage and API limits.
HubSpot can move a contact’s lifecycle stage forward based on Salesforce events, such as an opportunity being created or closed through a contact role. Stages only advance and never step backward automatically. This matters for funnel reporting, because marketing attribution in HubSpot is only as accurate as the Salesforce opportunity data and contact roles your reps actually maintain.
Form submissions, marketing email interactions and meetings logged in HubSpot can be written to Salesforce as tasks, and HubSpot contacts can be added to Salesforce campaigns. Reps then see marketing context on the lead or contact record without switching tools. Be selective, though, because syncing every email open creates task clutter that buries the activity reps genuinely need to see.
HubSpot Embed places a HubSpot panel on Salesforce lead, contact, account and opportunity pages, showing recent marketing activity. Where licensed, reps can enroll records in sequences or workflows from there. It suits organizations keeping reps in Salesforce while marketing runs in HubSpot. Confirm which actions your HubSpot seats allow, since embedded features depend on the subscriptions assigned to each rep.
Before connecting anything, write down which platform is the source of truth for leads, contacts, accounts, lifecycle stage, lead status and owner. Agree how a HubSpot contact becomes a Salesforce lead or contact, and who can change stages. This short document settles most future arguments and becomes the specification for every field mapping and sync rule you configure.
Deduplicate Salesforce leads and contacts, and deduplicate HubSpot contacts and companies, before the first sync links them. Standardize email formats, company domains and picklist values that will map across. Matching relies heavily on email address, so records missing one or sharing one cause trouble. Cleaning first avoids multiplying existing duplicates across two systems at once.
Connect a HubSpot test account to a Salesforce sandbox where possible, install the package and set sync rules field by field. Build the inclusion segment, decide whether HubSpot contacts arrive as Salesforce leads or contacts, and set a sensible API call cap. We test edge cases like converted leads, owner changes and records failing validation rules before production.
In production, start with a narrow inclusion segment and a limited set of mapped fields, then watch the sync errors list closely. Validation rules, required fields and record-type assignments in Salesforce are frequent blockers. Fix those causes, widen the segment in stages and confirm owner assignment behaves correctly before letting the full marketing database flow across.
Assign someone to review sync errors and API usage weekly, and alert on spikes. Build matching funnel reports in both tools so leaders see consistent numbers, and reconcile any gap. Revisit the setup each year: if most work now happens in one system, that is the signal to plan consolidation rather than keep adding sync complexity.
The connector requires a Professional or Enterprise tier of a HubSpot hub, such as Marketing, Sales, Service, Content or Data Hub. Salesforce must be an edition with API access, or Professional Edition, per HubSpot’s current documentation. Beyond the connector itself, the real cost questions are marketing contact tiers, seats and API capacity. HubSpot bills marketing contacts separately from non-marketing contacts, so records synced from Salesforce can affect your tier if flagged for marketing. Confirm with HubSpot which features, such as custom object sync or embedded sequences, require Enterprise or specific seats. On the Salesforce side, check daily API allocations, because heavy syncing consumes calls shared with every other integration.
Skipping the inclusion segment pushes every newsletter subscriber and form spammer into Salesforce as a lead. Reps drown in unqualified records, lead assignment rules fire on junk, and storage fills. Define the segment around qualification criteria from day one, and treat any change to it as a controlled decision rather than a quick marketing tweak.
Two-way rules on everything let the most recent edit win, whichever system made it. A marketing workflow can then overwrite a rep’s qualified status or a corrected job title within minutes. Reserve two-way sync for the few fields both teams genuinely maintain, and make Salesforce authoritative for ownership, status and anything feeding the sales forecast.
When HubSpot workflows set lifecycle stage by score and Salesforce processes set lead status independently, the two funnels drift apart and nobody trusts either. Pick one system to drive stage changes, map the other as read-only and document what each stage means, including who can move a record and when.
Bulk imports or workflow updates in HubSpot can trigger thousands of syncs at once, consuming Salesforce API calls other integrations depend on. Meanwhile, validation failures sit silently in the error list. Cap the connector’s API usage, schedule large updates off-hours and review errors weekly, because unresolved failures mean the two systems no longer agree.
You choose. The connector can create new HubSpot contacts as Salesforce leads, which suits teams that qualify and convert through a lead process, or it can create them as contacts. When a matching Salesforce record already exists, the sync updates it instead of creating another. Decide this based on how your sales team works today, and remember converted leads need testing, since conversion changes which Salesforce record HubSpot tracks.
Usually HubSpot owns early-funnel stages like subscriber, lead and marketing qualified, while Salesforce drives later stages through lead status and opportunities. HubSpot can advance stages based on Salesforce opportunity activity, which connects the two. What matters most is that each stage has one system and one team allowed to change it. Both tools should report the funnel using identical definitions.
Keep both when marketing gets real value from HubSpot’s ease of use and someone owns the integration. Consolidate when the sync causes constant errors, licensing overlaps heavily or reporting keeps disagreeing. Salesforce-native options such as Account Engagement or Marketing Cloud remove the connector entirely but bring their own learning curve. Compare the ongoing cost of maintaining the sync against the one-time cost and disruption of retraining marketing.
Yes, and it is a common pattern. Salesforce becomes the CRM of record while HubSpot continues handling marketing, and the connector keeps the two aligned. Load historical deals, tickets and activities through a separate data migration, since the connector is not designed for bulk history. Freeze CRM editing in HubSpot at cutover so reps do not update records that no longer drive the business.
Clean both databases before connecting, because the first sync links whatever it finds. Matching leans on email address, so enforce valid emails on Salesforce leads and contacts. Turn on duplicate rules in Salesforce, avoid creating companies automatically when syncing contacts as leads, and review new records after large imports. Duplicates caught weekly take minutes to merge, while duplicates left for a quarter require a project.
OpenAI GPT models and the Responses API for production applications and embedded AI features.
Gemini models on Google Vertex AI for enterprise AI deployments and Google Workspace integration.
Copilot Studio, Microsoft 365 Copilot, and Azure OpenAI for Microsoft-first organizations.
Enterprise API platform, for connecting Salesforce, ERP, data warehouses, and the rest of your stack.
Modern iPaaS for SaaS-heavy stacks, automations, recipes, and AI-augmented workflows.
Cloud data platform, for unified analytics, AI grounding, and data sharing across the enterprise.
Tech Talk
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.
