You find unused fields by reviewing field population, layout visibility, permissions, reporting, automation, and business context together — and by treating low usage as a review candidate, not a delete instruction.
Read-only diagnostics · Review-ready workbooks · No package install · No Connected App
Unused fields in Salesforce can be found by reviewing field usage across several signals: population and fill rate, page layout and Lightning record page visibility, field-level security and profile or permission set access, and references in reports, list views, automations, and integrations — together with the business context behind each field.
No single signal is enough on its own. A field that looks abandoned can still hold data, drive a formula, feed an overnight integration, or matter to one team on one record type. The goal of this guide is to help you surface review candidates and validate them before making any cleanup decision.
In practice, "unused" usually means a field that has little or no population, no visible business process behind it, no usage on layouts, reports, list views, or automation, and no clear owner who can explain why it exists.
The important distinction is that zero data does not automatically mean a field is unused, and an unused-looking field is not automatically safe to delete. A field can be empty because it is brand new, because it is populated only by a process that has not run recently, or because it is restricted through field-level security to a small group of users whose records you are not looking at.
Signals that a field may be a review candidate
You can build a first-pass picture by hand using Setup, Object Manager, and reporting. The work is methodical: gather the metadata, then layer the usage signals on top of it.
Practical steps
Fill rate is the fastest first signal, but it is only the first one. For the full set of signals worth reviewing, see why fill rate alone is not enough and how field usage by record type can change the picture.
The reason field cleanup stalls is rarely effort. It is that the signals are spread across the org and easy to misread.
What makes it hard
This is the same problem that makes inherited orgs hard to change safely. If you are new to the org, start with the inherited Salesforce org checklist before touching fields.
Once you have a list of review candidates, validate each one against these checks before changing or deleting anything. Treat the list as evidence to discuss with owners, not a queue of approved deletions.
Review before changing or deleting
A review candidate becomes a cleanup decision only after owners confirm it and you have validated the change in a sandbox.
Gathering these signals by hand is workable for one object and slow across an org. KeelCadence Field & Object Audit is a read-only diagnostic that helps surface field usage, fill rates, hidden populated fields, layout coverage, exposed-but-unused fields, cleanup candidates, and supporting reference signals in a review-ready XLSX workbook.
It does not make deletion decisions for you. It gives you the signals in one place so you can review candidates with context and validate them with the right owners before changing anything.
Relevant Workbook
Field & Object Audit surfaces field utilization, fill rates, hidden populated fields, layout coverage, FLS visibility, and cleanup review candidates across selected objects in a review-ready workbook.
Once you know which signals to review, run the read-only Field & Object Audit to capture fill rates, hidden populated fields, layout coverage, and cleanup candidates in one review-ready workbook. See the free on-screen summary before purchase.
KeelCadence uses session cookies and Google Analytics 4 for site usage insights. GA4 does not receive Salesforce credentials, Org IDs, Report IDs, or payment data. You can opt out for this browser.