Thought Leadership, Digital PR & Content SyndicationPlaybook3 min readUpdated September 2026

A Quarterly Runbook for Keeping Your CRM Data From Rotting

CRM data doesn't break all at once. It rots quietly: a contact changes jobs and their email starts bouncing, a company gets acquired and the account record still shows the old name, two reps create duplicate records for the same account without realizing it. None of it looks urgent in the moment, and all of it adds up.

A quarterly runbook catches this before it compounds into campaigns sent to dead addresses and account tiers built on outdated company sizes.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

How do you measure how bad your CRM data is?

Before fixing anything, run a baseline check: what share of contact records have a valid, recently verified email, how many company records haven't been touched in over a year, and how many likely duplicate accounts exist based on matching domain names. You can't tell whether your hygiene process is working if you never measured the starting point.

Don't skip this step because it feels like busywork before the real fix. A rough baseline, even a manual sample of a hundred records, tells you whether the problem is modest or genuinely widespread, which changes how much time the rest of the runbook deserves.

Write the baseline numbers down somewhere you'll actually look at again next quarter. Without a recorded starting point, it's impossible to tell whether the next cycle's cleanup is actually improving things or just treading water.

Why should you deduplicate accounts before enriching them?

Enriching a duplicate record just wastes the enrichment credit twice on the same company. Run a duplicate check by domain and company name first, merge what you find, and only then pull fresh firmographic and contact data into what's left.

Apollo handles the enrichment step well once duplicates are cleared, pulling updated firmographic and contact fields directly into your CRM instead of you researching each account by hand one at a time.

When merging duplicates, keep the record with the most complete activity history rather than defaulting to whichever one was created first. The oldest record isn't always the one your team has actually been working.

Flag records that are stale, not just wrong

A record can be technically accurate and still stale: correct information from eighteen months ago that no longer reflects the company's current size or situation. Set a rule that any account record untouched for more than a set period gets flagged for a re-check rather than assumed to still be accurate.

This matters most for the accounts your tiering or scoring model relies on. A tier-one account scored on employee count from a year and a half ago may no longer belong in that tier at all, and nobody would know without a re-check built into the process.

When you can't clean everything in one quarter, decide the order by what the data feeds. Start with the accounts your tiering or scoring model relies on, then the segments in your next campaign, then the rest. For example, if a large send is due next month, verify and refresh that segment first, and leave the long tail for the following cycle. Record what you skipped so it doesn't disappear. A partial cleanup with a clear priority order does more than an ambitious one that stalls halfway and leaves nobody sure which records were checked.

Clean before you send, not after a bounce spike

Verify email deliverability on a segment before a major send, not after open rates crater and you're trying to figure out why. lemlist includes deliverability signals that help catch this earlier in the process, rather than discovering the problem only once a campaign has already gone out to a list full of dead addresses.

A sudden jump in bounce rate on a list that was fine last quarter is usually a hygiene problem, not a content problem, and chasing a subject line fix when the real issue is dead addresses wastes a cycle you didn't need to lose.

Put the whole cycle on a repeating calendar entry

The runbook only works if it actually repeats. Put a recurring quarterly block on the calendar: baseline check, deduplication, enrichment refresh, and a deliverability sample, each with a named owner. If you're comparing enrichment tools to run this cycle, Apollo, ZoomInfo, and Lusha covers the main options.

Treat a skipped cycle as a real cost, not a minor miss. Two skipped quarters in a row is usually enough for the data to drift back to where it started, undoing whatever the last cleanup accomplished.

Put these steps in the recurring quarterly block, each with a named owner:

  1. Baseline: measure how many contacts have a verified email, how many company records are untouched for a year, and how many likely duplicates exist, then record the numbers.
  2. Deduplicate accounts by domain and company name, keeping the record with the most complete activity history.
  3. Enrich the cleaned records only, refreshing firmographic and contact fields so you don't pay to enrich the same company twice.
  4. Flag stale records: any account untouched beyond your set period gets a re-check, especially accounts your tiering or scoring depends on.
  5. Verify deliverability on a sample segment before your next major send.
Executive Capability Standard

What Good Looks Like

Good CRM hygiene means a measured baseline, duplicate accounts merged before enrichment, stale records flagged for re-verification on a schedule, and deliverability checked before major sends rather than after a bounce spike.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Sample a hundred contact and account records and check how many have a verified email and current company information.
2. Do Manually:Run a manual duplicate check by domain name and merge the records you find before your next campaign send.
3. Delegate:Assign a revenue operations or marketing ops owner to run the quarterly hygiene cycle as a standing responsibility.
4. Automate:Use a tool like Apollo to refresh firmographic and contact data automatically instead of researching accounts by hand.
5. Buy:Bring in a data cleanup specialist for a one-time deep clean if your CRM hasn't had a real hygiene pass in over a year.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Frequently Asked Questions

How often should we run a full CRM data hygiene pass?

Quarterly is a reasonable default for most small and mid-sized companies. A faster-growing company with a lot of new accounts and contacts flowing in might benefit from a lighter monthly check on top of the full quarterly pass.

Should marketing or sales own CRM data hygiene?

It genuinely needs both, since sales reps create and touch records daily while marketing depends on that data for segmentation and sends. Assign one clear owner for the quarterly process itself, even if the actual data entry habits involve the whole team.

What's the biggest cause of CRM data going bad?

Company and contact records not getting revisited after initial entry, not bad data entry in the first place. A contact entered correctly a year ago is often wrong today simply because the person changed roles, and nobody's process catches that kind of natural decay.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides