When someone leaves, the HR system disables their email and the laptop comes back. The CRM is where things go wrong. A salesperson’s account is typically tied up with open deals, scheduled reports, email templates, workflow rules that name them as owner, API tokens they created, and personal exports sitting in a downloads folder. Delete the account carelessly and some of that breaks. Leave it alone and you have a live login for someone with no reason to have one.

The goal is a sequence that closes access quickly while transferring what the business depends on.

Separate “Cut Access” From “Remove the Account”

These are different actions with different timelines, and conflating them causes most offboarding mistakes.

Cutting access should be immediate, or at the moment of departure for sensitive roles. It means the person can no longer sign in or pull data.

Removing the account can wait, because the user record is often the owner of other things. In many CRMs, you can deactivate or freeze a user rather than delete them, which stops login while preserving record history and ownership references. Check your platform’s current documentation for what deactivation does and whether it releases the licence.

The first, urgent step is therefore deactivation, not deletion.

What to Do on Day Zero

1. Disable sign-in. If you use single sign-on, disabling the identity provider account may be enough, but also confirm that the CRM does not still accept a local password.
2. End active sessions. Many platforms let an admin force logout. Use it so an open browser tab does not outlive the account.
3. Revoke personal API tokens and connected apps created by that user.
4. Remove mobile access, including any device-bound sessions or remote-wipe options your platform provides.
5. Review recent activity. Look at the last days of exports, mass updates and report downloads for anything unusual. This is routine diligence and is more important when the departure is not amicable.

Reassign Ownership Deliberately

Records owned by a departed user fall into holes. Decide, before the person leaves where possible, who takes each category:

• Open deals and active accounts: assigned to a named successor by the sales manager, ideally with a handover conversation.
• Leads in progress: routed back to the lead queue or a named rep, with the follow-up dates intact.
• Tasks and reminders: reassigned or closed, so they do not silently fire into a deactivated mailbox.
• Cases or tickets: reassigned by the support lead.
• Shared reports, dashboards and templates: moved to a shared folder or a team owner so they do not disappear or lose visibility.

A common trap is bulk-reassigning everything to the manager “temporarily.” Months later the manager owns hundreds of records they never touch, and the territory reports are wrong.

Find the Hidden Dependencies

Run a search for anything that references the user by name or ID:

• Workflow and automation rules that assign records to them, send email as them, or notify them.
• Approval chains where they were an approver.
• Email-to-CRM addresses, shared inboxes and calendar sync tied to them.
• Integrations that authenticate as their user.
• Scheduled reports and subscriptions delivering to their address.
• Territory or round-robin assignment lists.

The integration case is the most expensive surprise. If a sync was set up with a person’s credentials, deactivating them stops the sync. Moving integrations to dedicated service identities is the lasting fix, and offboarding is when you discover which ones need it.

Offboarding Task Table

Area	Action	Owner
Sign-in	Disable login, end sessions, check SSO and local password	CRM admin / IT
Tokens and apps	Revoke personal API tokens and connected apps	CRM admin
Records	Reassign deals, leads, tasks, cases to named people	Sales or support manager
Automations	Update workflows, approvals, routing, notifications	CRM admin
Reports	Move shared assets to a team owner	CRM admin
Data held offline	Request return or deletion of exports, per policy	Manager / HR
Licence	Release seat once nothing depends on the user	CRM admin
Record of action	Log date, actions taken and who approved	CRM admin

A Hypothetical Example

A regional account executive gives notice. Her manager schedules a handover week. In that week, the admin runs a dependency search and finds that a lead-routing rule sends all new enquiries from one region to her, and a weekly forecast report is scheduled from her account to the leadership team.

On her final day, the admin reassigns the routing rule to a regional queue, moves the forecast report to a shared folder owned by sales operations, and transfers her open deals to two named reps. Only then does the admin deactivate her user, revoke her tokens and release the seat. Nothing breaks on Monday, and there is a short record of what was done and by whom.

Handling Data That Left the Building

Departing employees may hold exports, spreadsheets or notes derived from CRM data. Your policy and employment terms govern what you can require, and these vary by jurisdiction, so consult qualified legal or HR advice for contentious cases. Operationally, a reminder of the data-handling policy at exit and a request to confirm deletion is a sensible baseline. Limiting bulk export permissions in advance is far more effective than chasing files afterward.

Make It Routine

Tie CRM offboarding to the HR departure process so the admin is notified automatically, not by a hallway comment. Use the same checklist each time. For contractors and temporary users, set an expiry date when you create the account so access ends by default.

Frequently Asked Questions

Should we delete or deactivate departed users? Deactivate in most cases. It stops access while preserving history and ownership references. Delete only when your policy requires it and you have confirmed nothing depends on the user.

How quickly should access be removed? At the time of departure, or earlier for roles with sensitive data access. Prompt action matters more than perfect paperwork.

What about shared logins? Avoid them. A shared login cannot be offboarded cleanly. If you find one, replace it with named users.

Do we need to keep the licence until records are reassigned? Often you can deactivate the user and still reassign records as an admin. Check how your platform treats licences for inactive users.

Who should approve reassignment of accounts? The sales or service manager who owns the territory, not the admin alone.

Next Step

Create a one-page offboarding checklist from the table above and add a recurring task to review active users against the current employee list each quarter.