CRM Data Hygiene: How to Keep Your Contact Database Clean
On this page
Why CRM Data Goes Bad
CRM databases decay at a rate of roughly 25-30% per year. People change jobs, companies are acquired, email addresses become invalid, phone numbers change. Without active maintenance, your CRM becomes a repository of outdated records that waste sales time, distort reporting and damage email deliverability.
Common causes of CRM data decay:
- Job changes. The average professional changes jobs every 2-3 years. A 10,000-contact database loses 3,000-5,000 valid contacts annually.
- Company changes. Mergers, acquisitions, name changes, closures. The company the contact worked for may not exist anymore.
- Email domain changes. Companies rebrand, change email providers, or shut down email systems.
- Data entry errors. Typos, inconsistent formatting, wrong fields, incomplete records.
- Duplicate records. The same person entered multiple times with slight variations.
- Orphaned records. Contacts with no associated company, deal, or activity.
- Zombie records. Records that have not been updated or interacted with in years.
Diagnosing Data Quality
The CRM audit
Before cleaning, understand what you are working with.
Step 1: Count and categorise
| Metric | How to measure | What it tells you |
|---|---|---|
| Total contacts | CRM count | Scale of the cleaning effort |
| Contacts without email | Filter: email field empty | Unusable for email outreach |
| Contacts without company | Filter: company field empty | Incomplete records, difficult to segment |
| Contacts with no activity in 12+ months | Filter: last activity date | Potentially stale records |
| Contacts with bounced emails | Filter: email status or bounce flag | Known bad email addresses |
| Duplicate contacts | CRM duplicate detection or manual review | Inflated contact count, wasted effort |
| Contacts with no owner | Filter: owner field empty | Unmanaged records |
Step 2: Assess email validity
Export all email addresses from the CRM. Upload to Email Extractor to identify duplicates and extract a clean, deduplicated list. Then run the deduplicated list through an email verification service.
Expected results:
- A CRM that has never been cleaned may have 20-40% invalid emails.
- A well-maintained CRM typically has 5-10% invalid emails.
- Anything above 10% indicates a data quality problem worth addressing.
Step 3: Check for formatting inconsistencies
| Field | Common inconsistencies |
|---|---|
| Name | All caps, all lowercase, extra spaces, titles included (Mr., Dr.) |
| Company | Abbreviation variations (Inc vs Inc. vs Incorporated), parent vs subsidiary |
| Phone | Mixed formats ((555) 123-4567 vs 555-123-4567 vs 5551234567) |
| Address | Abbreviations (St vs Street vs ST), missing state/country |
| Uppercase, spaces, invalid characters | |
| Industry | Free text vs picklist, inconsistent terminology |
| Job title | Extreme variation (VP Sales vs Vice President of Sales vs VP, Sales) |
Cleaning Workflows
Phase 1: Remove the obvious
Delete or archive:
- Contacts with no email AND no phone AND no recent activity. These records serve no purpose.
- Known competitors (unless tracking them deliberately).
- Test records and dummy data.
- Records where the contact has explicitly requested deletion.
Merge duplicates:
- Use CRM duplicate detection tools.
- Merge rules: keep the record with the most complete data, the most recent activity, or the one owned by an active user.
- Before merging, verify that the duplicates are truly the same person (same company, same role) and not two people with the same name.
Fix bounced emails:
- Hard bounces: mark as invalid, do not attempt to email.
- Soft bounces: investigate. Temporary issues (mailbox full, server down) may resolve. Repeated soft bounces become hard bounces.
Phase 2: Standardise formatting
Email addresses:
- Lowercase all email addresses.
- Trim whitespace.
- Remove invalid characters.
- Fix common typos (gmial.com to gmail.com, yaho.com to yahoo.com).
Names:
- Title case (John Smith, not JOHN SMITH or john smith).
- Remove titles from name fields (move Dr., Mr., etc. to a separate field if needed).
- Separate first and last names if stored in a single field.
Phone numbers:
- Choose a format and apply it consistently.
- Include country code for international contacts.
- Validate that numbers have the correct number of digits for their country.
Company names:
- Standardise legal suffixes (choose Inc. or Incorporated, LLC or L.L.C., and apply consistently).
- Use the company's official name as shown on their website.
- Resolve parent/subsidiary inconsistencies (decide whether to list contacts under the parent or the subsidiary).
Addresses:
- Standardise abbreviations.
- Validate postal codes.
- Add missing state/province or country.
Picklist fields (industry, source, status):
- Review all values currently in use.
- Consolidate variations (Marketing and marketing and Mktg should be one value).
- Map old values to standardised values.
- Lock down the field to prevent free-text entry going forward.
Phase 3: Enrich incomplete records
After cleaning and standardising, identify records with missing critical fields.
Critical fields for B2B contacts:
- Email address.
- Company name.
- Job title or function.
- Industry.
- Company size (employee count or revenue range).
Enrichment approaches:
- Manual research (LinkedIn, company website) for high-value accounts.
- B2B data provider API enrichment (ZoomInfo, Apollo, Clearbit) for bulk enrichment.
- Progressive profiling (collect additional data over time through form submissions and interactions).
See Data Enrichment Workflows.
Phase 4: Verify emails
After deduplication, standardisation and enrichment, verify all email addresses.
- Export the full email list from the CRM.
- Run through an email verification service (ZeroBounce, NeverBounce, Bouncer, etc.).
- Update the CRM:
- Valid: no action needed.
- Invalid: mark as invalid, suppress from email sends.
- Risky (catch-all, disposable): flag for cautious use.
- Unknown: re-verify in 48 hours; if still unknown, flag.
See Email Verification Service Comparison.
Automation Rules
Prevent bad data from entering
Form validation:
- Required fields on all web forms.
- Email syntax validation.
- Domain verification (reject disposable email domains).
- Duplicate checking before creating a new record.
CRM validation rules:
- Required fields for new record creation (at minimum: email, company, source).
- Field format validation (phone number format, email format).
- Duplicate detection on record creation.
- Picklist enforcement (no free-text entry on standardised fields).
Integration validation:
- Data from integrations (forms, marketing automation, third-party tools) passes through validation before creating CRM records.
- Map fields explicitly (do not allow unmapped fields to create new custom fields automatically).
Automate ongoing cleaning
Scheduled automation rules:
| Rule | Frequency | Action |
|---|---|---|
| Bounce processing | After every email send | Mark hard bounces as invalid, update email status |
| Duplicate detection | Weekly | Flag potential duplicates for review |
| Stale record detection | Monthly | Flag contacts with no activity in 12+ months |
| Email re-verification | Quarterly | Batch-verify all active email addresses |
| Owner reassignment | On employee departure | Reassign orphaned contacts to active reps |
| Data completeness check | Monthly | Report on records missing critical fields |
Trigger-based automation:
| Trigger | Action |
|---|---|
| Email bounces (hard) | Set email status to invalid, add to suppression list |
| Contact replies with new email | Update email field, verify new address |
| LinkedIn shows job change | Flag for review, update company and title if confirmed |
| Company website returns 404 | Flag company record for review |
| Contact unsubscribes | Update consent fields, suppress from marketing |
| Contact requests deletion | Trigger deletion workflow across all systems |
Ongoing Maintenance Schedule
Daily
- Process bounces from email sends.
- Review new duplicate flags.
- Handle data subject requests (access, deletion).
Weekly
- Review contacts flagged by automation rules.
- Merge confirmed duplicates.
- Update records flagged for job changes or company changes.
Monthly
- Run data completeness report.
- Review and clean contacts with no activity in 12+ months.
- Check for new formatting inconsistencies (especially in free-text fields).
- Review suppression list additions.
Quarterly
- Batch email verification of all active contacts.
- Enrichment run for records with missing critical fields.
- Review and update segmentation criteria.
- Report data quality metrics to stakeholders.
Export contacts from all connected systems quarterly, upload to Email Extractor to identify cross-system duplicates, then reconcile differences.
Annually
- Full CRM audit (repeat the diagnostic process from the beginning of this guide).
- Archive contacts with no activity in 24+ months (do not delete; archive).
- Review and update validation rules and automation.
- Review data governance policies.
- Train new team members on data entry standards.
CRM-Specific Guidance
Salesforce
Built-in tools:
- Duplicate rules and matching rules.
- Validation rules on fields.
- Data.com (deprecated, but legacy data may still exist).
- Report-based data quality monitoring.
AppExchange tools:
- DemandTools (data quality management).
- Cloudingo (deduplication and cleaning).
- RingLead (data quality and routing).
- Validity (DemandTools) for ongoing quality management.
HubSpot
Built-in tools:
- Duplicate management (identify and merge).
- Property validation (required fields, field types).
- List-based segmentation for identifying data quality issues.
- Operations Hub (data quality automation, formatting).
HubSpot Operations Hub features:
- Automated formatting (capitalisation, phone formatting).
- Data quality recommendations.
- Custom automation for data cleaning.
Pipedrive
Built-in tools:
- Duplicate detection on contact creation.
- Required fields on deal and contact creation.
- Smart contact data (basic enrichment).
Zoho CRM
Built-in tools:
- Duplicate detection and merge.
- Validation rules.
- Data enrichment (Zia AI).
- Blueprint (process enforcement).
Measuring Data Hygiene
Key metrics
| Metric | Target | Formula |
|---|---|---|
| Data completeness | 90%+ | Records with all critical fields populated / total records |
| Email validity rate | 95%+ | Valid emails / total emails |
| Duplicate rate | Under 3% | Duplicate records / total records |
| Bounce rate | Under 2% | Bounced emails / emails sent |
| Data freshness | 80%+ updated in last 12 months | Records updated in last 12 months / total records |
| Contact-to-company ratio | 1.5-3.0 | Total contacts / total companies (too high suggests duplicates) |
| Orphan rate | Under 5% | Contacts with no company or activity / total contacts |
ROI of data hygiene
Direct costs of bad data:
- ESP charges for invalid contacts (most charge by contact count).
- Sales time wasted on outdated contacts (research estimates 27% of sales time).
- Marketing spend on unreachable contacts.
- Compliance fines for emailing people who have opted out.
Indirect costs of bad data:
- Inaccurate pipeline reporting (decisions based on wrong data).
- Damaged sender reputation (high bounce rates, spam complaints).
- Lost deals (contacting the wrong person, using outdated information).
- Low team morale (sales reps frustrated by bad data).