Explainer
CRM data decay: why records go stale and how to fix it
Contact data has a shelf life. Industry estimates put B2B contact decay at roughly 30 percent per year, which means a third of your CRM records have at least one meaningful piece of information that is now wrong by the time twelve months have passed. Here is what causes it, what it actually costs, and how to fix it without a large migration project.
The half-life of a contact record
People change jobs. They get promoted. Companies get acquired. Job titles get reorganized out of existence. Email addresses stop working. Phone numbers get reassigned.
None of this is surprising. The scale of it is. A CRM built on data from three years ago is working from records where a large share have at least one meaningful piece of information that is no longer correct. The contact who was Head of Engineering is now at a different company. The company that was a target account was absorbed into a parent and no longer makes its own purchasing decisions. The email address you have for the right person now bounces.
The problem is not that data decays. That is just reality. The problem is that a CRM does not tell you which records are fresh and which have gone stale. Without that signal, you are treating three-year-old data the same way you treat last month's data, and making outreach and sales decisions on information that may not reflect anyone's current situation.
Three types of decay that happen in every CRM
Contact information decay
Email addresses stop working. Phone numbers change or go to someone new. A LinkedIn profile no longer matches the role in your CRM. This is the most obvious kind of decay and the easiest to detect after the fact, but easy to miss until you try to reach someone and get a bounce or no response.
Organizational decay
The person is still at the company but their role has changed. The champion you built a relationship with is now in a different department with different priorities. The company itself has merged, been acquired, or restructured. Your account record may still describe a version of the organization that no longer exists.
Relationship and intent decay
The hardest to measure. A contact who was warm six months ago may have gone cold for reasons you were never told. A company that was exploring a project may have put it on hold internally. A deal that looked close may have been cancelled without anyone notifying you. The record is technically current. The context is not.
The wrong contact at the right company
Tiago worked in business development for a software consultancy in Porto for several years before moving into product writing. He tells a story about data decay that he describes as embarrassing in retrospect but also just a predictable outcome of not maintaining records.
"We had a target account we had been trying to reach for about two years. No success. One of our newer BDRs found a contact in an old database, wrote a very warm re-engagement email referencing a project we had done for the company previously, and mentioned we were looking forward to continuing the relationship."
"The contact had left the company. The company had been acquired by one of our competitors. The project we mentioned had not ended well, and the new ownership was aware of that. The person who received the email was the integration lead trying to wrap up all vendor relationships from the old entity."
"The reply was polite. Barely." He pauses. "The worst part was that five minutes of checking LinkedIn before sending would have caught all of it."
He says the pattern is consistent: nobody schedules time to clean CRM data because it does not feel like revenue work. "But every outreach you send to the wrong contact at a changed company is a small reputation event. Enough of them and you start to seem careless to people who are actually watching."
What data decay actually costs
The obvious cost is bounced emails and failed calls. The less obvious ones add up faster:
- Wasted effort. Your BDR spends time researching and personalizing an outreach for a contact who left the company eight months ago. That time is gone, and it happens repeatedly across a team working from a stale database.
- Embarrassing missteps. Sending a re-engagement email that references a project the company no longer owns. Addressing someone by a title they changed two years ago. Reaching out to the wrong division of a company that restructured. These are avoidable, and each one leaves a small impression.
- Bad forecasting. A pipeline full of deals connected to contacts who have since left their companies is optimistic in ways that are hard to detect until a review goes wrong. Pipeline quality depends on contact quality.
- Missed re-engagement opportunities. A contact who moved to a new company and would be a strong prospect at their new employer gets treated as an existing contact at their old company. The opportunity is right there in your CRM, invisible because the record never got updated.
How to audit a stale CRM without a big project
You do not need a data migration project. These steps can be done in stages, prioritizing the records that matter most right now.
- Email engagement filter. Pull contacts with no email opens or replies in the past 12 months. These are your highest-risk records. They may be inactive, or the contact address may have been routing to nobody for months.
- Bounce rate check. If you send any email campaigns, segment by hard bounce rate and start there. Hard bounces almost always mean the contact has left the company or the address was never valid. These are easy to identify and safe to flag for review.
- LinkedIn reconciliation. For your top 50 to 100 accounts, check contact records against current LinkedIn profiles. It takes a few hours but surfaces the gaps you did not know existed. The person listed as Head of Engineering may now be CTO at a different company.
- Deal contact audit. For any deal that has been open longer than six months, verify that the contacts attached to it are still in their listed roles. A deal tied to a champion who left three months ago is not a live opportunity in any meaningful sense.
Ongoing prevention vs periodic cleanup
Fixing a stale CRM is a project. Keeping it from getting stale again is a system. Those two things need different approaches.
Prevention tools that help: email sync that captures bounces and updates engagement dates automatically, LinkedIn sync that flags profile and company changes, and enrichment services that periodically verify contact information against current external data. None of these eliminate decay entirely. They shift the problem from "the data is wrong and we don't know" to "the data may have changed and here is a flag."
The realistic goal is not a CRM that is always 100 percent accurate. It is a CRM where the freshest data is surfaced for active deals and the oldest, most uncertain data is flagged before someone acts on it. That is a much more achievable target, and it is where most of the practical value is.
How Lumenbase approaches this
Lumenbase is built around the assumption that manual data maintenance will not happen consistently, and that the system needs to do the tracking work that people will not.
- LinkedIn sync via the browser extension. When a contact changes jobs or updates their profile on LinkedIn, the change appears on the contact record without anyone manually checking. Job changes, title updates, and company moves surface automatically.
- Email engagement tracking. The system notes when emails stop generating replies or produce bounces, flagging those contacts for review before you send another outreach that goes nowhere.
- The Feed. Surfaces contacts and companies that have had no interaction for an extended period. It is easier to spot records that may be out of date when they are surfaced proactively, rather than discovering the problem when you are ready to reach out.
- Lumo. When preparing context before a call or writing an outreach, can flag when the most recent verified interaction with a contact was and note any gaps in contact verification. Working from stale context is one of the more avoidable mistakes in relationship sales.
Who this is for
Sales and business development teams at B2B service firms where relationship quality matters more than contact volume. Software agencies, consulting firms, and IT services companies where a single stale record sent to a wrong contact can close a door that took two years to open. If your team has a CRM that has been running for more than a year without systematic data review, there is almost certainly a data decay problem waiting to surface at the worst possible moment.
