It is the most common revenue-operations emergency we see: a resignation email, a two-week notice period, and an org that nobody else fully understands. Salesforce administration knowledge lives in one head and that head is leaving.
Here is the playbook we run with teams in exactly this situation, in the order it should be run. Days matter: the highest-risk failures happen in the first week after access is lost.
Day 1: secure and triage before the goodbyes
Do not wait for the last day. On the day the resignation lands, inventory what your admin holds: the System Administrator profile, integration credentials, ownership of scheduled jobs, flow error emails, and vendor portal logins such as AppExchange.
Start the knowledge capture while they are still motivated to help. A 90-minute exit interview over a shared screen covers most of the undocumented reality: what the nightly jobs do, which reports the board actually reads, which integrations are fragile.
Plan credential rotation for the last day. Connected apps, API keys, SSO bindings, email service accounts. Deactivate the user record last after ownership of everything scheduled has been transferred.
Week 1: stabilise the org
Reassign ownership of everything scheduled. Nightly data loads, scheduled jobs, flow error notifications, dashboard subscriptions. Orphaned schedules fail silently usually during month-end.
Freeze non-critical changes. Declare a change freeze for two weeks. Orgs break more often from an untested "small favour" during a handover than from anything else.
Triage the open-items list. Sort everything in flight into revenue-blocking (fix now), important (schedule) and nice-to-have (park). Most teams discover the list is 10/30/60 which is why the backlog panic is usually smaller than it feels.
Check the release calendar. Salesforce pushes three seasonal releases a year. Know the next one, and whether any newly enabled feature collides with your configuration.
Weeks 2-4: decide the bridge, not the replacement
The instinct is to hire a replacement admin immediately. That is the right call for some companies but make it deliberately, not in a panic.
If Salesforce is operationally critical and change demand is high: cover the gap with a Salesforce support retainer or emergency admin cover while you recruit. The queue stays clear, the org stays safe, and you can hire without pressure.
If your needs are genuinely light: a small managed-services retainer may be the permanent answer. A full-time senior admin costs a multiple of retainer coverage and a single hire recreates the same single point of failure you just lived through.
If you will hire: use the covered period to write a real job description from the exit interview, and to document the org so your new admin starts productive instead of starting as an archaeologist.
The handover document nobody wrote write it now
Every team promises itself it will document the org "after the project ships". Use the departure as the forcing function. Minimum viable documentation for the next person internal or us:
Integration inventory what connects to what, who owns the credentials, and how each integration fails.
Automation map every scheduled job and major flow, what it does, and who notices when it breaks.
Data model decisions key objects, the reasoning behind unusual configurations, known technical debt.
Reporting register which dashboards matter to whom, and what sits behind each number.
Access matrix who holds which profile, permission set and licence, and why.
Warning signs you inherited a bigger problem
When we take over an org mid-departure, certain findings recur. If you see these, the situation is bigger than a staffing gap: storage or licence counts approaching hard limits nobody was tracking; flow error emails still routed to the departed admin's mailbox; integrations authenticating as a personal user; sandboxes months out of date, or none at all; and a red security health score with wide-open sharing rules.
How we can bridge it
This is exactly what our support retainers and Salesforce managed services exist for: emergency admin cover with a same-week start, named SLAs, and a documented exit handover whenever you are ready to switch back to internal, or to a full managed service. Book a discovery call and we will scope a bridge in one conversation.