CRM handover when a salesperson leaves: what to do before their last day

Direct answer

A departing rep's deals, contacts, notes and follow-ups belong to the company, and the CRM should show that on their last day, not three weeks later when a client asks who is handling their account. The handover has seven parts: audit what the person owns, reassign it by rule, detach their email and calendar sync, capture conversations that never made it into the CRM, revoke access, check which automations depend on their user, and write a short handover record. Do the audit and reassignment while the person is still there, because they are the only one who knows which deals are real.

1. Audit what the person actually owns

Start with a filtered view rather than memory. Most CRMs let you filter records by owner, so build one view per object type and export it to a sheet before changing anything (check what your platform supports). You are looking for:

• Open deals, split into active, stalled and already dead but never closed
• Contacts and companies where they are the owner, including ones with no open deal
• Open tasks and overdue tasks, since these are promises someone made to a client
• Sequences, cadences or scheduled emails that are still running under their name
• Leads assigned to them that were never worked
• Custom owner-like fields, such as account manager or secondary owner, that a standard owner filter will miss

2. Reassign by rule, not by dumping

The lazy handover moves everything to the manager, who then cannot work it. Decide the rule per category before touching records:

• Active deals in the last two stages: hand to a named person with a warm introduction, ideally in a short call with the departing rep present
• Active early-stage deals: return to the normal routing rules so they are distributed the way new leads are (see [route leads between sales teams](/route-leads-between-sales-teams/))
• Existing customers: assign to the account owner for that segment, not to whoever has capacity
• Stalled deals with no activity for a long period: do not reassign blindly; mark them for a decision, close them with a reason, or move them to a nurture list
• Contacts with no deal: reassign in bulk to a holding owner and review, rather than leaving them owned by a deactivated user

3. Detach email and calendar sync

A connected inbox is a quiet dependency. While it stays connected, new emails with clients continue to attach to records under the departing user, and a deactivated mailbox can leave a gap in the timeline. Before the account is closed, note which mailbox and calendar connections exist, decide whether the shared sales mailbox should take over the client conversations, and disconnect the sync deliberately. Also check any personal email templates, snippets and meeting links: if a client has the departing rep's booking link, it needs to redirect somewhere or you will lose inbound meetings without noticing.

4. Capture what never made it into the CRM

The CRM only knows what was logged. Book a 30 to 45 minute exit conversation, ideally in the last week, and walk the open deal list together. For each active deal ask four questions: what did the buyer last say, what did you promise, who else is involved, and what is the next step with a date. Write the answers as a note on the deal, dated and marked as handover. Then ask about the conversations that live elsewhere: phone contacts, messaging apps, personal notes and calendar entries. This is not about surveillance; it is about the client relationship not depending on one person's phone.

5. Revoke access in the right order

Order matters. Reassign first, then detach sync, then deactivate. If you deactivate a user before reassigning, some platforms leave records without a valid owner, which breaks views and automations that filter by owner. On the day, remove CRM access, exports and API tokens the person created, and any shared tools connected to the CRM. Check which integrations were authorised under the person's own login: an integration connected with a personal account can stop working when that account closes, and it will not warn you.

6. Check automations that depend on the user

Look for workflows, routing rules and notifications that name the person, whether as owner, as a notification recipient or as the fallback assignee. Round-robin lists often include every rep and will keep assigning new leads to a user who is no longer working. Also check reports and dashboards filtered by that user: they will start showing zero and someone will misread it as a performance drop. If ownership rules are hard-coded to people rather than to roles or teams, that is a design issue worth fixing once so that the next departure does not repeat this exercise.

7. Write a one-page handover record

Keep it short and put it where the next manager can find it. Record the date, the person, how many deals and contacts were reassigned and to whom, which deals were closed with what reason, which automations were changed, which access was removed, and any open questions. This record is what lets you answer a client, an auditor or a new hire without reconstructing the story. It also turns the next departure into a repeatable process rather than a scramble.

When the handover is messier than a checklist

If ownership is unclear across a large number of records, there are duplicate contacts under several reps, or nobody trusts the pipeline stages, a checklist will only move the mess to a new owner. Those problems are fixed at the source. Duplicates are covered in how to merge duplicate CRM records safely, and recurring manual tidying in manual CRM cleanup automation. If you want the structure fixed rather than patched, CRM & Sales Workflow Implementation starts with a review of your setup and covers ownership rules, pipeline and cleanup in one scoped piece of work. The CRM migration complexity estimator is a free way to see how complex your data is before you talk to anyone.