Loading

Behavior After Extending the Archive Period for Activity Records (Events and Tasks) in Salesforce

Publiseringsdato: Jan 29, 2026
Beskrivelse

This article explains the impact and considerations when extending the archive period for activity records (Events and Tasks) in Salesforce organizations with a large volume of data.

Løsning

Salesforce Support cannot provide specific guidance on individual organizational changes, as the impact depends on factors such as the number of custom fields in the Activity object (Events and Tasks), display columns in reports or list views (including related objects), and filter conditions.

Testing Recommendations for Organizations with Full Sandboxes

For Customers with Full Sandbox: We recommend preparing a Full Sandbox with a record count equivalent to your production environment to perform advance verification. Please note that activity records (Events and Tasks) already archived in the production environment are not copied to the Sandbox. Therefore, you must prepare an equivalent number of activity records and related object records within the Sandbox environment for testing.

Incremental Approach for Organizations without Full Sandbox

For Customers without Full Sandbox: Consider extending the archive period for activity records (Events and Tasks) incrementally (e.g., 1 year -> 2 years -> 3 years, etc.).

Performance Optimization After Extension

General Recommendation: If you experience performance degradation after extending the archive period for activities, we recommend adding stricter filter criteria (such as date ranges or specific field filters) to your reports to reduce the volume of data being processed.

Knowledge-artikkelnummer

005299570

 
Laster
Salesforce Help | Article