Your Salesforce Admin Just Left. Here’s What to Do in the First 30 Days.
When your Salesforce admin left, it usually started with an email like this one.
“I’ve accepted another opportunity” — or some version of it. And somewhere between reading that message and the end-of-day, the realization sets in that the person who knew where everything lived in your Salesforce org, why certain automations exist, and what that one flow does that nobody else has ever looked at — is leaving.
Most businesses don’t have a plan for this. And that’s fine, until it isn’t.
The first thirty days after your Salesforce admin left are the window that determines how much damage gets done. Move quickly on the right things and you’ll barely notice the gap. Miss the first few weeks and you’ll spend the next six months untangling problems that didn’t have to happen.
Here’s exactly what to do — in order.
Week One — Secure the Org Before Anything Else
The moment you know your admin is leaving, security is the first priority. Not because of bad intent — most departing admins are professional and helpful through the transition — but because access that doesn’t get revoked on day one tends to stay open indefinitely.
Day 1 — Change critical credentials:
- Reset the System Administrator password
- Rotate any API keys or connected app credentials the admin personally managed
- Check for any personal email addresses being used as login aliases
- Review Single Sign-On settings if the admin configured SSO through their personal accounts
Day 2–3 — Audit active users and profiles:
Run a user report filtered by active status and administrator-level profiles. If the departing admin has a System Administrator profile, freeze the account immediately — don’t wait for their final day. Freezing is safer than deactivating at this stage because it preserves their record ownership without locking you out of data.
Day 4–5 — Document what you can while they’re still there:
If the admin is working out a notice period, use that time deliberately. Ask them to record a Loom walkthrough of anything they consider non-obvious — custom flows, integrations they built, third-party apps they manage, and anything that would break if nobody touched it for three months.
Don’t assume they’ve documented anything. Most haven’t. This is the one window you have to get it directly from them.
Week Two — Map What You Actually Have
Once the immediate security concerns are handled, the next priority is understanding the full scope of what your Salesforce admin left behind — and what state it’s in.
This is where most businesses discover things they didn’t know existed.
Run Salesforce Optimizer. It’s a free built-in tool that generates a report covering unused fields, redundant layouts, legacy automation, and performance issues. It won’t tell you everything, but it gives you a fast picture of how complex the org actually is.
List every active automation:
| Automation Type | Where to Find It | Risk if Untouched |
| Flows | Setup → Flows | High — can trigger on every record save |
| Apex Triggers | Setup → Apex Triggers | High — runs custom code on data events |
| Workflow Rules | Setup → Workflow Rules | Medium — legacy but still active |
| Process Builder | Setup → Process Automation | Medium — often conflicts with Flows |
| Scheduled Jobs | Setup → Scheduled Jobs | High — runs on a timer nobody may know about |
Any automation you can’t explain is a risk. It’s not something you need to fix in week two — but you need to know it exists.
Map your integrations. Check Setup → Connected Apps and Setup → Named Credentials. Every integration your Salesforce admin configured — to HubSpot, your ERP, your support platform, your billing system — needs to be documented with the owner, the credentials used, and what breaks if it stops working.
Week Three — Stabilize Operations
By week three, you have a clearer picture of what you’re working with. Now the goal is making sure nothing breaks while you figure out the longer-term plan.
Assign a temporary admin — carefully. Someone needs to have administrative access, but “give it to the most technical person on the team” isn’t a good strategy if that person doesn’t understand Salesforce’s sharing model or automation architecture. Giving someone admin access without the right background is how accidental data loss happens.
If nobody on the team has Salesforce administration experience, this is the point at which bringing in external support temporarily is the right call — not because you can’t manage, but because the cost of a mistake at the admin level is significantly higher than the cost of a few hours of outside help.
Check your data quality. Once your Salesforce admin left, data quality problems that were being quietly managed start to surface. Duplicate records accumulate faster. Required fields get bypassed. Records get assigned to deactivated users. A quick data quality review in week three catches these before they compound.
Don’t make big changes yet. The instinct after losing an admin is often to clean everything up immediately — delete unused fields, rebuild the pipeline stages, restructure the reporting. Resist this. Week three isn’t the time. You don’t have enough context yet, and changes made without understanding why things were built a certain way have a high chance of breaking something downstream.
Week Four — Decide Your Longer-Term Plan
By the end of week four, you need to have made a decision about what comes next. Not necessarily implemented it — but decided.
There are three realistic options, and which one makes sense depends on how complex your Salesforce org is, how frequently it needs to change, and what your budget looks like:
Option 1 — Hire a replacement admin internally
This makes sense when your org is actively evolving — new automations being built regularly, frequent configuration changes, ongoing integration work. A full-time internal admin has the context depth that’s hard to replicate fractionally.
The downside: hiring takes time, and you’ll likely be three to four months into a search before someone is onboarded and productive. That’s a long gap to manage.
Option 2 — Managed admin services
A Salesforce partner provides ongoing admin capacity on a retainer basis — typically a set number of hours per month covering configuration changes, user management, data quality monitoring, and ad hoc support.
This is the right fit for most mid-market businesses whose Salesforce needs are real but don’t justify a full-time hire. The key is finding a partner who provides senior-level oversight, not a junior admin working from a ticket queue.
Option 3 — Internal ownership with external support for projects
A team member takes day-to-day ownership of simple admin tasks — user management, password resets, basic report updates — while a consulting partner handles anything architectural. This works when the org is relatively stable and the configuration isn’t changing dramatically quarter to quarter.
The 30-Day Checklist
Use this as your reference through the transition:
| Timeline | Action | Priority |
| Day 1 | Reset System Admin password and freeze departing admin account | Critical |
| Day 1–2 | Rotate API keys and connected app credentials | Critical |
| Day 2–3 | Audit active users and administrator profiles | Critical |
| Day 3–5 | Get knowledge transfer from departing admin — record walkthroughs | High |
| Week 2 | Run Salesforce Optimizer and review the full report | High |
| Week 2 | List all active Flows, Apex Triggers, Workflow Rules, and Scheduled Jobs | High |
| Week 2 | Map all active integrations and document credentials and owners | High |
| Week 3 | Assign temporary admin access — carefully | High |
| Week 3 | Run a basic data quality check across key objects | Medium |
| Week 3 | Freeze changes — no major configuration work yet | Medium |
| Week 4 | Decide on long-term admin coverage model | Medium |
| Week 4 | Brief incoming resource on org complexity and known risks | Medium |
What Usually Goes Wrong in This Window
Having seen what happens after a Salesforce admin left across many B2B organizations, the same mistakes show up consistently:
Deactivating instead of freezing the departing admin account. Deactivation reassigns record ownership and can trigger automation you didn’t know existed. Freeze first, deactivate later once you’ve confirmed nothing broke.
Assuming the departing admin documented things. Most didn’t. Even well-intentioned admins rarely have documentation that would let someone else maintain their org without a learning curve. Don’t assume — verify.
Making changes too quickly. The first instinct is to clean up. The second instinct is to rebuild. Both are wrong in week one. Understand first, then change.
Giving admin access to the wrong person. System Administrator is one of the most powerful access levels in any business system. Giving it to someone without Salesforce experience to “just handle things temporarily” creates more risk than it solves.
Waiting too long to get outside help. There’s a version of this where the business waits three months, things quietly degrade, and by the time someone looks closely the org has accumulated problems that take twice as long to fix. If nobody on the team has the Salesforce background to manage this transition confidently, getting external support in week two is significantly cheaper than fixing the consequences of week eight.
Final Thoughts
When your Salesforce admin left, it’s disruptive — but it doesn’t have to be a crisis.The businesses that navigate this well move fast on security, slow on changes, and honest about the gap between what they know and what they need to know.
The first thirty days set the trajectory. Get the access controls right, understand what you’re working with, stabilize operations, and make a clear-eyed decision about long-term coverage before the window closes.
If you’re currently working through this and want an independent view of where your org actually stands — what’s documented, what isn’t, what’s at risk, and what the right next step is — a Salesforce health check is usually the most useful place to start. It gives you a clear picture without the guesswork.
For businesses still working out whether they need a full-time admin or something more flexible, this breakdown of when a business actually needs a Salesforce admin covers the decision honestly.
And if you need admin coverage while you figure out the longer-term plan, Salesforce support services can bridge the gap without committing to a hire before you’re ready.
Amroar works with B2B businesses at exactly this stage — coming in after a transition, auditing what’s there, and either stabilizing the org or taking over ongoing admin coverage so nothing falls through the cracks while the business figures out what comes next.
Book a Free Salesforce Org Review →
Comments are closed