The playbook
CRM Data Cleanup: Template and Field Guide
This CRM data cleanup template turns a broad task into a record another person can use. It captures record ID, issue, trusted value, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| record ID | Record the record ID associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| issue | Record the issue associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| trusted value | Record the trusted value associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| action | Record the action associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with record ID. Use the same reference throughout the record so notes are not attached to the wrong item. Then find duplicate stale and inconsistent information. This establishes the information required before the worksheet becomes a request for action.
Next, define trusted values and safe merge rules. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as deleting records solely because one field is blank, rather than a broad instruction to “improve performance.”
Finally, review exceptions before changing important relationships. Put determine business relevance and preserve required history in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Deleting records solely because one field is blank |
| Action | Determine business relevance and preserve required history |
| First check | Find duplicate stale and inconsistent information |
| Follow-up check | Review exceptions before changing important relationships |
| Outcome to define | usable unique customer records |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If issue changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep usable unique customer records connected to the item so the team can later assess whether the action was useful.
Preserve the context of the last meaningful conversation. The next owner should know what was promised, what remains unresolved, and who is expected to act. A stage label alone rarely supplies enough information.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now