Disabling a departing employee's login does not automatically give somebody else responsibility for their work. Account access and record ownership need coordinated but separate decisions, especially when tasks, approvals and integrations refer to that user.
Related service: CRM, ERP and web application development- 01Inventory records and unfinished commitments.
- 02Choose new owners by workflow.
- 03Preview related changes.
- 04Revoke access and execute the transfer.
- 05Reconcile exceptions and verify follow-up.
SECTION 01
Include work that is not on the account record
List open opportunities, tasks, appointments, approval requests, shared views and scheduled reports. Some records may be owned by a team rather than an individual. Others may use the employee's credentials to connect an external system. Treat those connections as operating dependencies, not merely contact fields.
Decide which related records move with the account and which remain with another responsible person. Microsoft's relationship documentation shows why cascading assignment rules matter: transferring a parent record can affect its children. Review your actual platform behavior rather than assuming every task follows, or that every historical activity should be reassigned.
SECTION 02
Illustrative example: an account has several active specialists
Suppose an account manager leaves while a technical specialist is handling an open implementation question. The new account manager receives commercial follow-up and outstanding customer promises. The technical task remains with its specialist. This is an illustrative transfer plan, not a client case study.
Completed notes retain their original author. Upcoming reminders should go to the new responsible person rather than the disabled account. A shared report owned by the employee may need a team owner, while a personal draft can remain excluded. The transfer preview should expose these differences before a bulk action changes hundreds of relationships.
SECTION 03
Verify both the old and new access paths
Start with a dry run and reconcile counts by record type. Keep an exception queue for records without an eligible replacement. Avoid a blanket transfer to an administrator simply to make the report empty; operational ownership needs someone who will actually act.
Test that the old session loses access as intended, that the replacement sees the relevant work and that unrelated private records remain restricted. Verify approval queues, saved links and scheduled integrations after the change. OWASP's authorization guidance supports reviewing the permission side of this operation. Your organization's employment and retention decisions remain separate; the software should implement the approved policy rather than invent one.
SECTION 04
Frequently asked questions
Should every record be assigned to the replacement?
No. Some tasks belong to specialists or teams, and historical authorship should remain accurate. Define which active responsibilities transfer.
Is disabling the account enough?
It addresses one access path, not ownership, scheduled jobs or external credentials. Review those dependencies and confirm the operational handoff.
How do we know the transfer is complete?
Reconcile active records and exceptions, test the replacement's access and confirm that pending reminders, approvals and integrations have an accountable owner.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Table relationships and their behaviorMicrosoft Learn
- Authorization guidanceOWASP Foundation
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy