Salesforce field history tracking: the limits, and what to do about them

The short answer: The Salesforce field history tracking limit is 20 fields per object, and the history stays in the UI for about 18 months (24 months through the API). Tasks and Events get six fields. Field Audit Trail, Salesforce’s own add-on, raises the cap to 200 fields per object and keeps history until you delete it. Otherwise you choose your 20 carefully.

A VP forwards a screenshot with one line: “What was this amount last quarter, and who changed it?” You open the record, find the history list, and see a tidy table that starts three weeks ago. Or nothing at all, because Amount was field number 21 and nobody picked it.

Field history tracking is a good feature with hard edges. Knowing the edges before the question arrives is the difference between a two-minute answer and an afternoon of asking people what they remember.

How many fields can Salesforce field history track?

Twenty per object is the standard limit, as reported by Salesforce Ben, and it applies to standard and custom objects alike. Events and Tasks are tighter: Salesforce Help says you can track up to six fields per object on them, and only standard fields qualify.

The User object has its own arrangement. Salesforce Help says admins can track a maximum of 20 fields there, chosen from a fixed list that includes Name, Email, Profile and Role. Winter ’27 brought field history to the User object, and we cover it in field history tracking for the User object.

Two more edges from the same Help article. Long text fields with more than 255 characters are logged only as an edit: the before and after values aren’t stored or shown. And as reported by Salesforce Ben, formula fields can’t be tracked at all.

How long does Salesforce keep field history?

About 18 months in the UI and up to 24 months through the API, per Salesforce Help. Data older than 18 months can be retrieved with Data Loader or the queryAll() API. Salesforce Ben reports the same split.

The upside is that field history doesn’t count against your data storage, according to the same Help article. The downside is the clock. A question about a change two years ago has no native answer unless you did something about it two years ago.

What is Field Audit Trail?

Field Audit Trail is Salesforce’s own extension to field history tracking, sold as an add-on. Salesforce’s Trailhead module says it lets you track up to 200 fields per object, with custom retention periods in months or years and history that can be stored indefinitely. Salesforce’s Shield product page says up to 10 years. Salesforce Help says that with Field Audit Trail turned on, Salesforce retains history until you manually delete it. The sources describe the retention a little differently, so read your own contract and the current documentation before you promise an auditor a number.

Some older articles still say Field Audit Trail raises the limit to 60 fields. That figure appears in Salesforce Ben’s guide, but Salesforce’s current Trailhead and Shield pages say 200. Trust the Salesforce pages.

If you need long, defensible retention on a set of regulated fields, this is the native answer and it deserves a real look. Check which editions and licenses it is available for in your org.

How do you choose which 20 fields to track?

Track the fields where a change tells a story and where someone will one day ask “who did that?”. Start there, not with the fields that are merely important.

A short method that works:

  1. List the disputes you have already had. Amount, Close Date, Stage, Owner, Account Type, Status on Cases. Real arguments beat guesses.
  2. List the fields that drive money or access. Forecast category, discount, contract end date, a credit-hold checkbox.
  3. Skip fields that change on every save. Anything updated by automation all day will fill the history list with noise and make the real change harder to find.
  4. Skip what history can’t show. Formula fields and long text over 255 characters won’t give you useful values.
  5. Leave two or three slots empty. The next question will be about a field nobody thought of.

Then turn it on. Per Salesforce Ben, for a standard object open it in Object Manager, go to Fields & Relationships and choose Set History Tracking. For a custom object, enable Track Field History in the object’s details first, then pick fields. Ben also reports that since Summer ’24 there is a dedicated Field History Tracking page in Setup that manages objects and fields together. Changes are tracked from the moment you select a field, but users see them only after you add the history related list to the page layout or record page.

That last point catches people. Tracking starts when you save the selection, never earlier. There is no back-filling.

What do you do when 20 fields is not enough?

You have four honest options, and the right one depends on how long you need the history and how many objects are involved.

OptionGood forWatch out for
Choose better fieldsMost orgs. Often the limit is a prioritization problemYou will still have nothing for field 21
Field Audit TrailRegulated fields, long retention, one vendorSold separately, so check your edition and contract
Your own history object, fed by a Flow or triggerSmall, specific needs on one or two objectsYou build it, you maintain it, and its records count against your data storage
A history app that keeps its own logMany fields or objects, retention you set, restore from the logAnother thing to install and secure; history starts when you begin

A custom history object is the one admins try first, and it works. It is also the one that turns into a Flow nobody dares touch in two years. If you go that way, write down which fields it covers.

Whatever you choose, remember native history is a log of field changes, and nothing more. It doesn’t tell you who changed a permission or a setting. For that you need other audit tools, and we get into that in the User object post.

What to do Monday:

1. Pick your five most-argued-about objects and write down which fields each already tracks.

2. For any object at 20 fields, review the list and swap out fields that change by automation.

3. Check the page layout. History that nobody can see is history nobody uses. Add the related list where it’s missing.

4. Ask the person who owns audits what retention they need, in years. That number decides whether you need more than native.

Where we come in

Wake, by GTM Cloud, is in early access. It logs changes to the fields and objects you choose, past the native 20-field limit, with retention you set. It sits beside Salesforce’s own history, so you don’t turn anything off. It stores history in Big Objects in your org, starts from the day you begin monitoring a field, and doesn’t back-fill. See the Wake page.

Questions people ask

What is the field history tracking limit in Salesforce?

Twenty fields per object for standard and custom objects, as reported by Salesforce Ben. Per Salesforce Help, Tasks and Events allow six, standard fields only. Field Audit Trail, an add-on, raises the limit to 200 fields per object. Check your edition, because availability depends on it.

How far back does Salesforce field history go?

Native history is kept for about 18 months in the UI and up to 24 months through the API, according to Salesforce Help. With Field Audit Trail turned on, Salesforce retains history until you delete it. Tracking starts when you select a field, so you can’t recover changes made before that.

Does field history count against Salesforce storage?

No. Salesforce Help says field history data doesn’t count against storage limits. That changes if you build your own history object, because its records use data storage like any other custom object. It is one more reason to compare options before you build a log with a Flow.

Sources