Limitations on Historical Trend Reporting

Historical trending in Salesforce is subject to certain limits on the time during which data is tracked, the number of rows of data, and the fields and objects you can track. These limits are designed to restrict the data set so that reports return data quickly.

• Salesforce retains historical data for the previous 3 months, plus the current month. If you enable Historical Trending in Pipeline Inspection, up to 12 months of Opportunity history is stored.
• Up to 5 million rows of historical trending data can be stored for each object. Historical data capture stops when the limit is exceeded. The admin is alerted by email when any object reaches 70 percent of the limit, and again if the limit is exceeded.
• Each historical trend report can contain up to 100 fields. In Opportunities reports, the fields include standard preselected fields, which can’t be disabled.
• For historical trend reports in Lightning Experience, you must set the snapshot date as the primary row grouping.
• Formula fields aren’t supported.
• Row limit filters aren’t supported.
• The summary report format isn’t supported.
• You can specify up to 5 historical snapshot dates in each historical trend report.
• You can use up to 4 historical filters on each historical trend report.
• These field types are supported: Number, Currency, Date, Picklist, Lookup.
• Dynamic exchange rates aren’t supported. When you run a historical trend report, it uses a static exchange rate, which could be outdated.
• Internet Explorer 6 isn’t supported.
• You can’t subscribe to historical trend reports.
• The Report Wizard isn’t supported. Historical trend reports can only be created with the Report Builder.
• Historical trend reporting with charts is supported in Lightning Experience, but tabular views of historical trend reports aren’t available.
• Historical trending reports can’t be exported.
• When you enable historical trending, data collection starts from when the record was last modified.

Important If a picklist field is already being used in a historical trending data filter, consider the impact before changing any of its values. You could make that field less useful for historical reporting in the future.