Who owns the records of people who left?
The short answer: The departed person does, until you move the records. Deactivating a Salesforce user doesn’t reassign what they own. To find those records, report on each object with the owner’s Active field set to false. To reassign them, use Mass Transfer Records for accounts, leads and custom objects, and Data Loader for opportunities, cases and activities.
Say a rep leaves on Friday. IT switches off the account, someone ticks the box on the user record, and the leaver email goes round. On Monday an automation that updates opportunities starts failing on 40 of them, a dashboard that “runs as” the rep comes back empty, and a lead routed to a queue last month is still sitting under a name nobody recognises.
None of this is a bug. It is what the platform documents. The gap is that nobody owns the follow-up.
What does Salesforce do when you deactivate a user?
It stops the person logging in and frees their license, and that is nearly all. According to Salesforce Help, the user stays in the list marked inactive, and records they own stay with them until you transfer ownership.
What else the Help pages say happens:
- Deactivated users lose access to records shared with them manually or through team membership, effective immediately. Users higher in the role hierarchy keep access until the shares are removed asynchronously.
- They are removed from other users’ default account and opportunity teams, but their own default teams aren’t removed.
- Files they own aren’t deleted, and the deactivated user remains the owner until an admin reassigns them.
- Chatter groups they own stay theirs until reassigned.
- Inactive users can still hold permission set assignments, so Salesforce suggests removing those afterward.
- Deactivating needs the Manage Internal Users permission.
Reassigning first is not required, but if a user owns more than 10,000 records of one object, Salesforce says to transfer them beforehand to avoid performance issues.
Why do records owned by inactive users matter?
Because things that run on ownership keep running on a name nobody answers to. Four places it bites.
Automation. Salesforce Help says “processes can’t update records that are owned by inactive users”, so a flow or process that edits those records fails until they have an active owner. There is an admin setup that lets users create and edit records with inactive owners. In Setup, User Interface holds the org-level checkbox, and a permission, Update Records with Inactive Owners, covers users. Treat it as a workaround, not a plan.
Reports and dashboards. Salesforce Help warns that Lightning dashboards owned by or running as a deactivated user may return unexpected results. Change the dashboard owner.
Sharing. Per Salesforce Help, the person loses access shared with them manually or through teams. Managers higher in the role hierarchy keep access until the shares are removed asynchronously, so check what the rest of the team can still see before you assume nothing changed.
Assignment. Records stuck on an old name don’t get follow-up, and some defaults block deactivation outright. Salesforce lists default owners for leads and cases, the default workflow user, the default lead creator, workflow email alert recipients, custom hierarchy field selections and Customer Portal administrators. Approvers must be removed from approval processes. If one of these blocks you, freeze the user to stop logins now and finish the cleanup before deactivating, because freezing doesn’t release the license.
How do you find records owned by inactive users?
Build a report on the object with a filter on the owner’s Active field. Salesforce Help describes this for leads: create a custom report type with Leads as the primary object, add the Lead Owner’s Active field through the layout editor, then filter “Lead Owner: Active equals False”.
The steps from Setup:
- Create, then Report Types, then New Custom Report Type, with the object as primary.
- Edit Layout, add fields related via lookup, and add the owner’s Active field.
- On the Reports tab, create a report from that type.
- Add the filter “Owner: Active equals False” (the label follows the object, such as Lead Owner).
- Group by owner, and save it in a shared folder.
Repeat for accounts, opportunities, cases and any custom object that matters. Salesforce documents the leads case, so read the same pattern across to the other objects as my adaptation. If you want a quick estimate first, open the Inactive Users list in Setup, then group your main objects by owner and look for those names. Count the result as a share of the total. It is number five in seven data quality numbers every admin should know.
How do you reassign records from an inactive user?
Use Mass Transfer Records for accounts, leads, service contracts and custom objects, a list view for small batches, and Data Loader for opportunities, cases and activities. Each has a documented scope.
| Method | What it covers | Documented limits |
|---|---|---|
| Mass Transfer Records (Setup) | Accounts, leads, service contracts, custom objects | Up to 250 records at a time |
| List view Change Owner | Leads in the Help example | A list view shows 2,000 records |
| Data Loader update on OwnerId | Opportunities, cases, activities, anything | You export, edit and reload the file |
Mass Transfer Records. Setup, Quick Find, Mass Transfer Records. For accounts it also moves contacts (business accounts only), attachments, notes, open activities, and open opportunities owned by the current owner. Closed opportunities and other users’ open opportunities are optional. For leads, open activities move, except when the lead goes to a queue. You need Transfer Record and Transfer Leads for accounts, and Transfer Record for custom objects.
One thing to know first. In Professional, Enterprise, Unlimited, Performance and Developer editions, transferring accounts removes access given by manual sharing, Apex managed sharing and sharing rules, then applies the new owner’s rules. As reported by Salesforce Ben, Winter ’27 adds a Keep Manual Shares When Transferring Records option under Sharing Settings, off by default and org-wide when on. Its status isn’t stated in that article, so check the release notes. We cover it in manual shares and owner changes.
List views. Salesforce Help describes selecting leads in a list view and choosing Change Owner. The new owner needs at least Read access on the object, and in Lightning the button may need adding to the list view button layout.
Data Loader. Salesforce Help says Mass Transfer can’t bulk-transfer opportunities, cases or activities. Export the records with their Owner ID, replace it with the new owner’s User ID, and run an Update. Check the success and error files afterward.
What goes in a leaver checklist?
Report first, resolve blockers, transfer, then deactivate. In that order, because the report disappears the moment ownership is gone.
- Run the owned-records report for each key object and save the export, with Ids.
- Check the blockers: default owners, approvals, workflow email alerts, hierarchy fields.
- Move shared-record dependencies: dashboards the person owns or runs as, folders, Chatter groups, files.
- Transfer records, with a note of who inherits what and why.
- Deactivate (Setup, Users, Edit, clear Active), or freeze if something still blocks you.
- Remove permission set assignments and handle default team memberships.
- Rerun the report. It should read zero.
What to do Monday:
1. Build the inactive-owner report for accounts and opportunities and run it. Write down the count.
2. Add “run the report, then transfer” to the leaver ticket, ahead of the deactivation step.
3. Ask who currently owns the dashboards and default assignments in your org.
Where we come in
The Data Health Check is our two-week fixed-scope audit, and records owned by inactive users is one of the checks it measures, with the records behind each figure. It reads and recommends. It doesn’t change a single record, so the transfers are yours, or ours as separate work. The 20-minute scorecard gets you a rough number first.
Questions people ask
Does deactivating a Salesforce user transfer their records?
No. Records they own stay with them until you transfer ownership, according to Salesforce Help. Transferring first isn’t required, but Salesforce recommends it when a user owns more than 10,000 records of one object, to avoid performance issues.
Can you edit a record owned by an inactive user?
Not by default in every case. Salesforce Help says processes can’t update records owned by inactive users. An admin can enable editing of accounts, opportunities and custom object records with inactive owners through the User Interface setting and a permission, but reassigning is the cleaner fix.
Is there a limit on Mass Transfer Records?
Salesforce Help says the tool handles up to 250 records at a time and points to Data Loader for larger transfers. It also covers only accounts, leads, service contracts and custom objects, so opportunities and cases need Data Loader or another route.
Sources
- Considerations for deactivating users: what deactivation does, 10,000-record guidance, processes, dashboards, files, teams.
- Deactivate users: steps, permission, blockers, freeze.
- Mass Transfer Records: supported objects, related records, permissions, sharing, 250-record limit.
- Create a report to display records owned by inactive users: custom report type and Owner Active filter.
- Transfer ownership of opportunities, cases and activities using Data Loader: steps and cautions.
- Change the owner or status of multiple leads at once: list view Change Owner, 2,000-record view, permissions.
- Enable the Create Audit Fields permission: org-level setting and permission for records with inactive owners (read via search excerpt).
- Top 12 Winter ’27 features for admins, as reported by Salesforce Ben: Keep Manual Shares When Transferring Records.