Salesforce Data Export Limits – Winter ’26 Update Explained

The Salesforce Data Export tool lets you back up your data manually or on a schedule. To use it effectively, you need to understand the limits on export frequency, file handling, and availability. 

This article explains these limits, outlines the possible workarounds, and highlights the changes introduced in the Winter ’26 release.

These limits apply to all orgs that use the standard Data Export tool in Setup.

Salesforce restricts how frequently full data exports can run:

• Weekly exports: Available once every 7 days in Enterprise, Performance, and Unlimited Editions.
• Monthly exports: Available once every 29 days in all other supported editions (excluding Database.com)

After Salesforce generates the export files, they stay available for 48 hours. Once this window ends, the files are automatically deleted.

Older documents used the phrase “48 business hours.” Salesforce’s current guidance (2025) now states “48 hours,” and this is the correct behavior across orgs.

If you start a new export—manual or scheduled—Salesforce immediately deletes all files from the previous export.

This happens even if the earlier export is still within the 48-hour availability period.

This is expected system behavior and not a bug. Salesforce can retain only one export set at a time.

Once export files are deleted—either because 48 hours passed or because a new export was initiated—they cannot be restored. Admins should monitor completion emails and download files soon after they become available.

Salesforce applies the following rules when preparing export files:

• ZIP file creation: Exported data is packaged into ZIP files of roughly 512 MB each. Large exports automatically split into multiple ZIPs.
• Export format: Each object exports as a CSV file.
• Formula and roll-up summary fields: These fields do not export because Salesforce calculates their values dynamically.
• Recycle Bin: Records in the Recycle Bin are not included in exports.

Salesforce enforces several process-level limits on Data Export jobs. These limits affect how exports are scheduled and executed.

You can maintain only one active Data Export schedule per org—weekly or monthly.

Salesforce does not allow editing the schedule type or running user. To change either, you must delete the existing schedule and create a new one.

Salesforce does not provide an SLA for the completion of Data Export. Export jobs may take several days or longer if system queues are busy. This is expected behavior.

Data Export does not run in sandbox orgs or in orgs that are in read-only mode. Salesforce disables this functionality by design.

Only the running user receives email notifications for completed exports.

You cannot change the notification address on an active schedule. To use a different email, recreate the schedule with a different running user.

Salesforce has added a new restriction in the Winter ’26 release that affects how administrators download exported ZIP files from Data Export. This update introduces a delay between downloads. 

Salesforce now enforces a sequential download policy for export files:

• Users can download only one export file at a time.
• A 60-second wait is required before downloading the next file.
• Starting a second download too soon triggers an HTTP 429 “Too Many Requests” error.

This controls repeated manual downloads and reduces load on the export service. However, for customers who export dozens of files each week, it introduces extra manual work and can disrupt automations that previously ran smoothly.

• The restriction applies only to manual downloads performed through Setup → Data Export.
• It does not affect API-based tools, Data Loader, XL-Connector, command-line scripts, or any automated integrations.
• This is a UI-only safeguard, not a platform-wide limit.

Teams that rely on exporting data or attachments can avoid this new delay by using XL-Connector. The tool connects to Salesforce through APIs and sends the exported data directly into Excel. Since the Winter ’26 download timing rule affects only the Setup interface, XL-Connector is not impacted by it.

XL-Connector helps users by providing:

• Direct export Salesforce records and files into Excel, without ZIP downloads.
• API-based extraction, which is not limited by the new Winter ’26 timing rule.
• No dependency on the 48-hour expiration that applies to Setup export files.
• Options for bulk exports, filters, and scheduled operations.

• Download export files as soon as they are ready. Delays can lead to lost access, especially if a new export runs.
• Always complete your current downloads before starting another export to avoid conflicts.
• Exclude attachments or large files when they are not needed. Smaller exports finish faster and are easier to store. Export only the required objects to keep the process efficient.
• For consistent backups, use XL-Connector or API automation. These options help you schedule exports and reduce manual steps.

Plan your download window: Salesforce deletes export files after 48 hours or when a new export starts.

Salesforce’s export limits influence how admins plan backups, and the Winter ’26 update adds a timing rule for downloading files. Understanding these limits helps maintain reliable backups. 

For more flexibility, API-based tools like XL-Connector offer a practical alternative to the UI restrictions.