Key takeaways
- Dirty CRM data rarely fails loudly. It quietly breaks lead routing, scoring, territory reports and any AI agent that reads your records.
- Audit in a fixed order: duplicates, required fields, formats, ownership, then decay. Fix the issues that touch routing and reporting first.
- A one-off cleanup lasts a quarter. Validation rules, enrichment on entry and a weekly hygiene report are what keep it clean.
Your forecast looks off. Two reps are chasing the same account. Marketing says 400 leads went to sales, but sales only sees 250. Nobody has a clean answer, because the CRM has been collecting small mistakes for three years.
That’s what poor data hygiene looks like in practice. This checklist walks through what to audit, in what order, and how to stop the mess coming back.
Why data hygiene is a revenue problem
Bad data doesn’t announce itself. It shows up as a lead routed to the wrong rep, a segment that’s smaller than it should be, or an email sequence that goes to someone who left the company.
It also matters more now. Anything you automate, from scoring to an AI agent drafting follow-ups, reads your records and acts on them. If the CRM is wrong, automation makes it wrong faster. Salesforce’s 2026 State of Sales report found 51% of leaders say disconnected systems slow their AI efforts.
The audit order that saves time
Don’t start with formatting. Start with whatever breaks revenue processes first.
Count duplicate accounts, contacts and leads, matching on domain first, then name and email.
Find records missing owner, country, industry, lifecycle stage or source.
Fix company names, phone formats, countries, job titles and picklist values.
Reassign records owned by people who've left or by inactive queues.
Flag contacts with no activity, bounced emails or changed jobs.
Duplicates come first because they distort everything after them. If one account exists three times, your field-completeness numbers and ownership checks are all wrong.
Fields that deserve the most attention
You don’t need 100 perfect fields. You need perhaps 15 that routing, scoring and reporting depend on. Here’s a starting point:
| Field | What breaks if it’s wrong | What good looks like |
|---|---|---|
| Account domain | Matching, enrichment, dedupe | One clean root domain, lowercase |
| Owner | Routing, follow-up, accountability | An active user on every open record |
| Country / region | Territory rules, compliance | Standard values, not free text |
| Industry | Segmentation, reporting | One picklist, mapped consistently |
| Lead source | Attribution, spend decisions | A controlled list, never blank |
| Lifecycle stage | Handoffs between marketing and sales | Defined entry and exit rules |
Pick your own list with RevOps and sales leadership. If nobody uses a field in a report or a rule, don’t spend time cleaning it.
How clean is your CRM, really?
Book a free 30-minute consultation. We'll review your data model and your biggest routing or reporting headaches, and show you how a cleanup would work for your team.
The full CRM hygiene checklist
Print this, or paste it into your RevOps backlog.
CRM data hygiene checklist
- Duplicate accounts, contacts and leads counted, with a merge plan
- Survivorship rules agreed: which record wins, which fields carry over
- Required fields enforced at the point of entry
- Picklists consolidated, with free-text fields removed where possible
- Phone, country and domain formats standardised
- Every open record has an active owner
- Parent-child account hierarchies mapped
- Bounced and invalid emails suppressed
- Stale contacts flagged or archived on a set rule
- Import rules in place so spreadsheets don't reintroduce duplicates
- A weekly data quality report goes to RevOps
How to merge safely
Merging is where cleanups go wrong. A bad merge can delete the field that mattered, and it’s painful to undo.
A few rules we’d follow on any CRM:
- Start in a sandbox. Test your matching rules on a copy before touching production.
- Merge in small, reversible batches. Keep a log of what was merged into what.
- Decide survivorship first. For example: the record with the most recent activity wins, and the oldest created date is kept.
- Don’t merge on name alone. “Acme Inc” and “Acme Industries” may be different companies. Domain is a stronger starting point.
If you’re on Salesforce, HubSpot or Zoho, each has native duplicate tools. They’re fine for small clean-ups. Past a few tens of thousands of records, or with messy hierarchies, a custom approach is usually faster. Our CRM comparison covers how the platforms differ.
A quick illustration
Here’s an illustration (not a client story). Say a 40-person sales team on HubSpot has 30,000 accounts. An audit finds the same 2,000 companies entered twice, one version owned by a rep who left in spring.
Marketing’s routing rule sends new leads to the owner of the oldest record, so those leads sit unworked in a dead user’s queue. Nobody notices for months, because the lead count in the dashboard still looks healthy.
Fixing that takes a domain-based match, a survivorship rule and a reassignment, not a new tool. That’s the point: most hygiene problems are boring, specific and cheap to fix once you’ve measured them.
Keeping it clean after the cleanup
This is the part most teams skip, and it’s why they’re back in the same mess within a year.
- Validate on entry. Required fields, picklists and format rules stop most bad data at the door.
- Enrich on creation. Fill firmographics from a provider as the record is created, rather than in a yearly batch.
- Dedupe at the gate. Check new leads against existing accounts before they’re saved.
- Report weekly. Track duplicates, missing owners and blank required fields as a simple trend line.
- Assign an owner. Someone, usually RevOps, is accountable for data quality.
Agents help here. They can flag likely duplicates, fix formatting and fill gaps continuously, with a person approving anything destructive. If you’re thinking about putting AI on top of your CRM, our CRM AI readiness checklist is a good first read, and so is our post on automating CRM data entry with AI.
The bottom line
Clean data isn’t glamorous, but routing, scoring, reporting and every agent you plan to deploy depend on it. Audit duplicates first, fix the 15 fields that matter, and put controls in place so the cleanup lasts. If your CRM has grown past what a spreadsheet and a weekend can fix, talk to us about CRM data and enrichment.
Sources
- Salesforce, State of Sales report 2026: https://www.salesforce.com/news/stories/state-of-sales-report-announcement-2026/
Want this working for your team?
Book a free 30-minute consultation. We’ll review your current setup and use cases, show you how it would work for you, and leave you with a recommended plan.