Index
Deleting duplicate contacts can erase history or break relationships with opportunities. CRM cleanup needs to decide which record remains and how its information will be consolidated.
How to evaluate this decision
Define matching criteria and cases that require review. People with similar names are not necessarily the same person; Companies can have legitimate branches and relationships. Separate duplicate detection from actual merging. Before changing the basis, map activities, attachments, consents, and integrations that use the current identifiers.
Criteria for comparing proposals
- Diagnosis: classify probable duplicates, empty fields and records without responsible.
- Consolidation: establish precedence by field and maintain relevant links and information.
- Rollback: Maintain evidence of changes and a recovery path for incorrect merges.
A scenario to discuss with the supplier
Hypothetical example: two contacts share a general company email, but represent different people. A rule that binds only by email can mix relationships and business activities.
What to validate upon delivery
Apply cleaning first to a reviewed batch. Compare quantities, links and activities before and after. Check that integrations continue to find the records and that the correction is not undone by the next synchronization.
Prepare the conversation about the project
Bring Quantum9 an anonymized sample, input sources, and identification rules. The project must include prevention of new inconsistencies, in addition to cleaning the history.
CRM and retention · Map the company's priority