Missing on one side
Contacts, companies and deals that exist in one system and not in the other, grouped by object.
For HubSpot agencies and RevOps teams
A read-only audit that compares both systems record by record, so your next sync fix starts from a list, not a guess.
We are building this now with a small group of design partner agencies and RevOps teams. Nothing here is for sale yet.
Contacts, companies and deals that exist in one system and not in the other, grouped by object.
Owner, lifecycle stage and deal stage differences, listed with the value on each side.
Pairs that look like the same person or company across the two systems, so you can merge before the next sync run.
A 20-minute walkthrough of what we are building, and a place in the design partner group if it fits. No charge, no card.
Design partner pricing will start at $149 a month per connected HubSpot and Salesforce pair. You pay nothing until you decide to continue.
Common causes are inclusion lists, field mapping rules, required Salesforce fields, record ownership and API limits. The hard part is knowing which records are affected; that list is what this audit gives you.
Export the same objects from both systems (contacts, companies, deals) with the Salesforce ID HubSpot stores, match on that ID, then compare owner, lifecycle stage and deal stage, and list records that exist on one side only. Syncscope is meant to do exactly that comparison for you, read only.
Usually a mapping rule set to prefer one side, picklist values that do not exist in the other system, or a workflow that overwrites the value after the sync. Listing the records where the two values differ shows which rule is at fault.
No. It reads only, or works from two exports. Fixes stay in your hands.
It will list likely duplicate pairs across the two systems with the matching fields, so you can merge on purpose.
No. We are working with design partners first. Request a demo and we will show you where it stands.