Data and reporting
Review duplicates and reverse record merges
Identity Resolution helps reconcile account and contact records across supported imports, syncs and manual edits. Matching evidence suggests where to look; workspace policy determines who can merge or reverse the records.
Reviewed November 2026
Find and inspect possible duplicates
- Open Accounts or Contacts → Duplicates → Review queue. You can also use Data Sources → Identity & duplicates, or CDP → Duplicates.
- Choose Accounts or Contacts, then All open or High confidence. In an import or sync context, use the run filter to narrow the queue.
- Compare the records, matched keys, confidence, component scores and sources. Use View to inspect the original records.
- Choose Not a duplicate for an incorrect pair, or Merge to inspect the merge preview.
Choose the golden record and review fields
- Select the golden record: the surviving record whose ID will be kept.
- Choose Review fields. Inspect each differing value and Why it wins.
- Select a different value when appropriate. A Pinned manual edit takes precedence; use the offered Unpin control only if you intend to replace it.
- Expand matching fields if needed and inspect the relationships that will move to the golden record.
- Confirm Merge, then review the outcome and the resulting record.
Inspect the merge ledger
Open Merge history to inspect the status, trigger, timestamp, surviving and merged records, source and link count. The underlying ledger preserves pre-merge snapshots and field changes for reversal.
Merged records are parked rather than simply deleted. Source priority, recency and pinned manual edits influence surviving values. Resolver settings may allow some automatic merges or exact matches, so review the trigger and source of the merge.
Reverse an eligible merge
- In Merge history, find the applied account or contact merge. Review the survivor, merged IDs, timestamp, source and link count.
- Choose Revert, read Revert this merge?, then confirm Revert merge.
- Read the result and inspect the restored records and links. Later changes recorded as user edits in field provenance are preserved on the surviving record.
- Inspect the restored records and their relationships. A link that moved again after the merge is not forcibly moved back; the history view does not list every skipped relationship.
- If a newer merge affects the same survivor, reverse that newer merge first, then retry the older one.
Understand import coverage and policy
Import and sync results can distinguish new, linked or adopted, auto-merged and review-needed records. This is not coverage for every object or integration.
Scored automatic merging is off by default, but a shared external CRM ID can cause an automatic merge and exact natural-key matching can adopt existing records. Inspect the workspace’s resolver mode and the import strategy.
Workspace role policy controls records.merge and records.revert_merge. Resolver configuration, rescans and backfill are administrator-only controls.
| Source | Supported scope |
|---|---|
| CSV files | Account and contact imports; skip or update strategies affect matching behavior. |
| Salesforce and HubSpot | Account and contact CRM imports through the shared importer. Provider permissions still apply. |
| Inbound CDP | Supported account and contact syncs, with review filtered by sync run. |
| Manual work | Account and contact creation and updates maintain matching keys and flag candidates. |