Sync errors piling up unnoticed
The integration throws errors in the background nobody's watching. By the time someone notices, weeks of records have failed to sync and nobody's sure which system is right.
I make HubSpot and Salesforce agree with each other: sync errors fixed, fields mapped correctly and one version of the truth your forecast can run on. For B2B teams moving to HubSpot, or running it alongside Salesforce.
Leakage Check: A personal 20-minute review of one process, with a one-page summary within 1 working day.
Rather see your numbers first? Run the free Lead Leak Audit
Lead Leak Audit: An automated, read-only assessment of your HubSpot portal, starting with the lead handoff; 90 seconds to connect, report in under 10 minutes.
HubSpot and Salesforce don't agree with each other by default. The gap between them is where sync errors, duplicate records, and reporting arguments live.
The integration throws errors in the background nobody's watching. By the time someone notices, weeks of records have failed to sync and nobody's sure which system is right.
The same contact exists three times in HubSpot and twice in Salesforce, each with a different mix of correct and stale data. Nobody trusts a search result anymore.
Marketing calls it an MQL. Sales calls it something else in Salesforce. The mapping between the two drifted months ago and nobody rebuilt it.
The board deck has a HubSpot number and a Salesforce number, and they don't match. Someone has to explain the gap instead of the pipeline.
Pick the process you trust least, such as form to owner, MQL to SQL or deal stages. We look at it together in HubSpot and I write up where leads leak and what to fix first. The only question I ask up front: are you a B2B company using HubSpot or choosing it?
Led the Pardot-to-HubSpot migration for a 400-person B2B SaaS company: around 300k contacts, 30k companies and 10k deals, with Salesforce kept live. “Wow, in all my 25 years in marketing I've never seen such a smoothly run migration and not only that it was delivered early too!” (CMO, B2B SaaS)
At a 65-person B2B tech company, usable contacts went from 17% to 89% in about three months, as part of a six-month rebuild. Pipeline from rebuilt email nurture reached about £3m in a single half-year: around £1.5m a quarter, about 4x the £300–400k quarterly average before.
Built SDR dashboards at a B2B tech firm.

HubSpot consultant
I'm a consultant, not an agency. I work with B2B teams of £2-15m ARR where HubSpot and Salesforce have to agree.
It's rarely the tools. It's the gaps between them: the data that doesn't move, the process that lives in someone's head, the forecast nobody trusts. That's where I work.
I live in the gap between the two CRMs: the field that maps wrong, the sync that silently drops records, the lifecycle stage that means something different on each side. I keep my client list small so each integration gets proper attention, not a template delivered and handed off to a junior. If something I've built breaks on a Tuesday, I'm the one who fixes it.
Yes. I led the Pardot-to-HubSpot migration for a 400-person B2B SaaS company: around 300k contacts, 30k companies and 10k deals, with Salesforce kept live. “Wow, in all my 25 years in marketing I've never seen such a smoothly run migration and not only that it was delivered early too!” (CMO, B2B SaaS) HubSpot Go-Live is from £14,000, starting with a data clean and a migration from one source system, and the price rises with records and workflows.
With the Free Lead Leakage Check: 20 minutes on one process and a one-page summary within 1 working day. If there's more to fix, we have a scoping call, and the next step is the Lead Handoff Sprint: £15,000, six weeks, paid 50/50.
Usually one of a handful of causes: a field mapping that changed on one side, a picklist value missing on the other, a permission or sharing rule blocking the sync user, or a record failing validation rules. The complete guide walks through the sync errors I see most often and what causes each one.
Yes. Most engagements involve your Salesforce admin and your HubSpot owner both. I scope the integration work with both of you, and I don't make changes on the Salesforce side without their sign-off.
Most of the time, yes. Inherited integrations are the norm, not the exception: an agency, a freelancer, or an admin who's since left. I check what's actually there first, so any fix builds on what's really happening rather than what the old documentation claims.
The native HubSpot-Salesforce connector covers most integrations well. Where it doesn't (complex object mapping, custom sync logic, or middleware needs), I bring in tools like Make, Zapier, or a custom API layer depending on what the gap actually requires.
Check three things: records with sync errors in the last 30 days, contacts whose lifecycle stage or owner differs between the two systems, and fields that both systems are allowed to overwrite. If any of those numbers is more than a handful, the integration is costing you leads or reporting accuracy.
Pick one and make the sync one-way for that field. If sales lives in Salesforce, let Salesforce own stages from SQL onwards and let HubSpot own everything before that. Two systems writing to the same field is a common reason funnel reports stop matching.