This article explains how to request an increase to the maximum number of fields allowed for Field History Tracking per object (entity) in Salesforce. Field History Tracking lets administrators monitor changes made to specific field values on records, capturing who changed a value, when it was changed, and what the previous value was.
Some organizations with complex compliance, audit, or data governance needs may find the default limit insufficient for their use case.
This article answers how to increase the 'Number of Fields to Track History per Entity' limit in Salesforce. The limit cannot be increased manually or with the help of Salesforce Support, and your Salesforce Account Executive (AE) can help you request an increase.
Field History Tracking is a native Salesforce feature that records changes to field values on standard and custom objects. When enabled, Salesforce logs changes up to the tracked field limit per object, storing the old value, new value, date, and the user who made the change.
Professional, Enterprise, Unlimited, Performance, and Developer editions. Field History Tracking is available across all Salesforce editions.
The default limit is 20 fields per object. Activities objects (Task and Event) are separately limited to 6 fields per object.
If the limit is increased, the maximum is up to 60 fields per object, available through the purchase of Field Audit Trail.
If your organization needs this limit increased beyond the default of 20 fields per object, contact your Salesforce Account Executive (AE) to purchase Field Audit Trail or the Additional Field History Per Entity product.
Note 1: While Salesforce Support cannot assist with this limit increase, your AE can provide you with additional options, including the purchase of Field Audit Trail, which raises the limit to 60 fields per object.
Note 2: This does not apply to the Field History Tracking limit for the Activities object (Task and Event), which is separately limited to 6 fields per object.
If the limit has been increased in production, the same limit can be applied in sandboxes by using the License Match Tool.
000386871

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.