← All postsHow-to

CRM data hygiene: measuring it before trying to fix it

CRM data hygiene fails as a clean-up project and works as a measured routine. The numbers worth tracking, the fields worth enforcing, and why enrichment often makes things worse.

How-toC

Every CRM eventually gets a clean-up project: somebody spends two weeks merging duplicates, everybody agrees it is much better, and within a year it is exactly as bad. CRM data hygiene only works as a routine with numbers attached, because the thing being fought is not mess but decay — contacts change jobs, companies rename, and the data was correct when it was entered.

The four numbers worth tracking

  • Duplicate rate: records sharing an identity key, usually email or domain plus name. Measure it monthly; a rising line means the entry path is broken, not the data.
  • Completeness on the fields that drive decisions — owner, stage, next action — rather than on every field.
  • Decay: the share of contacts with no meaningful interaction in twelve months. This is the number that tells you how much of your database is fiction.
  • Bounce rate on any send, which is decay made visible and the only one you get for free.

Fix the entry path, not the records

Cleaning without changing how data arrives is sweeping the floor during a sandstorm. Decide the identity rule — one field, enforced — and apply it at creation so a duplicate cannot be made rather than being merged later. Make the small number of decision-driving fields required and leave everything else optional, because a form with twenty required fields produces twenty fields of invented data. And give every record an owner at creation; ownerless records are the ones that rot first, since nobody is embarrassed by them.

Enrichment services look like a shortcut and often raise your duplicate rate: they add records that do not match your identity rule and fill fields nobody agreed on. Run one against a sample and measure the effect before letting it near the whole database.

A CRM data hygiene routine that survives a busy quarter

  1. Publish the four numbers monthly to the people who use the CRM, not only to whoever owns it.
  2. Merge duplicates rather than deleting, so history and attribution survive.
  3. Mark decayed records dormant instead of removing them — they stop skewing reports and remain searchable.
  4. Re-verify key contacts annually at renewal or review, when you are talking to them anyway.
  5. Delete only what you have no basis to keep, and record consent and source at capture so that decision is possible later.

Why it matters beyond tidiness

A database people distrust gets replaced by private spreadsheets, and at that point the CRM holds the subset of reality each person was willing to share. The forecast built on it is then an opinion with decimal places. Hygiene is less about neatness than about whether the numbers coming out can be used to decide anything.

Ettex Crm keeps the entry path narrow: an identity rule enforced at creation, a small set of required fields, an owner on every record and a dormant state rather than deletion. The underlying list discipline is the same one described in contact management, applied where a process rather than a person is being tracked.

Frequently asked

How often should duplicates be checked?

Monthly as a measurement, continuously as a prevention. If the monthly number keeps rising, the problem is the entry path rather than the backlog.

Is data enrichment worth it?

Sometimes, but test it on a sample first. Enrichment that ignores your identity rule reliably increases duplicates and fills fields nobody asked for.

Should stale contacts be deleted?

Mark them dormant instead. Deletion loses history and attribution; dormancy removes them from reports and sends while keeping the record findable.

MI
Written by Maria I.

Part of the Ettex team — writing about product, engineering and the future of work.

More posts
Get the best of the Ettex blogProduct news, guides and tips — straight to your inbox, no spam.