What happens when contacts are duplicated across systems?
Understand the impact, fix duplicates safely, and prevent them with clear rules—without losing activity history or compliance signals.
Why it matters
- Prevent misrouted leads and stalled workflows
- Stop double-sends and reduce unsubscribe risk
- Restore accurate attribution and funnel metrics
- Preserve activity history during safe merges
- Enforce ongoing data quality with guardrails
Key facts
| Item | Definition | Why it matters |
|---|---|---|
| Duplicate | Same person stored as multiple records | Creates routing and reporting errors |
| Golden record | Single trusted version | Keeps fields and history consistent |
| Source of truth | System that wins in conflicts | Prevents random overwrites |
| Match key | Fields used to identify duplicates | Improves merge accuracy |
| Merge policy | Rules for auto vs. manual merges | Protects compliance and data |
How to fix and prevent
Remediate safely
Define match keys, run a dry-run match, protect compliance fields, and merge in batches with rollback. Set precedence rules (e.g., CRM wins firmographics; MAP wins subscription state) and quarantine suspected dupes.
Prevent recurrences
Standardize forms, normalize inputs, restrict free-form record creation, and schedule similarity checks with alerts. Document merge policies and train admins and sellers.
Why TPG
We co-manage HubSpot and Salesforce data quality programs with governed merge policies, dashboards, and rollback playbooks—so you fix today’s duplicates and prevent tomorrow’s.
Frequently Asked Questions
Use unique IDs and email; add composite keys like email+domain or name+company when email is shared or missing.
Governed merges retain activity on the surviving record; test on a sandbox and keep rollback steps documented.
Honor the stricter consent; set precedence so any opt-out wins across systems.
Yes—enforce creation rules, normalize inputs, and run scheduled similarity checks with alerts for human review.
Define golden record rules, set a system of record, run a dry-run match, then remediate by priority (active pipeline, compliance-sensitive lists).