After Salesforce’s Spring 2019 release Field History Tracking older than 18 months will be deleted. Pre-Spring 2019, it was Salesforce’s policy to retain Field History Tracking data for 18 to 24 months as standard, or up to 10 years upon special request. If you require Field History Tracking data to be retained for longer than 18 months you will have to contact Salesforce so they can ensure the correct licensing is in place to retain your data before Spring 19.
Field History Tracking Use Cases
Field History Tracking allows permissioned Salesforce users to see every time a change is made to a specific field. It can be used to provide analytics for certain specific use cases. Finance users can use reports generated from Field History Tracking to identify whether or not an account executive is properly processing opportunities, not over-inflating pipeline, or skipping stages. If the organization does not have a comprehensive backup and recovery solution, some Salesforce admins will use Field History Tracking as a makeshift backup solution to fix individual fields. As a new user is being trained, the Salesforce admin or the user’s manager can leverage Field History Tracking to see if the new user is using Salesforce as instructed.
Track Field History with OwnBackup
Customers with OwnBackup need not be concerned about this change because all of their audit logs, including fields, are already backed up with OwnBackup. In fact, OwnBackup offers its customer unlimited storage for all of their data, metadata, and attachments. Furthermore, all of the use cases mentioned above are much easier to run using OwnBackup Compare, which allows you to view business data changes by comparing data and metadata backups to pinpoint data loss and corruption or simply track historical data changes.