Skip to content

Salesforce field history tracking limits

See the Salesforce field history tracking limits per object, how long history is kept, and what Field Audit Trail adds.

CRM Field Limits

Check how many fields you can track

Type a field, a number or an error, or paste a column. See the Salesforce or HubSpot limit, whether it fits and what to do.

Try:

Runs in your browser. Nothing is sent or stored.

Salesforce field history tracking limits

Open a row for what fails past the limit, what to do and the source.

  • Field history trackingSalesforceup to 20 fields per object
    Limit
    Tracked fields per object
    Value
    Up to 20 standard and custom fields per object; a paid add-on raises it
    Applies to
    Each object (business and person accounts share one 20)
    Can be raised
    a paid add-on through your Salesforce account executive, up to 60
    Past the limit
    Setup won't let you pick a 21st field. A deployment fails with NUM_HISTORY_FIELDS_BY_SOBJECT_EXCEEDED: "The number of history fields specified for the sObject exceeds the allowed limit."
    What to do
    Track the fields an auditor asks about. For more, your account executive sells Field Audit Trail or Additional Field History Per Entity.
    Watch out
    • Salesforce Support can't raise it.
    • Formula, roll-up summary and auto-number fields can't be tracked, nor Created By and Last Modified By.
    • Multi-select picklists and long text fields are tracked as changes only, without old and new values.
    • History is kept 18 months in Salesforce and 24 months through the API.
    • Tracking starts when you turn it on; earlier changes aren't recorded.
    • Available in Contact Manager, Group, Essentials, Professional, Enterprise, Performance, Unlimited and Developer editions.
    Who can change it
    An admin with the Customize Application permission picks the fields; only a paid add-on raises the 20.

    Source: Salesforce Help: tracking field history for standard objects (opens in a new tab); more: Salesforce Help: tracking field history (opens in a new tab), Salesforce Help: field audit trail (opens in a new tab), Salesforce API status codes (opens in a new tab), Salesforce knowledge article 000386871 (opens in a new tab) ยท Checked Nov 15, 2026

  • Field history on tasks and eventsSalesforceup to 6 fields
    Limit
    Tracked fields per object
    Value
    Up to 6 fields on tasks or events, standard fields only
    Applies to
    Task and Event objects
    Past the limit
    You can't track a seventh field, or any custom field, on tasks or events.
    What to do
    For custom activity fields, record changes with a flow into a custom object.
    Watch out
    • Changes can take minutes to hours to show.
    • Up to 60,000 task and event history changes a day per org; past 80,000 a day, Salesforce advises against tracking.
    • Currency and percent fields aren't tracked on activities.
    Who can change it
    An admin with the Customize Application permission.

    Source: Salesforce Help: tracking field history (opens in a new tab) ยท Checked Nov 15, 2026

  • Field history on the User objectSalesforceup to 20 fields
    Limit
    Tracked fields
    Value
    Up to 20 of 23 listed fields
    Applies to
    User object
    Past the limit
    You can't pick more than 20.
    What to do
    Pick the access fields first (profile, role, active).
    Watch out
    • Custom auto-number, formula, rich text and long text fields on users aren't tracked.
    • Role changes made from the Roles setup page aren't tracked.
    Who can change it
    An admin with the Customize Application permission.

    Source: Salesforce Help: tracking field history (opens in a new tab) ยท Checked Nov 15, 2026

  • Field Audit TrailSalesforceup to 200 fields per object (one Salesforce article says 60)
    Limit
    Tracked fields per object with the paid add-on, and how long history is kept
    Value
    Up to 60 or 200 fields per object, by which Salesforce page you read; history kept until you delete it
    Applies to
    Each object with a retention policy
    Default
    Archives after 18 months in production, 1 month in sandboxes
    Another page says
    Salesforce's Field Audit Trail page says 200; its article on raising the limit says 60.
    Past the limit
    You can't pick more than 200 fields for an object.
    What to do
    Buy Salesforce Shield or Field Audit Trail licenses (Enterprise, Performance and Unlimited), then deploy a retention policy with the Metadata API.
    Watch out
    • Salesforce's Field Audit Trail page (Nov 13, 2026) says up to 200 tracked fields per object; its knowledge article on raising the history limit (Oct 13, 2026) says up to 60. Many guides repeat 60. Confirm the number in your contract.
    • Archived history lives in the FieldHistoryArchive big object and is read through the API only.
    • Field history data doesn't count against data storage.
    • Available in Enterprise, Performance and Unlimited editions with Salesforce Shield or Field Audit Trail licenses.
    Who can change it
    Your Salesforce account executive sells it; an admin deploys the retention policy.

    Source: Salesforce Help: field audit trail (opens in a new tab); more: Salesforce knowledge article 000386871 (opens in a new tab) ยท Checked Nov 15, 2026

  • Field history retentionSalesforce18 months, 24 through the API
    Limit
    How long history stays
    Value
    18 months in Salesforce, 24 months through the API; until deleted with Field Audit Trail
    Applies to
    Each tracked change
    By object or place
    • in Salesforce18
    • through the API24
    Past the limit
    Older history can be gone; read it with Data Loader or queryAll() while it's 18 to 24 months old.
    What to do
    Export history you must keep before month 18, or add Field Audit Trail.
    Who can change it
    An admin.

    Source: Salesforce Help: tracking field history (opens in a new tab) ยท Checked Nov 15, 2026

