Salesforce can remain technically operational while becoming increasingly difficult for users and administrators to manage. Reports may no longer be trusted, automations may overlap, data may be duplicated, and teams may compensate with spreadsheets or manual work. A Salesforce Health Check provides a structured way to understand what is happening before committing to a major redesign.
What a Salesforce Health Check should accomplish
A useful Health Check should do more than produce a long list of technical observations. It should connect configuration findings to business impact and organize recommendations by urgency, value, effort, and dependency.
- Identify risks affecting security, data integrity, reliability, or user access.
- Document friction in sales, service, fundraising, program, or operational processes.
- Review automation for duplication, failure points, unnecessary complexity, and maintainability.
- Evaluate whether reports and dashboards support current leadership and operating needs.
- Separate immediate fixes from longer-term improvement opportunities.
Core areas to review
Configuration and data model
The review should examine how standard and custom objects, fields, record types, page layouts, validation rules, and relationships support the organization’s current operating model. Unused or confusing configuration should be identified without assuming that everything custom is unnecessary.
Security and access
Profiles, permission sets, roles, sharing rules, public groups, integration users, and administrative access should be reviewed for excessive access, inconsistent assignments, and maintainability.
Automation and integrations
Flows, legacy workflow rules, approval processes, scheduled jobs, email alerts, and integrations should be mapped to understand dependencies and potential conflicts. The goal is not simply to modernize automation, but to make it understandable and dependable.
Data quality and reporting
Duplicate records, incomplete fields, inconsistent values, ownership issues, and reporting gaps can undermine confidence in the system. A Health Check should distinguish between configuration problems and data-governance problems.
User experience and adoption
User interviews and targeted observation often reveal issues that technical analysis alone will miss. The review should identify where staff rely on workarounds, external files, or informal knowledge to complete routine tasks.
When an organization should consider a Health Check
A Health Check is particularly valuable when leadership is considering a new implementation partner, users report that Salesforce is difficult to use, reports are unreliable, multiple administrators have made changes over time, a major integration or migration is planned, or the organization needs a practical roadmap before approving a larger investment.
What the final deliverable should contain
The final deliverable should include an executive summary, current-state findings, risk and impact assessment, quick wins, prioritized recommendations, estimated effort ranges, dependencies, and a phased roadmap. The organization should be able to act on the findings whether it engages the assessor for follow-on work or uses another delivery partner.