DEV Community

Demo
Demo

Posted on • Originally published at orgdoc.dev

How to set up Salesforce change management for solo admins

#salesforce #crm #admin #governance

As a solo Salesforce admin who’s navigated change management in healthcare, manufacturing, and SaaS environments, I’ve seen too many orgs implode because one person tried to juggle deployments, documentation, and firefighting alone. You don’t need a team of 10—just a disciplined process. Here’s how to build one without drowning in complexity.

Document Everything (Even the "Obvious" Stuff)

Stop relying on memory. I once inherited a healthcare org where a critical patient data sync failed because a solo admin forgot to update a custom field’s API name after renaming it. Documentation isn’t optional—it’s your safety net. Create a single master doc (Google Docs works for solo admins) with:

  • Field/API names (e.g., "Account.Payer_Type__c" not just "Payer Type")

  • Permission set assignments (e.g., "Billing Team" gets "Edit_Patient_Records" permission)

  • Process IDs (e.g., "Case.001 → Case.002" for case type changes)

When a manufacturing client needed to add a new product line, I used this doc to trace every field and validation rule affected. No guesswork, no rollback chaos.

Version Control Is Non-Negotiable

Don’t store metadata in your head or scattered emails. Set up a free GitHub repo (yes, free) for your org’s metadata. For example, when a SaaS client requested a new lead scoring field, I:

  • Created a branch: feature/lead-scoring-v2

  • Pushed the field and validation rule XML to the branch

  • Tagged the commit: v2.1.3-deploy-2023-10-05

This let me revert instantly when a sales team accidentally disabled the scoring rule during a deployment. No "I think I remember what I changed" panic.

Build a 5-Item Deployment Checklist

Enterprise teams over-engineer checklists. For solo admins, keep it to five critical items:

  • Test in Sandbox: Run SELECT Id FROM Lead WHERE Score__c > 50 in sandbox to verify new logic

Check Dependencies: Use

SELECT Id, ParentId FROM FlowDefinition WHERE ApiName LIKE '%LeadScore%'
Enter fullscreen mode Exit fullscreen mode

to find flows using a field

  • Update Documentation: Link the commit hash to your master doc

  • Notify Stakeholders: Email sales ops: "Lead scoring rules updated. Test in sandbox by 5 PM."

  • Monitor Post-Deploy: Check SELECT Id, Status FROM AsyncApexJob WHERE JobType = 'Flow' for failures

I used this checklist for a retail client’s Black Friday campaign. It caught a missing permission set for the new promo code field before launch.

Monitor Like a Solo Pro

Post-deployment, you can’t wait for users to report issues. Set up two quick checks:

Run this SOQL to spot broken flows:

SELECT Id, Status, LastModifiedDate FROM FlowDefinition WHERE Status != 'Active'
Enter fullscreen mode Exit fullscreen mode

Check error logs with:

SELECT Id, Exception FROM AsyncApexJob WHERE CreatedDate = TODAY
Enter fullscreen mode Exit fullscreen mode

At a healthcare client, this caught a failed patient data sync during a patch deployment—before 200 users hit the error screen.

Change management isn’t about perfection. It’s about reducing the "oh no" moments from 100% to 5%. Start with documenting field names and a GitHub repo. Do that consistently for 30 days, and you’ll spend 50% less time firefighting. Your future self (and your boss) will thank you.

Want to see how your org stacks up? Run a free health scan to spot hidden risks in your change process, deployment history, and documentation gaps. Get your free Salesforce health scan here.

📚 Recommended Resource: Salesforce for Dummies — great for anyone learning Salesforce.

📚 Recommended Resource: The Phoenix Project — great for anyone IT management.

Need a second opinion on your Salesforce org? Request a diagnostic.

Top comments (0)