Keeping CRM contacts current when people move roles
Nobody announces that a contact has left. The record just quietly stops being true. Here is what catches it, what to do about it, and what stays unknown.
A contact record is correct on the day it is written. After that it drifts. The person is promoted, moves to another site, leaves for a competitor or retires, and nothing in the CRM changes until a rep sends an email and gets a bounce, or worse, gets a polite reply from a stranger.
In our experience a sales database that has been running for a few years has a meaningful share of contacts who no longer hold the role on their record. The exact share depends on the industry and how often the team actually writes to its contacts, so we do not quote a figure here. What matters is that the drift is continuous, and that it is rarely anyone's job to notice.
What tells you a person has moved
Most of the evidence is already arriving. It just is not being read.
- A bounced email, or an automatic reply that says the person has left and names a replacement. Both are facts about the record, not just about one send.
- A reply from the mailbox's new owner. Often the most useful signal, because it tells you who inherited the responsibility.
- A change on a public profile: a new title, a new employer, a new location.
- A company's own team page, press release or site listing naming someone else in the role.
- A verification check that used to pass and now fails.
Each of these says something different. A bounce says the address is dead. A new title at the same company says the person may still matter, in a different role. A new employer says the role is now open at the company you care about, and that the person may be worth following to where they went.
What to do with the signal
The temptation is to delete or overwrite. We would not do either without a rule.
Flag first. A contact whose address has failed or who appears to have moved gets a status on the record, not a deletion. The sales team can see it, and the history stays.
Reopen the role, not just the contact. If the budget holder has left, the account now has a budget-holder gap. That gap is what the research should fill, and it should show on the record as open until it is.
Follow the person where it makes sense. Someone who was a champion at one account and has moved to another company in your market is a new prospect with a known relationship. That is worth a separate, deliberate decision rather than an automatic record.
Protect what your team entered. Notes, deal history and anything a rep typed by hand stay. Only the agreed fields are updated, and only on a rule.
What catches it continuously
Checking every contact once is a clean-up. Keeping them current is a cycle: recheck roles and addresses on an agreed schedule, read replies in the team's mailboxes for job changes and new addresses, and verify again before anything goes out. The weekly report then shows how many contacts moved, how many roles reopened and how many were filled again.
In the fictional Meridian Industrial Supply example, suppose Rachel Ng, the Finance Director, leaves. Her record is flagged rather than deleted, the budget-holder role on Meridian goes back to open, the search for her replacement starts, and the report that week shows one role reopened at that account. Nothing a rep wrote about her is lost.
What stays unknown
Some moves are never announced anywhere public. Some replacements take months to appear. A person can change title without changing responsibility, or keep a title while losing the budget. The honest record says what was checked, when, and what could not be confirmed, and leaves the gap visible rather than filling it with a guess.
That is the work described on improving the records you already hold and finding the right people. If your contacts have been drifting for a while, tell us roughly how many you hold and we will say what a first pass would look like.