Salesforce orgs don’t break all at once. They accumulate: a field added for one project, an automation built by an admin who’s since moved on, a report nobody remembers creating. Over time, that buildup makes the system slower to change, harder to trust, and riskier to maintain.
Here are 15 signs your Salesforce org, or your Litify org, which runs on Salesforce, is due for a health check.
Automation
1. You still rely on Workflow Rules or Process Builder
Salesforce has retired both tools in favor of Flow. Automation built on them should be migrated to Flow so it stays supported.
2. Automations fire in unpredictable ways
When several automations act on the same record, changes can trigger each other in surprising ways. If nobody can explain what happens when a record is saved, it’s time to map it out.
3. Nobody knows what some automations do
Undocumented automation built by people who’ve left is a common source of mystery errors.
Data and configuration
4. Many fields are empty or unused
Unused fields clutter layouts, confuse users, and make reporting harder.
5. Duplicate records are common
Duplicate contacts and accounts undermine reporting and create extra work.
6. Page layouts are crowded
If users scroll past dozens of fields to find the few they need, layouts should be simplified by role.
7. Reports and dashboards are out of control
Hundreds of unused or near-duplicate reports make it hard to find the numbers that matter.
8. You’re approaching storage limits
Data and file storage limits can lead to unexpected costs. Check your usage and plan for archiving.
Security and access
9. Your Security Health Check score is low
Salesforce includes a Security Health Check in Setup that compares your settings to recommended standards. Review it and fix high-risk items.
10. Too many users have too much access
Broad administrator access and overlapping profiles and permission sets make access hard to manage. Aim for least privilege.
11. Former employees still have active accounts
Deactivate users promptly, and review licenses you’re paying for but not using.
12. Multi-factor authentication isn’t enforced for everyone
Salesforce requires multi-factor authentication for user logins. Make sure it’s enforced consistently.
Code and integrations
13. Deployments are slow or risky
If every change feels risky, it’s time to improve how changes are tested and released, including your use of sandboxes. See Salesforce sandbox types explained.
14. Integrations fail quietly
Integrations that break without alerting anyone leave data out of sync. Make sure failures are logged and someone is notified.
15. Custom code has thin test coverage
Salesforce requires test coverage to deploy Apex code, but meeting the minimum isn’t the same as testing well. Weak tests make every change riskier.
What to do next
- Start with security, including access, inactive users, and multi-factor authentication.
- Map and modernize automation, especially anything on retired tools.
- Clean up fields, layouts, and reports with input from the people who use them.
- Put a regular review on the calendar, so problems don’t build up again.
Want a second opinion? Litify firms can book a free Litify org review, and our admins for hire can take on ongoing maintenance.
Frequently asked questions
What is a Salesforce org health check?
A health check is a review of a Salesforce org’s automation, data, configuration, security, and integrations to find problems and risks that have built up over time.
Are Workflow Rules and Process Builder still supported?
Salesforce has retired Workflow Rules and Process Builder in favor of Flow, so automation built on them should be migrated to Flow.
How often should we review our Salesforce org?
Many organizations benefit from a review at least once a year, and after major changes such as a new implementation phase, a merger, or turnover on the admin team.
Does this apply to Litify orgs?
Yes. Litify runs on Salesforce, so the same health check areas apply to Litify orgs.
