All data in this report is drawn directly from Lusha’s live signal database. Signal counts reflect contacts with a detected company change or promotion event in Lusha’s database between January 1 and June 1, 2026. Department and seniority breakdowns are based on Lusha contact classifications. Geography is based on contact location as recorded at the time of the signal. No third-party estimates or extrapolated figures are used. Source: Lusha B2B Contact Change Report Q2 2026.
121,238 sales contacts changed companies between January and June 2026. That is more than any other function tracked in Lusha’s database during this period. Sales is the most mobile function in the B2B contact universe — and the contact lists that B2B sales teams rely on most are also the ones decaying fastest.
This report maps what those 121,238 changes mean in practice: which seniority levels carry the highest commercial risk, what happens to an active deal when a sales contact departs, where the new-company opportunity window opens and closes, and what the coverage gap problem looks like when nobody is watching the account.
The numbers at a glance
Part One: Why Sales is the highest-volume data quality problem
Sales professionals move more frequently than any other function in the B2B contact universe. Average tenure in sales roles has been declining for several years and Q2 2026 continues that trend. The reasons are structural: commission structures reward external moves more reliably than promotions, equity is more concentrated at senior levels, and the supply of sales leadership talent is constrained enough that good operators are regularly recruited away.
The result is a function where the contact list is always in motion. A CRM built on sales contacts is a CRM that requires the most frequent verification of any data segment. Most teams verify it the least — relying on bounced emails, returned calls, and LinkedIn notifications to surface departures that Lusha’s signal database detects in real time.
The seniority split: volume vs consequence
Director and Head-of level shows the highest raw volume of company changes within the Sales function. These are the people who run sales regions, manage AE teams, and carry the relationships that persist through vendor renewals. When a Sales Director moves, the accounts they owned personally often go cold. The AEs they managed may not have direct relationships with the accounts at all.
VP-level and above show the lowest raw volume of changes but the highest individual impact. A VP of Sales who moves does not just create a data quality problem at the old company — they take the strategic vendor relationship with them. A vendor that was embedded at an account through a VP of Sales relationship may find that the new VP has their own preferred stack and the relationship needs to be rebuilt from scratch.
Part Two: Three problems every Sales contact departure creates simultaneously
Every sales contact who changes companies creates three separate data problems at the same moment. Most teams discover all three too late.
Part Three: The 30-day opportunity window
When a sales contact changes companies, the data quality problem at the old company is immediate. The opportunity at the new company is time-limited. Lusha’s signal data shows a consistent pattern: the window between a contact arriving at a new company and the new stack being locked in is approximately 30 days.
121,238 Sales contact changes in Q1–Q2 2026 means 121,238 of these windows opened in the first half of the year. The teams that caught the signal within 14 days worked a genuinely different opportunity than teams that found out via a bounce. The difference is not effort. It is whether anyone was watching.
Part Four: The coverage gap problem
The third problem created by every Sales contact departure is the one that surfaces latest and costs most. When a sales contact leaves an account, the selling organisation often has no other active contacts there. The account is not flagged as at-risk. It is simply not worked — until a renewal is due, a pipeline review surfaces it, or the next outreach attempt bounces.
The Q2 2026 data shows 121,238 Sales contacts changed companies in the first half of 2026. Each one represents a potential coverage gap at the old account. At any given moment, a sales team with a large contact database has a meaningful percentage of accounts where the primary contact has changed and the account is effectively unworked without anyone knowing it.
The most expensive version of this problem: A renewal account where the primary contact has changed, the new contact does not know the vendor, and the first outreach from the selling team is a renewal reminder — to an inbox belonging to the person who replaced the champion.
Part Five: What to do with this data
Three actions follow directly from the Q2 2026 Sales mobility numbers:
1. Monitor Sales contacts at Director level and above on a rolling daily cadence, not a quarterly one. Director and Head-of level show the highest volume of changes. VP and above show the highest impact per change. Both categories warrant daily monitoring on any active deal, open renewal, or named account. Quarterly verification is not adequate for a function moving at 121,238 changes per five months.
2. Build the new-company opportunity motion before the window closes. Every Sales contact who joins a new company represents a buying window that opens immediately and closes within 30 days. A team that detects the move on day 1 and reaches out by day 8 is working within the optimal window. A team that detects it via a LinkedIn notification three weeks later is already at the closing edge. The signal needs to come from a live data source, not from passive observation.
3. Audit coverage gaps on named accounts every time a Sales contact changes companies. The coverage gap problem is not visible in the CRM until someone looks for it. Build a weekly check on all named accounts where the primary contact has been flagged as departed — identify the new contact, verify them via Lusha, and assign them before the account goes dark.
Methodology and data notes
Data source: Lusha live signal database — 300M+ verified contacts, signals pulled June 1, 2026.
Signal window: January 1 to June 1, 2026 (108 working days).
Signal definitions: Company change signals reflect contacts where Lusha detected a move to a new employer during the reporting window. Seniority breakdowns are based on Lusha’s internal contact classification system applied at the time of the signal.
Privacy and compliance: All data in this report is aggregated and anonymised. No individual contact details are included or derivable from the figures presented. Lusha is fully GDPR compliant, certified by European independent auditors ePrivacyseal GmbH, and validated by TrustArc. Full privacy documentation is available at lusha.com/trust-center.
Source report: B2B Contact Change Report Q2 2026 — Lusha
