Leads leave HubSpot. Some never reach Salesforce.
HubSpot tells you a sync error happened. SyncWatch tells you which Salesforce rule blocked which records, in plain English, with the fix your admin needs.
The decoder runs in your browser. Your file is never uploaded.
HubSpot gives you a category. You need a cause.
Sync Health groups failures into buckets like “Custom code”. That tells an admin something broke, not what to change. SyncWatch reads the same errors and names the rule.
What Sync Health shows
Each bucket opens a list of records and the raw Salesforce message. Working out which rule caused it, and whether 300 errors share one cause, is left to you.
What SyncWatch tells you
Your Lead validation rule “Phone is required” is rejecting every web-form lead without a phone number.
- Open Object Manager → Lead → Validation Rules and find the rule with that message.
- Make phone required on the form, or exempt the HubSpot integration user in the rule.
- Click Resync in HubSpot. The 312 records go through.
Decode your sync-error export
Free. Drop in the CSV that HubSpot exports from Sync Health. Results appear below, ranked by how many records each cause blocks.
Drop your HubSpot error export here
One or more .csv files. HubSpot exports each error category separately, so add them all at once.
Where to find the export
- In HubSpot, open Connected apps → Salesforce.
- Go to Data sync → Sync Health.
- Click an error category with records in it.
- Click Export errors (CSV). Repeat for each category.
You need Super Admin or Salesforce integration access in HubSpot.
Root causes
Worst first. Each card is one fix.
From error export to fixed sync in three steps
Export from Sync Health
HubSpot already logs the errors. Export each category as a CSV, about a minute of clicking.
Drop it into the decoder
SyncWatch groups the errors by root cause and ranks them by how many records each one blocks.
Send the fix to your admin
Each cause comes with step-by-step Salesforce instructions you can copy straight into a ticket or Slack.
The export is a snapshot. Your sync breaks on a Tuesday.
We're building SyncWatch monitoring for teams that can't afford to find out at the end of the quarter.
-
A daily root-cause checkNew sync errors grouped by cause, with the fix, sent to your admin by email or Slack.
-
Records that silently never syncedLeads that met your sync rules but have no Salesforce ID hours later, and no error to explain it.
-
A warning before a change breaks the syncSomeone adds a validation rule or required field in Salesforce. You hear about it before the first lead bounces.
Questions
Is my export uploaded anywhere?
No. The decoder reads your CSV inside your browser tab. The site only records anonymous counts: that an analysis ran, how many rows it had and which kinds of errors it found. Never names, emails or record IDs.
Do I need to connect HubSpot or Salesforce?
Not for the decoder. You only need access to HubSpot's Sync Health page to export the errors. Ongoing monitoring will connect read-only to both, which is what lets it catch silent failures and risky Salesforce changes.
Which errors does it recognize?
The common Salesforce rejections behind HubSpot sync errors: validation rules, required fields, triggers and flows, duplicate rules, permissions, restricted picklists, field lengths, record locks and API limits. Anything it doesn't recognize is still grouped and shown with the raw message.
Will this still work when HubSpot moves to its new Salesforce sync?
HubSpot is rolling out a rebuilt Salesforce integration object by object. Salesforce validation rules, picklists and permissions still reject records on the new sync, so those causes and fixes stay the same. We'll update the decoder as the export format changes.
Who's behind SyncWatch?
A Salesforce and RevOps consultant who has spent ten years cleaning up HubSpot–Salesforce syncs. Questions or a sync story to share: hello@getsyncwatch.com.