2026-06-19 · FieldRat

Salesforce custom field limit: how to free up headroom

Salesforce caps custom fields per object — 800 on most standard objects in Enterprise and Unlimited editions, lower on some objects and editions. Once a busy object gets close, the fix usually isn't "ask Salesforce for an exception." It's finding the fields nobody's used in years and retiring them first.

Why orgs hit the limit before anyone notices

The limit creeps up slowly. A field gets added for a campaign that ended two years ago. A picklist gets added for a record type that was deprecated last year. An integration field stays after the integration it served got replaced. None of these show up as a problem until someone tries to add a field for a real project and gets blocked by the cap on Account or Opportunity — usually the two most field-heavy objects in any org, and usually mid-deploy when it's least convenient to find out.

Step 1: Know how close you actually are, per object

Field count alone isn't the full picture — the limit is per object, and it varies by object type and edition (it's lower on objects like Case in some configurations than on Account). You need a per-object view of current field count against that object's actual cap, not a global custom-field count across the org. FieldRat's dashboard tracks field-limit utilization per object so you can see which ones are actually close before you're blocked by one mid-deploy.

Click to enlarge

Step 2: Separate "old" from "actually unused"

A field created five years ago isn't automatically a retirement candidate — it might be the most-used field on the object. Field age tells you nothing about field usage. Run a population check across the object's fields and look for the ones sitting at 0–2% population given the object's record count. Those are your real candidates, regardless of how old or new they are.

Step 3: Check dependencies before retiring anything

Freeing up headroom only works if the fields you retire actually stay retired — not rolled back two days later because a flow broke. Before deleting a low-usage field, scan it against validation rules, flows, Apex, reports, and layouts. FieldRat's Quick Scan covers 11 metadata types in seconds; for fields with any ambiguity, Deep Scan extends to 23 metadata types via a metadata ZIP, including Apex and flow references that Setup's native dependency view misses.

Step 4: Retire in batches, not one field at a time

If an object is near its cap, you likely need to retire more than one field to get meaningful headroom back. Score every candidate's deletion risk (0–100, based on usage, dependency breadth, and whether any dependency hit lands in a critical metadata type), sort by risk, and clear the lowest-risk batch first. That gets headroom back fast without touching anything a flow or integration still depends on.

Related: How to find unused fields in Salesforce, or see how FieldRat compares to other tools on the comparison hub.