Start a CRM data cleanup with a small, reversible batch. Decide which records need attention, agree how to resolve conflicts, and test the result before changing your full database. The goal is a usable sales record with its history intact.
Find the problem that affects daily work
Ask sales and operations for specific examples: two people contacting the same lead, deals with no owner, reports with several names for one stage, or closed customers still receiving prospect messages. Use those examples to choose the first batch.
Do not merge everything that looks similar. Two contacts may share a company address, and one person may have several valid email addresses. Keep uncertain matches in a review list.
Save the records and their relationships
Before editing, record the selected IDs and export the fields you need to compare. Check whether your export also contains notes, activities, attachments, company links and deal relationships. An export of contact fields alone may not be enough to restore a merged record.
Confirm the CRM’s backup, merge and recovery options in its current documentation. If a change cannot be undone reliably, narrow the batch and require a manual check before applying it.
Agree which values to keep
Write rules for each field that often conflicts. For example, an account owner should come from the agreed territory or account rule. A recently imported blank value should not erase a verified phone number. Marketing preferences need their original evidence and should never be guessed from activity.
Choose standard names for pipeline stages, lead sources and countries. Keep a record of old and new values so reports remain explainable. If the pipeline itself is unclear, review your sales pipeline stages before normalizing thousands of records to the wrong definitions.
Test duplicates before merging them
Select examples that include conflicting owners, open deals and linked companies. Review each candidate pair, choose the surviving record, and check what happens to activities and relationships after the merge. Record both original IDs and the surviving ID.
Shared phone numbers and similar company names are clues for review, not proof of duplication. Leave disputed records separate until someone who knows the account resolves them.
Check workflows and reports after the batch
- Open a sample of changed records and confirm the right owner, stage and company.
- Check that active deals, notes and scheduled tasks remain accessible.
- Look for unexpected assignment changes or messages triggered by field updates.
- Compare record counts and pipeline totals with the saved baseline. Explain differences rather than expecting every total to stay identical after merging.
- Confirm that integrations will not recreate the duplicates on the next sync.
Prevent the same mess returning
Fix the entry point that caused the problem: an import mapping, an overly broad sync, a free-text stage field or a form that creates another contact every time. Add a regular review of suspected duplicates and unassigned leads, with a named person to resolve each queue.
If a cleanup becomes a move to another system, use the CRM migration checklist to plan imports, cutover and rollback. A tidy spreadsheet is useful only if the live CRM still supports the team’s work.