Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

CRM & Marketing Automation › CRM for Marketers

Reassigning CRM Records When Someone Leaves

How to hand over CRM records when someone leaves: owned records, open deals and tasks, routing groups, emails sent in their name, alerts and access.
Tutorialbeginner8 min readUpdated

Why leavers leave leads behind

The CRM fundamentals guide says every record needs an owner, who receives its tasks and notifications and is accountable for its state, and that records with no owner are the ones nobody follows up. A leaver turns a whole set of records into exactly that, without any of them appearing in a report of unowned records, because they still have an owner on paper.

The leak shows up in several places at once. New enquiries keep arriving in the leaver's slot of a round-robin group, so a share of new leads goes to an inbox nobody reads, which is one of the causes the diagnosis of sales not following up leads traces. Open deals lose their next step. Customers miss renewals. And the automated first-touch email that the lead stages and pipeline guide recommends sending in the owner's name keeps arriving from someone who has gone. A routing or alert step still pointing at a leaver is also one of the causes the diagnosis for a CRM workflow that is not running separates, because the workflow looks live while nobody receives anything.

What the person leaves behindWhere it hidesWhat breaks if it is missed
Open dealsPipeline views filtered by ownerNext steps lapse; renewals are missed
Contacts and companiesOwner field on each recordNobody follows up; reports show activity falling
Open and overdue tasksThe leaver's task queuePromised calls never happen
Routing and round-robin slotsAssignment rules and groupsNew leads go to an unread inbox
Sequences and emails in their nameTemplates, sender settings, sequencesCustomers hear from someone who has left; replies vanish
Alerts, reports and workflow notificationsWorkflow actions and subscriptionsSignals reach nobody
Integrations and accessConnections authorised as the person; their sign-inConnections stop; a former colleague keeps access

The handover is short when it is a routine and long when it is improvised. The automation governance guide makes ownership transfer of workflows a step in the leaver process; this tutorial extends that step to everything else the person owns in the CRM. Outside the CRM, the tutorial on handing over marketing work when someone leaves collects the leaver's recurring tasks, open work, files and know-how, and runs this reassignment as one of its steps.

Before you start

Gather four things. Administrator access to the CRM, including the ability to filter every object by owner and to see workflow, routing and integration settings. The written owner rules (by account, territory or segment), which the inbound lead handling playbook and the fundamentals guide describe. The leaver's leaving date and, if possible, an hour of their time before it. And the automation inventory, which lists the workflows that might reference them.

Then agree who does what. A RACI matrix with one accountable person per row keeps the handover from stalling between sales and operations.

TaskResponsibleAccountableConsultedInformed
List the footprintCRM administratorSales operations leadThe leaverSales manager
Decide new ownersSales managerSales managerAccount managersNew owners
Reassign deals with notesThe leaver, or the sales manager if they have goneSales managerNew ownersFinance, where renewals are affected
Reassign contacts, companies and tasksCRM administratorSales operations leadSales managerNew owners
Routing, sequences, notificationsMarketing operationsMarketing operations leadSales managerSales team
Integrations and accessCRM administratorSales operations leadIT or securityMarketing operations

