CRM data cleaning makes existing contact and company records easier to use without losing their history. Zoha helps define matching rules, normalize agreed fields and prepare checked imports. Enrichment is a separate, permission-based task: additional information needs an acceptable source and a record of where it came from.
Updated
On this page
Find the problems that interfere with everyday work
Start with a sample export and the decisions people struggle to make. A sales team may see the same company under several names, contacts assigned to former staff or inconsistent industry categories. Operations may need a reliable identifier shared with another system. These problems need different fixes.
An audit should distinguish structural issues from outdated information. An empty field, an invalid value and a value nobody has checked recently are different states. Keeping that distinction helps your team choose what to repair first.
Decide what makes two records the same
| Situation | Safe starting rule |
|---|---|
| Two contacts share an email address | Review names, company and history before a merge |
| A company has several branches | Keep branch relationships rather than flattening every address |
| A former employee owns open work | Reassign responsibility using an agreed business rule |
| Two sources disagree | Retain provenance and send the conflict for a decision |
A hypothetical customer list may contain both a head office and a branch with the same trading name. Merging by name alone would destroy a useful relationship. Matching rules should use the identifiers and account structure that your business actually relies on.
Normalize fields without changing their meaning
Useful cleanup can include consistent capitalization, controlled categories, country fields or telephone formatting. Agree the transformation with examples. A free-text sales note should not be compressed into a category if the original detail is still needed.
Keep a change file showing the source record identifier, the old value, the proposed value and the reason. This makes review possible before an import. It also lets your team distinguish deliberate standardization from an accidental edit.
Treat enrichment as sourced information
Enrichment can fill an agreed business field when the source and permitted use are clear. It should not become a search for private contact information or an assumption that a public-looking value is current. Record the source, check date and confidence or review state appropriate to the field.
Give the buyer a choice about conflicts. A new company address may be a branch, an old address may remain relevant to an invoice, and an employee role may have changed. Updating everything to the newest-looking value is not always the right decision.
Test the import and leave a maintainable record
- Export a recoverable starting copy and identify the records included in the cleanup.
- Apply agreed transformations to a working copy, with uncertain matches in a separate review file.
- Test a small import and check ownership, relationships and record history.
- Compare record counts and exceptions after import; retain the approved mapping and change log.
A one-time cleanup lasts longer when the source of new errors is addressed. Required fields, controlled lists and a simple duplicate-review process may reduce repeat work. The handover should explain those rules in language the people entering records can use.