Data Decay
Data decay is the gradual loss of accuracy in CRM data as the people, companies and details it describes change over time. A contact moves to a new job, a company rebrands or moves to a new domain, a phone number is reassigned, and a record that was correct when it was entered no longer matches the real world. Also called CRM data decay or contact data decay, it affects every kind of record a CRM stores.
Decay happens even when every record was entered correctly, because the world changes while the record stays the same. It also has a second effect: when a person who's already in the CRM comes back with a new email address or at a new company, they're often added as a new record, so the out-of-date record and the current one sit side by side as duplicates. Keeping decay in check means updating records, and finding and merging the duplicates it creates.
See how Dedupely finds the duplicates data decay leaves in your CRM
What Is Data Decay?
Data decay, sometimes called B2B data decay when it's about business contacts, covers every change that makes a stored value stop being true. Common causes are people changing jobs or roles, email addresses that stop working when someone leaves a company, companies that merge, rebrand or move to a new domain, and phone numbers and addresses that change. Some decay is visible, such as an email that bounces. Much of it isn't: a job title or a company name can stay wrong for a long time without anything flagging it.
A typical example: "Maria Lopez, maria@acme.com, Acme, Marketing Manager" was added two years ago. Maria has since moved to a new team at Acme and now uses m.lopez@acme.com. When she fills out a form, a check on email address finds no match, so a second record is created. One record now holds her old email and two years of history, and the other holds her current details and none of that history.
Decay applies to every object: contacts and companies in HubSpot, accounts and leads in Salesforce, people and organizations in Pipedrive, leads in Close, and contacts in Nimble and Google Contacts.
Teams respond in two broad ways. Updating records, by hand, through outreach or with enrichment from outside sources, keeps the values in each record current, and its strength is that the record people already work from stays right. Deduplication finds the records that decay has split in two and merges them, and its strength is that history and current details end up on one record. Many teams use both.
How Data Decay Works
Data decay works through the gap between when a value is entered and when it stops being true. The record doesn't change when the person does, so the gap only grows.
- A record is created with correct details. A form fill, an import or a rep adds a contact or company with the email, phone, title and company that are true at that moment.
- Something changes in the real world. A person changes jobs or gets a new email address or phone number, or their company rebrands, merges or moves to a new domain. Nothing in the CRM records the change.
- The record goes stale. The old values stay in place. Some show signs, such as bounced emails or unanswered calls, but many look just as correct as they did when they were entered.
- The person comes back with new details. They fill out a form, are added from an event list or arrive through a sync, with a new email address or at a new company. A duplicate check on that new value often finds nothing, so a new record is created.
- The duplicate stays. The old and new records now describe the same person, each with part of the picture. Without deduplication in place, nothing brings them back together, and the next change can add another record.
Decay is continuous, and its pace varies with the data: contacts in fast-changing roles often change more than long-standing accounts. Finding the duplicates it creates means comparing records on values that change less often, such as a name with a company or a phone number, so the old and new records of one person can be paired.
Why Data Decay Matters for CRM Teams
Decayed data makes outreach less reliable. Emails sent to old addresses bounce, which can affect how well other emails get delivered, and calls go to numbers that no longer reach the person. Reps spend time on contacts who left a company months ago, and a lead routed on an old job title or company can end up with the wrong team.
Reports suffer too. A contact list full of people who've moved on overstates the audience a team can reach, and when decay creates duplicates, the same person is counted twice, with their activity split across two records. Attribution and pipeline tied to the old record don't show up on the new one, so the customer's history looks shorter than it is.
Decay also has a billing cost. Tools billed by contact count charge for every record, including the ones no one can reach and the duplicates decay creates, so the bill grows along with the decay.
Decay is easy to miss because nothing flags it. A wrong job title, or a duplicate created a year ago, looks as valid as a correct record, so the cost grows quietly until someone checks. Treating decay as a routine instead of a one-time cleanup keeps that cost from building up.
Getting Started With Data Decay
Start by finding where decay already shows. Bounced emails, unsubscribes, wrong numbers and records with no activity in a long time point to stale data. A search for the same name at the same company, or the same phone number on two records, points to the duplicates decay has created. Together, those lists show how much of the database needs attention.
Merge the duplicates before updating values, so each update lands on one record. When old and new records describe the same person, decide which values the merged record keeps: the most recently updated values often reflect the person as they are now, while the older record often holds the longer history. Records for people who have left a company may still be worth keeping for that history, marked as no longer current, instead of deleted.
Then make it a routine. Decay is continuous, so a one-time cleanup only resets the clock. Running the same duplicate checks on a schedule catches new records for existing people while they're still few, and a regular review of bounces and inactive records keeps the remaining values current.
In Dedupely, Duplicate Searches pair old and new records of the same person on fields that change less often, such as name + company or phone number. Auto Match and Auto Merge then keep those searches running as new records arrive, with Auto Match notifying you when new matches reach a count you set and Auto Merge merging new duplicates on a schedule.
Key Takeaways: Data Decay
Data decay is the loss of accuracy as people change jobs, email addresses and phone numbers, and as companies rebrand or move domains. It's continuous, it often goes unnoticed, and it creates duplicates when a person already in the CRM comes back with new details. Keeping it in check means updating records and merging the duplicates it creates, on a schedule rather than once. In Dedupely, Duplicate Searches pair old and new records of the same person on fields such as name + company or phone number, and Merge Rules decide which values each merge keeps, with blank values never winning. Auto Match and Auto Merge keep those searches running as new records come in: Auto Match notifies you when new matches reach a count you set, and Auto Merge merges new duplicates on a schedule.
Frequently Asked Questions About Data Decay
How fast does CRM data decay?
CRM data decays continuously, and the pace varies from one database to the next. It depends on who the records describe: people change jobs, roles and email addresses, companies rebrand or move domains, and phone numbers get reassigned, each on its own timeline. A database of business contacts in fast-changing roles often decays faster than one of long-standing customers or accounts. Because no single rate applies to every CRM, the useful measure is your own: how many emails bounce, how many records have had no activity in a long time, and how many new duplicates your searches find from one month to the next. Tracking those over time shows how fast your data goes out of date. In Dedupely, the Duplicate Report email shows your merges, with a trend, and the matches found, including Search matches and Dedupely Intelligence matches for each connected CRM. It's sent weekly by default, or monthly, and each person sets their own.
Does data decay create duplicate records?
Yes, data decay often creates duplicates, because a person whose details have changed is easy to add again as someone new. When a contact gets a new email address or moves to a new company, the next form fill, import or sync brings them in with details that don't match the old record. A duplicate check on email alone finds nothing, so a second record is created, and the old one keeps the history. Over time, one person can end up with a record for each email address they've used. Matching on values that change less often, such as name + company or a phone number, pairs those records so they can be reviewed and merged. In Dedupely, a Duplicate Search compares several fields at once, each with its own Match Option, such as Exact on last name and Fuzzy on first name. Auto Match and Auto Merge keep checking as new records come in, and new records are detected within 1–5 minutes.
How do you keep contact data current in a CRM?
Keep contact data current by updating records as a routine and merging the duplicates that changes create. Review bounced emails, unsubscribes and records with no recent activity on a schedule, and update or mark the ones that are out of date. Ask contacts to confirm their details when they get in touch, and set forms and imports to update an existing record where they can, instead of adding a new one. Updates alone leave a gap, though: when a person comes back with a new email, a new record is often created, and the current details end up on a different record from the history. Regular deduplication closes that gap. In Dedupely, Merge Rules decide which values win, so the last updated record can be the Primary Record, and blank values never win in a merge. Auto Merge can run as soon as possible, and new records are detected within 1–5 minutes, so new duplicates are merged soon after they appear.
Should you delete old CRM records or merge them?
Merge old records when they describe the same person as a newer record, and delete only the ones with nothing worth keeping. A record created before someone changed their email holds their history: calls, notes, deals and past activity. Deleting it loses that history, while merging it into the newer record keeps the history and the current details together. Records for people who have left a company are a different case. Some teams keep them, marked as no longer current, because they're tied to past deals and reports. Records with no history, no working contact details and no links to deals are the strongest candidates for deletion. In Dedupely, a merge preserves all activities and associations, such as notes, calls, tasks and linked companies and deals. Merges can't be undone, and Merge History shows each merge with every original record and its values. To keep two records apart, rejecting the match removes it from current and future Duplicate Searches.
What are the signs your CRM data is decaying?
The clearest signs are bounced emails, wrong phone numbers and people who are already in the CRM showing up as new records. Others are quieter: job titles and companies that no longer match what contacts say on calls, records with no activity in a long time, and a contact count that grows faster than the real audience. A rising number of duplicates is a strong signal, especially pairs where the name and company match but the email differs, because that's often one person entered twice after a change. Reports can show it too, when the same customer appears under two records or a campaign reaches far fewer people than the list holds. Checking these signs on a schedule shows whether decay is being kept in check. In Dedupely, a Duplicate Search on name + company or phone number shows these pairs, and the Duplicate Report email shows the matches found in each connected CRM, weekly by default.
