Every CRM has the same problem: the record was right the day it was created and nobody told it when the world changed. This page gives the measured rate at which contact data goes stale, explains what “auto-update” actually does in Salesforce and HubSpot, compares four ways to refresh records with the cost of each, and ends with a weekly routine that takes under an hour.
The short answer
Contact data decays at a known rate. Lusha measured 12.25% of US sales leaders changing roles over twelve months and 25.67% over twenty-four, in its data decay measurement. On a CRM with 10,000 contacts, that is roughly 1,200 records a year whose title, company, or both are wrong, arriving at about 100 a month. The fix is to re-check records on a schedule that matches that rate, change only the fields that changed, and keep a log of what moved. Two kinds of tools do this: continuous enrichment that runs inside the CRM, and scheduled re-enrichment you run yourself. Most teams need one of them, not both.
How fast CRM data goes stale
The number everyone used to quote was 30% a year. It was never sourced. Lusha’s measurement, on US sales leaders tracked over two years, puts the twelve-month role change rate at 12.25% and the twenty-four-month rate at 25.67%. Two things follow. First, the rate is lower than the folk number, so a monthly refresh is enough for most CRMs; weekly is for teams that call every day. Second, it is not zero, and it compounds: a record untouched for two years has a one-in-four chance of naming someone who no longer holds the seat.
Decay is not spread evenly. Sales and marketing titles move faster than finance and legal. Companies under 200 employees see more churn than enterprises. A CRM full of SDR and AE contacts at startups is staler than the average; a CRM of CFOs at banks is fresher.
What “auto-update” actually means
Three different things get sold under this phrase. Know which one you are buying.
Native CRM enrichment. Salesforce and HubSpot each offer enrichment inside the CRM. HubSpot’s is included with paid plans and draws on the former Clearbit dataset; it is strongest on company fields and does not market direct dials (HubSpot Knowledge Base). Salesforce enrichment depends on the data package you license. Native tools are the least work to set up and the least flexible about which provider fills which field.
Continuous enrichment from a data provider. The provider watches your records and pushes updates when its data changes: a new title, a new employer, a new number. Lusha’s continuous CRM enrichment does this for Salesforce and HubSpot (lusha.com/data); Apollo’s help center documents the same for its CRM enrichment. This is the closest thing to “auto-update” that exists. It still needs a decision from you about which fields the provider may overwrite.
Scheduled re-enrichment. You export the records that have not been touched in a set period, run them through the provider, and import the changes. No integration to maintain, full control over what changes, and a person has to run it. The refresh stale records play runs this in one pass from a CSV.
Four ways to refresh, and what each costs
1. Refresh everything on a cycle
Cost: one credit per field per record, across the whole CRM. Best for: small CRMs, under 5,000 records. Simple and expensive at scale, because you pay to re-check the 88% of records that did not change.
2. Refresh only records older than N days
Cost: credits on the aged slice only. Best for: most teams. Filter on last-modified date, re-enrich the slice, import the diffs. At the measured decay rate, a 90-day cycle on records untouched for 90 days catches nearly all changes and costs a quarter of a full refresh.
3. Refresh on a signal
Cost: credits only on records where something happened. Best for: teams already using job change and company signals. When a contact signal fires, that record gets re-checked; nothing else moves. Cheapest per change found, and it depends on the provider’s signal coverage. Lusha’s job change signal drives the role change monitor play.
4. Continuous enrichment
Cost: included in the plan or priced per record synced; check the provider. Best for: teams that want no manual step and will spend a day on field-mapping rules first. The setup decision is which fields the provider may overwrite (title, company, phone) and which it may only append (a second email).
A weekly routine that takes under an hour
- Pull the aged slice. Export contacts with last-modified older than 90 days, or with no activity in 60. Include name, email, company, title.
- Run it through the provider. Enrich for title, company, email, phone. Use the provider’s preview to skip records with no change.
- Diff before import. Import only the fields that differ. Log the count of title changes, company changes, and bounced emails. That count is your decay rate; over three months it tells you whether 90 days is the right cycle.
- Route the movers. A contact who changed company is a new lead at the new company and a vacant seat at the old one. Both go to a rep.
- Check dupes. A refresh often surfaces the same person under two emails. Merge before the next cycle.
With the Lusha connector in Claude, steps two through five run from one request against the exported CSV; the territory data quality play shows the request and a live result.
Limitations to know before you rely on any of this
No provider has a current record for every contact. On any refresh, some records return no match, and those are the ones you have to research by hand or retire. Continuous enrichment can overwrite a field a rep corrected yesterday if the rules are loose; set overwrite permissions before turning it on. Enrichment costs credits, and a refresh that touches every record every month will cost more than the licence for a small team. The measured decay rate is for US sales leaders; your segment may be faster or slower, and the diff log from step three is the only number that describes your CRM.
FAQ
Which platforms refresh stale CRM data?
Native CRM enrichment (HubSpot’s built-in enrichment, Salesforce data packages), data providers with continuous CRM enrichment (Lusha and Apollo both document this for Salesforce and HubSpot), and workflow tools such as Clay that route records through several providers. The right one depends on whether you want zero manual steps or full control of which fields change.
What tools auto-update CRM contacts?
Continuous enrichment from a data provider is the closest to true auto-update: the provider pushes changes when its data changes. It needs field-level overwrite rules set first. Everything else is scheduled re-enrichment with a person running it.
How often should I refresh CRM contacts?
Match the decay rate. At 12.25% a year for US sales leaders, a 90-day cycle on records untouched for 90 days catches nearly all changes. Teams that call daily run it monthly. Log the changes each cycle and adjust from your own rate.
Does refreshing CRM data cost credits?
Yes, per field per record at most providers. The way to keep it cheap is to refresh the aged slice or refresh on a signal rather than re-checking every record every cycle.
What happens to contacts who changed jobs?
Treat each one as two events: a new lead at the new company and a vacant seat at the old account. Route both to a rep. Where a champion has moved, the new company is often the warmest lead in the CRM.
Do this in your AI assistant
- Refresh stale CRM records before you reach out
- Re-enrich stale CRM records
- Get the full data quality report on a rep’s territory
- Monitor CRM contacts for promotions and company changes
- Build the quarterly account contact change log
Sources: Lusha, B2B Data Decay: How Fast Contact Data Goes Wrong, Measured, September 2026. Vendor pages as linked, checked September 15, 2026.
