The playbook
CRM Data Cleanup: Checklist
Use this CRM data cleanup checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect usable unique customer records. Check an actual customer or opportunity record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Separate exact duplicates from people who share a company or household. Review ownership, open opportunities, and communication history before merging. Preserve a recoverable record of the changes so a mistaken merge can be investigated.
Before you use the checklist
Name the exact item being checked and its purpose. Gather record ID, issue, trusted value, action. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Find duplicate stale and inconsistent information | A dated observation showing how record ID was verified | sales operations lead |
| Define trusted values and safe merge rules | A dated observation showing how issue was verified | record owner |
| Review exceptions before changing important relationships | A dated observation showing how trusted value was verified | sales manager |
Check the failure path
- Look specifically for this failure: deleting records solely because one field is blank.
- Determine business relevance and preserve required history. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check action.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Find duplicate stale and inconsistent information,” a meeting about the subject is not the evidence itself. Retain the relevant record ID and issue, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents improve the accuracy and usability of customer records deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow usable unique customer records using a consistent definition so later reviews can connect execution quality with useful results.
Review a small sample of underlying records before trusting a summary. Duplicates, stale close dates, and missing outcomes can make a dashboard misleading even when the calculation is correct. Correct the record-level cause.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now