5 Salesforce Org Health Checks Every Admin Should Run
Most Salesforce orgs accumulate technical debt quietly. Here are five checks that surface real problems before they become incidents.
Most Salesforce orgs don’t fail dramatically — they degrade quietly. A flow that worked fine at 500 records starts timing out at 50,000. A permission set that made sense two years ago now grants access it shouldn’t. An automation nobody remembers writing fires on every update and slows your page loads.
These five checks take an afternoon. They surface the issues that silently cost your team time and trust.
1. Governor Limit Exposure Audit
Pull your Apex Execution Logs from Setup → Apex Jobs and look for anything regularly using more than 50% of the CPU or SOQL governor limits. These aren’t failures yet — but they’re one data load away from being one.
What to look for:
- Automations triggered on high-volume objects (cases, orders, log records)
- SOQL queries inside loops (the classic mistake — one query per record instead of one query for all records)
- Synchronous callouts blocking the transaction
Quick win: Enable Debug Logs on your integration user for a busy hour and scan for Maximum CPU time warnings. If you see them, you have a ticking clock.
2. Security Model Review
Salesforce’s security model is powerful but easy to over-grant. Run the Permission Set Analyzer (available in the Security Center if you have it, or manually via SOQL) and check:
- Any profile or permission set with “Modify All Data” or “View All Data” that isn’t a system integration user
- Users with Edit access to fields they only need to read
- Public groups with access to sensitive record types
A quick SOQL check to run in Developer Console:
SELECT Name, PermissionsModifyAllData, PermissionsViewAllData
FROM PermissionSet
WHERE PermissionsModifyAllData = true OR PermissionsViewAllData = true
If non-integration users appear here, dig in. Least-privilege isn’t just a best practice — it’s your audit defence.
3. Inactive Automation Inventory
Every Salesforce org has automations that were “temporarily” deactivated and then forgotten. They don’t do harm sitting there, but they create confusion — and sometimes get re-activated accidentally during deployments.
Run this in Developer Console:
SELECT DeveloperName, ProcessType, Status, LastModifiedDate
FROM Flow
WHERE Status = 'Obsolete' OR Status = 'InvalidDraft'
ORDER BY LastModifiedDate ASC
Delete what’s truly dead. For anything you’re unsure about: add a description, note who owns it, and set a review date. Undocumented automations are a support ticket waiting to happen.
4. Data Quality Spot Check
Bad data is the silent killer of Salesforce ROI. A quick sample audit:
- Leads with no email and no phone — what’s the point of the record?
- Accounts with no associated Contacts — orphaned records from imports
- Opportunities stuck in the same stage for 90+ days — pipeline illusion
- Duplicate detection rate — run the Duplicate Jobs report and see what percentage of new records are flagged
You don’t need to fix everything today. But knowing the shape of your data quality problem tells you where to invest in validation rules, duplicate matching, or a cleanup project.
5. Release Management & Change Tracking
This one is procedural, not technical — but it’s the check most orgs skip. Ask yourself:
- Do you have a change log (even a simple spreadsheet) of what was deployed in the last 6 months?
- Are your flows and apex classes deployed via CI/CD or change sets — or direct production edits?
- When something breaks, can you tell within 10 minutes what changed and who changed it?
If the answer to any of these is “no,” you’re operating without a safety net. The first step is simply requiring that every change to production goes through a sandbox first, with a ticket or Slack message noting what was done and why.
Making This a Routine
None of these checks are one-and-done. The orgs that stay healthy are the ones where someone runs through this list (or a version of it) quarterly. Put it in your calendar. Share the output with stakeholders. It’s the difference between managing your org and being managed by it.
Need a professional org health review? We offer structured Salesforce audits — get in touch to find out what’s in yours.