Low fill rate, no layout presence, and no visible metadata references can make a field a cleanup review candidate — but they do not prove the field is safe to remove.
Read-only diagnostics · Review-ready workbooks · No package install · No Connected App
Salesforce field cleanup review candidates are fields that available metadata signals suggest may be unused, redundant, or low-value — and therefore worth closer review before cleanup work begins. They are not fields confirmed as safe to delete.
The distinction matters. Salesforce metadata can show fill rates, layout presence, FLS visibility, and whether a field appears in automation or formulas. It cannot show every external system that reads or writes the field, every export or data warehouse that depends on it, or every business process that uses it outside standard record creation.
A field can show zero fill rate in Salesforce metadata while still being written to by an external form, read by a middleware integration, referenced in a BI tool dataset, or used in a data export that bypasses the Salesforce UI entirely.
Examples of how this plays out in practice:
Low usage is a signal worth reviewing. It is not a conclusion.
Multiple signals together strengthen the case for review — but no combination of metadata signals alone confirms that a field is safe to remove.
Relevant Workbook
Field & Object Audit surfaces fill rates, layout coverage, FLS visibility, hidden populated fields, and multi-signal review candidates for selected objects in a review-ready XLSX workbook.
The following systems and patterns are common sources of hidden field dependencies. None of them appear in standard Salesforce metadata:
See Salesforce external field dependencies for a deeper look at what metadata may not show.
A field cleanup review process that surfaces candidates rather than issuing delete instructions puts the right decision with the right people:
Also see the Salesforce field cleanup checklist for a broader pre-cleanup review process.
No. A zero fill rate means no records in the queried dataset have a value in that field. It does not mean no external system reads or writes to the field, no automation references it, no report uses it, and no business process depends on it. Validate with field owners and integration owners before removing any field.
Field cleanup review candidates are fields that available metadata signals suggest may be unused, low-value, or redundant. They are not fields marked safe to delete — they are fields that warrant a closer conversation with business owners, automation owners, and integration owners before any action is taken.
External integrations, marketing automation platforms, middleware, BI tools, data warehouses, web-to-lead forms, portals, and exports that read or write Salesforce fields may not appear in org metadata. These are common consumers of fields that look unused inside Salesforce.
Yes. Before removing a field, validate with the teams responsible for integrations, forms, data warehouses, and reporting outside Salesforce. A field that shows zero fill rate and no metadata references can still be actively used by a system that writes to it outside of standard record creation.
Field & Object Audit surfaces fill rates, layout coverage, FLS visibility, and multi-signal review candidates for selected objects in a review-ready XLSX workbook. It helps admins organize the review process — not make deletion decisions.
Run a read-only KeelCadence diagnostic to surface metadata, access, automation, field, and readiness signals before cleanup, UAT, imports, handoff, or change work.
Read-only · No package install · No Connected App setup · No Salesforce writes
Trust & Security
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.