TL;DR
- In some CRMs, deactivating a user leaves that user as the owner of their records.
- A merge can move a customer to a former employee if that record's owner wins.
- Reassign records owned by former employees before merging their duplicates.
- Owner rules in a merge should keep inactive or placeholder owners from winning.
- Dedupely lets you set rules for which owner wins and preview each merge before it runs.
When a rep leaves, their records usually stay behind. The accounts, contacts and deals still carry their name, and nobody has time to reassign everything in the last week.
Months later, a cleanup finds duplicates. One record belongs to an active rep who talks to the customer every week. The other belongs to someone who left, and it may be the one that survives the merge.
In this post, you'll see how former employees end up owning duplicates and why merging them is risky. You'll also see what to reassign first, how to set owner rules for the merge and how to keep it from happening again.
How former employees end up owning duplicates
Deactivated users keep their records
In some CRMs, deactivating a user doesn't move their records. HubSpot's help page says a deactivated user "will remain assigned to their records." Salesforce's admin blog says "Deactivation does not change ownership" of a user's records.
Removing a user can leave a placeholder instead. In HubSpot, "Deactivated/Removed" plus the user's email appears as the owner of their contacts, companies, deals and tickets.
Colleagues create the record again
When a customer calls and their record sits under a former rep, a colleague may not find it or may not feel it's theirs. Creating a new record is the quickest way to log the call.
Routing can do the same. A new form fill goes to an active rep, while the original record still sits with the person who left. Our post on how lead routing and ownership rules create duplicates covers that side.
Placeholder owners hide the problem
Some teams move records from people who left to a generic owner, such as an admin or integration user. That clears the name, but it doesn't give the customer a real owner, and the placeholder can still win a merge.
Why merging these duplicates is risky
A merged record keeps one owner. If the rule keeps the oldest record's owner, the former employee's record can win, since it was often created first.
The deals, tasks and history from the active rep's record then move to a record owned by someone who left. The rep loses sight of their customer, reports credit the wrong person, and follow-ups go nowhere.
Ownership disputes between two active reps are a separate problem, which we cover in duplicate records from a sales manager's point of view.
Reassign before you merge
The safest order is to fix ownership first and merge second. Once every record has an active owner, the merge only has to choose between people who still work there.
List the owners who left
Compare the CRM's users with your current team. Look for deactivated users, removed users and generic owners such as an admin, an import user or "Unassigned".
Decide who gets the records
Ownership is a sales decision, and the answer is case by case. Common choices are the territory owner, the account manager or the rep who replaced the person who left. Agree on it with sales leadership before you change anything.
Reassign, then look for duplicates
After reassigning, run your duplicate searches again. Some sets that looked like ownership conflicts now share one owner, and others need the usual ownership rule for active reps.
Set owner rules for the merge
Reassigning everything first isn't always possible, especially in a large CRM. When some former owners remain, the merge needs a rule that keeps them from winning.
Write the rule per object, and preview a few sets with mixed owners before merging in bulk.
| Owners in the duplicate set | What to do |
|---|---|
| Both active | Follow your ownership rule, such as the rep with the most recent activity |
| One active, one who left | The active owner wins |
| One active, one placeholder | The active owner wins, and the placeholder never does |
| Both left | Reassign first, then merge |
| Owner is part of a commission or territory dispute | Send the set to review |
Some teams write this as a rule that placeholder owners always lose. If the other record's owner is a real person, that person keeps the customer.
Keep it from happening again
Add a step to your offboarding process: reassign a person's records before or on their last day. Then check for duplicates created around each departure, when colleagues may create new records.
A regular check of records owned by people who left is part of our CRM record maintenance checklist.
How Dedupely keeps former employees from winning a merge
In Dedupely, filter searches by owner and choose rules that favor the authorized active owner over an inactive or placeholder owner. Preview the result before merging and test the supported activities and associations. Reassignment remains a business decision: confirm who owns the relationship before running a bulk rule.
Give every customer an owner who still works there
Records owned by former employees are easy to forget until a merge puts them back in charge of a customer. Deactivated users can keep their records, and placeholder owners can win a merge just as easily.
Reassigning before you merge, and setting a rule so inactive or placeholder owners lose, keeps customers with the people who serve them. An offboarding step stops the next departure from starting the cycle again.
References: HubSpot: Deactivate and remove users; Salesforce: Users May Come and Go, But Their Records Must Live On.
Frequently asked questions
What happens to CRM records when an employee leaves?
It depends on the CRM, but often nothing happens on its own. In HubSpot and Salesforce, deactivating a user leaves them as the owner of their records until someone reassigns them. Removing a HubSpot user shows a "Deactivated/Removed" placeholder as the owner, which reassigning during offboarding avoids.
Should I reassign records before merging duplicates?
Yes, where you can: once every record has an active owner, the merge only chooses between people who still work there. If some can't be reassigned first, set a merge rule so inactive or placeholder owners never win. Preview sets with mixed owners before merging.
Which owner is kept when you merge duplicate records?
It depends on the CRM and your merge settings. Often the primary record's owner is kept, and the primary record may be the oldest one. That can hand a customer to a former employee, so decide the owner rule before merging and check it in a preview.
How do I find records owned by inactive users?
Compare the list of CRM users with your current team, then filter records by owner for each person who left. Include generic owners such as admin, import or integration users. Many CRMs let you filter or report on records by owner, which gives you a list to reassign.
What is a placeholder owner in a CRM?
A placeholder owner is a generic user that holds records without a real person behind them, such as an admin, import or integration user. Some CRMs also show a removed user as a placeholder. These owners should never win a merge, since nobody follows up on their customers.
Or sign up with Google
HubSpot Marketplace 