Browse all 70 limits

Pick a group, or open a row for its details and source.

How we built this list

How the limits were read and checked

Every limit comes from the platform's own help, API, knowledge or plan pages, quoted and dated per row. Where two of a platform's pages disagree, both are shown and the check uses the lower number. Limits Support can raise say so, with the most they can be. Nothing you type or paste leaves your browser.

Photo of Utku Zihnioglu

By

ยท CEO & co-founder

Published Nov 16, 2026

New page: tracked fields per object, retention and Field Audit Trail, with a count check.

Salesforce field history tracking limits allow up to 20 tracked fields per object, with history kept 18 months in the app and 24 months through the API. Type how many fields you want to track, or ask about retention or Field Audit Trail, and the tool above says whether it fits and what raises it.

How to read the result

The verdict compares your number with the per-object limit first. The rows under it show the other history limits: tasks and events track fewer fields, and only standard ones; the User object has its own allowance; Field Audit Trail is a paid add-on with a much higher cap.

Where Salesforce's own pages disagree, as they do on how many fields Field Audit Trail tracks, the tool shows both numbers with each page's date and checks your count against the lower one. Open a row for the source.

Some fields record less than you'd expect. Long text and multi-select picklist fields are tracked as changes only, without the old and new values. Formula, roll-up summary and auto-number fields can't be tracked at all, and tracking starts the day you turn it on, so earlier changes are never recorded.

When the limit isn't enough

Start with the fields an auditor or a compliance request will ask about: owner, stage, status, amount and the fields your team argues over. Salesforce Support can't raise the per-object limit. More tracked fields come only from a paid add-on, Field Audit Trail or Additional Field History Per Entity, which your Salesforce account executive sells. Field Audit Trail also keeps history until you delete it, instead of the standard retention. Ask for the per-object number in writing, since Salesforce's pages give two.

If you must keep history past the standard window without the add-on, export it on a schedule before it ages out; Data Loader can read it through the API while it is still there.

When most changes come from an enrichment or a sync rather than from people, review them before they reach the CRM. In Oneprofile you see every enriched column in a table before it is written to Salesforce, so the tracked fields can stay on what people edit.

Salesforce field history tracking limits: questions

How many fields can you track history on in Salesforce?

Up to 20 standard and custom fields per object. Accounts and person accounts share the same 20.

Can the field history limit be raised?

Only with a paid add-on. Salesforce Support can't raise it; Field Audit Trail or Additional Field History Per Entity, sold by your Salesforce account executive, adds more tracked fields.

How many fields does the audit trail add-on track?

Salesforce's Field Audit Trail page says up to 200 per object, while its knowledge article on raising the history limit says up to 60. Confirm the number in your contract before you plan on more than 60.

How long does Salesforce keep field history?

18 months in Salesforce and 24 months through the API. With Field Audit Trail, history is kept until you delete it.

Can you track history on tasks and events?

Yes, up to 6 fields, and only standard ones.

About this article

Photo of Utku Zihnioglu

Utku Zihnioglu

CEO & co-founder

Serial entrepreneur who built infrastructure companies handling billions of requests. Now leads engineering at Oneprofile, which finds the people worth talking to, researches each one, and follows up until they reply.

Drafted with AI from our product docs and code. Utku Zihnioglu answers for what it says.

Enrich records, then write them to your CRM

Find the missing details in a table, shape each column to your field, and write it to the Salesforce or HubSpot field you pick.

Free plan: 200 credits a month, 3 integrations, no card

Enrich records, then write them to your CRM

Find the missing details in a table, shape each column to your field, and write it to the Salesforce or HubSpot field you pick.

Free plan: 200 credits a month, 3 integrations, no card