The steps

  1. List everything the person owns or appears in

    Filter every object by owner: contacts, companies, deals, tasks, and anything else the CRM lets someone own. Then look beyond ownership: routing rules and round-robin groups that name them, sequences and templates that use their name or reply address, workflows that send alerts or notifications to them, reports and dashboards they subscribe to or own, and integrations authorised under their user. Record the list in one place. It is the input to every later step and the checklist for the final one.

  2. Decide new owners by rule, not by inbox

    Apply the owner rules the team already uses. Records on accounts someone else owns go to that person. The rest follow territory or segment, as they would if they arrived today. Do not send everything to whoever has the most capacity that week, or to the manager by default: both leave records with owners who did not choose them and will not keep them. Where the leaver's role is being replaced, the replacement inherits the territory, not a bulk dump. Write the decision down beside the list.

  3. Reassign open deals first, with a handover note

    Open deals carry the most value and the most context, so move them before anything else, one by one. For each, add a note: where the deal stands, who the contacts are, what was promised and the next step with a date. Ask the leaver to write the notes while they are still there; if they have gone, the sales manager reviews each deal's history. Check renewal dates on customer deals and flag any that fall soon. The new owner should contact each account to introduce themselves rather than let the customer discover the change.

  4. Reassign contacts and companies by account and territory

    Move company records first, then their contacts, so contacts follow their account owner. Leave the lifecycle stage and source fields untouched: reassignment changes the owner, not the history. Watch for workflows that trigger on owner changes, such as an introduction email or an assignment alert, and decide whether a bulk reassignment should fire them; for a large move it usually should not. Where a contact is not linked to a company record, decide its owner by territory rather than leaving it with the leaver.

  5. Move open tasks and overdue follow-ups

    Reassign open tasks to the new owner of the record they belong to, and review overdue tasks rather than moving them blindly: some are obsolete, some are urgent. A follow-up the leaver promised a customer is a commitment the business made, and the new owner should keep it or explain the delay.

  6. Take the person out of routing and round-robin groups

    Remove the leaver from every assignment rule and round-robin group, and name who receives what they used to. Then send a test lead through each affected route, as the lead routing QA checklist describes, and confirm it reaches a current person with a task and a notification. This step protects Lead Response Time for new enquiries, which is the cost most handovers miss, because Lead Routing keeps working perfectly while sending leads to someone who has gone.

  7. Change sequences and emails sent in their name

    Find every automated email, sequence and template that uses the leaver's name, signature or reply address. Where the sender is taken from the record owner, reassigning the records fixes it, but check a sample. Where the name is written into the template, edit it. Make sure replies to emails already sent are forwarded to a monitored inbox for a period, so a customer answering an old message reaches someone.

  8. Repoint alerts, reports and workflow notifications

    Workflows that notify a named person, scheduled reports sent to the leaver and dashboards they owned all need a new recipient or owner. Alerts on owned records should follow the owner field rather than a fixed name, as the guide to sales alerts from marketing activity recommends, so this step also fixes alerts that were built the other way. Update the automation inventory with the new owners, as the governance guide requires. Rows in the automation inventory that still name the leaver as owner or deputy are the ones to change.

  9. Hand over integrations and remove access

    The fundamentals guide asks integrations to authenticate as their own named users so a departure does not break them. Where one was authorised under the leaver's account, reconnect it under an integration user or a long-term owner before their access goes, and check that data still flows. Then remove their sign-in, their API keys and any access to connected tools. The agency offboarding checklist covers the same access questions for an agency, and the order is the same: hand over, then remove.

  10. Check a week later for anything still pointing at them

    Run the first step's filters again. Look for records, tasks or deals still owned by the leaver, leads created since they left that were assigned to them, emails sent in their name, and notifications that bounced. Fix what turns up, then record the handover in the change log, as the measurement change log does for analytics changes, so a dip in follow-up or reporting in that territory can be traced to its cause.

An insurance broker's handover (illustrative)

Illustrative example — not a real result

Grondavik Insurance Brokers hands over an account executive's book

Grondavik Insurance Brokers, an invented commercial insurance broker, learns that an account executive is leaving with four weeks' notice. The CRM administrator's list finds 214 companies, 530 contacts, 37 open deals (22 of them renewals within the next quarter), 61 open tasks of which 14 are overdue, a slot in the round-robin group for new small-business enquiries, and a nurture email for new prospects signed with her name. The sales manager applies the territory rules: 160 companies go to the account executive taking over her region and 54 to colleagues who already own related accounts. In her last week she writes a handover note on every open deal; 6 renewals have no next step and are scheduled at once. Removing her from the round-robin group and sending a test lead shows that 9 enquiries had already gone to her that month without a reply; they are reassigned the same day. The nurture email is re-signed from the team. A week after she leaves, the check finds 3 contacts created from an event list still assigned to her, and nothing else.

Common mistakes

  • Deactivating the user first. Workflows, routing and integrations that point at the user can break when it disappears. List and move first, then remove access.
  • Moving everything to one person. Bulk reassignment to a replacement or a manager ignores the owner rules and leaves records with the wrong owner for years.
  • Contacts before deals. Deals carry the context; move them first, with a note.
  • Forgetting round-robin groups. New leads keep arriving in the leaver's slot and nobody answers them.
  • Leaving their name on automated emails. Customers hear from someone who has gone, and replies vanish.
  • Firing introduction workflows on a bulk move. Hundreds of contacts receive an assignment email at once.
  • Integrations under a personal account. The connection stops the day their access is removed.
  • No check a week later. Something is always still pointing at them.

Frequently asked questions

Should the leaver's user account be deactivated straight away?

Their sign-in access should be removed when they leave, as with any system holding customer data. Deactivating the user record itself is better left until their records, routing slots, workflows and integrations have been moved, because anything still pointing at the user can stop or misbehave when it disappears. Where the two cannot be separated, list everything in the first step before anything is switched off, so nothing is found only once it breaks.

Should a leaver's contacts all go to their replacement?

Only if the replacement takes over the same territory or accounts. Owner rules in most teams assign by account, territory or segment, and reassignment should follow the same rules rather than moving everything to one inbox. Contacts on accounts another person already owns go to that person; the rest follow the territory. A bulk move to one replacement is quick, but it leaves records with the wrong owner for years.

What should happen to automated emails sent in the leaver's name?

They should change before the person leaves, or on the day. Automated first-touch emails, nurture steps and sequences that use the owner's name and reply address will otherwise keep going out under the name of someone who no longer works there, and replies will go to an inbox nobody reads. Where the sender is taken from the record owner, reassigning the record fixes it; where the name is written into a template, the template has to be edited.

Terms used on this page

Frameworks

Where this page is used

Also related

Related