2026-08-04 · Updated 2026-08-04 · FieldRat

Salesforce field cleanup checklist: what to check before deleting a field

Field cleanup is one of the fastest ways to reduce Salesforce technical debt, but deleting the wrong field can break automations, reports, integrations, and trust. Use this checklist before retiring any custom field.

The short checklist

Confirm the field owner and original business purpose.
Measure field population against the object's total record count.
Separate empty fields from stale fields that still hold old data.
Scan formulas, validation rules, flows, Apex, reports, layouts, and integrations.
Check whether the field affects required reporting, compliance, or AI/data quality work.
Export the evidence before retiring anything.
Hide or deprecate first when the blast radius is unclear.
Delete only after review in sandbox and business sign-off.

1. Start with field usage, not instinct

A field that looks obsolete may still be used by a quiet business process. Start by measuring population: how many records actually hold a value, compared with the object's total record count. Fields at 0-2% population are cleanup candidates, not deletion approvals.

2. Scan dependencies before you remove anything

The dangerous fields are often empty but referenced. Check formulas, validation rules, flows, Apex, reports, dashboards, layouts, list views, permission logic, and integrations. Salesforce's native views help, but they do not give a bulk cleanup workflow across every field candidate.

3. Classify the retirement risk

Sort candidates by blast radius. A field with zero values and no dependencies belongs in the low-risk review queue. A field referenced by Apex, Flow, integrations, or compliance reports needs deeper review even if nobody has populated it in years.

Usage

Population and stale-value checks

Dependencies

Metadata references before deletion

Risk score

Prioritized cleanup candidates

Evidence

Exports for review and sign-off

4. Retire in stages when risk is unclear

If ownership or dependency risk is uncertain, do not jump straight to deletion. Rename, hide, remove from layouts, or mark deprecated first. Watch for user impact, then delete only after sandbox validation and stakeholder sign-off.

5. Keep the evidence

Good cleanup work leaves a trail: field name, object, population, dependency scan, owner, decision, date, and reviewer. This is what keeps a field cleanup project from becoming tomorrow's undocumented technical debt.

How FieldRat helps

FieldRat combines field usage analysis, dependency scanning, a 0-100 deletion risk score, and exportable cleanup evidence so Salesforce admins can retire fields with confidence instead of guesswork.

Salesforce field cleanup FAQ

What should I check before deleting a Salesforce field?

Check population, metadata dependencies, business ownership, reporting usage, integrations, and deletion risk. A field with 0% population can still be referenced by formulas, flows, Apex, layouts, reports, or external mappings.

Is an empty Salesforce field safe to delete?

Not automatically. Empty means the field has no values on records. It does not prove the field is unreferenced. Always scan dependencies before deletion.

How often should admins run Salesforce field cleanup?

Run a field cleanup review before major releases, after large implementations, and at least quarterly for high-volume orgs near custom field limits.