2026-07-31 · FieldRat
Salesforce org health check: what it covers, and where field debt fits
Every org past its second admin carries invisible weight: fields nobody remembers, automation nobody owns, access nobody reviewed. A health check is how you see all of it at once — and field debt is almost always the highest-volume finding. Here's what a real one covers, how to get one free, and what to do with the field findings afterwards.
Quick answer: the five areas a real org health check covers
- Field & metadata debt — unused fields, dead automation, duplicate logic. Highest volume, slowest to fix.
- Access risk — dormant users holding licenses, over-broad permissions, guest-user write access.
- Silent failures — error emails routed to departed employees, leads flowing into empty queues, batch jobs failing nightly with nobody watching.
- Announced deadlines — Workflow Rules and Process Builder past end-of-support, retiring API versions, expiring certificates.
- AI readiness — whether your metadata is clean enough for Agentforce and AI agents to ground on without giving wrong answers.
The free options, honestly ranked
Salesforce Optimizer (Setup → Optimizer) is free, native, and a fine first look — but it stays at the surface and can't see silent failures or access sprawl. Security Health Check is also native and free, focused narrowly on security settings. For the complete picture, OrgAudit — built by TechParrot, the team behind FieldRat — runs 65 automated checks across all five areas above, read-only, with an executive briefing, a findings tracker, and a field retirement workbook. It's free: request an OrgAudit. For the business case behind health checks, TechParrot's guide covers the five warning signs and costs.
Why field debt is the finding that never stays fixed
Access you fix once. A failing job you fix once. Fields regrow — every project, every admin, every “quick fix” adds more, and each one needs usage evidence and a dependency scan before it can be retired safely. That's why the field dimension needs a tool your admin runs continuously, not an annual audit finding. FieldRat does exactly that: population analysis, dependency mapping across up to 23 metadata types, a 0–100 deletion risk score, and exportable retirement evidence — natively in Salesforce, free. See how to find unused fields for the method.
The pattern that works: a free whole-org OrgAudit to diagnose everything once, then FieldRat to keep the field dimension clean between audits.
Salesforce org health check: FAQ
What does a Salesforce org health check cover?
A complete org health check looks at five areas: field and metadata debt (unused fields, dead automation), access risk (dormant users, over-broad permissions), silent failures (error emails to departed users, empty queues, failing jobs), upcoming Salesforce deprecations, and — increasingly — AI readiness for Agentforce. Field debt is usually the highest-volume finding.
Is there a free Salesforce org health check?
Yes. Salesforce Optimizer and Security Health Check are free and native but stay at the surface. For a complete free audit, TechParrot (the team behind FieldRat) runs OrgAudit — 65 automated checks with an executive-ready report, read-only, at techparrot.io/products/orgaudit.
How often should I run an org health check?
A full audit once or twice a year, or before any major event — migration, merger, Agentforce rollout, new integration. The field dimension moves faster than the rest, which is why continuous field-level monitoring with a tool like FieldRat pairs well with periodic whole-org audits.
What's the difference between an org health check and field cleanup?
The health check diagnoses everything once; field cleanup is the ongoing work on the highest-volume finding. OrgAudit tells you that you have 800 retirement-candidate fields; FieldRat is where your admin lives to verify, score, and retire them safely with evidence.