This article helps to answer some of the most frequently asked questions regarding the 'Full Data Export' feature.
Large exports can take a long time to complete. This is expected behavior. Completion time depends on the size of your export and current traffic on the instance. Unfortunately, it is not possible for Salesforce to speed up this process.
Data Export is not optimized for speed. If this is not acceptable for your needs, please consider alternative options such as the data loader tool or explore third-party apps on AppExchange.
This is expected behavior. The system allows only one file download at a time, and there is a 60-second wait required between downloads. If you try to download multiple files too quickly, you’ll see the following error:
HTTP ERROR 429 Too many requests. Please try again later.
URI: /servlet/servlet.OrgExport
STATUS: 429
MESSAGE: Too many requests. Please try again later.
SERVLET: system.organization.OrgExportServlet
This rate limit is in place to help prevent system overload and ensure fast, reliable downloads for all users.
Your Salesforce organization can generate backup files of your data on a weekly or monthly basis, depending on your edition. You can generate backup files manually once every 7 days for weekly exports, or 29 days for monthly exports. Weekly exports are available in Enterprise, Performance, and Unlimited Editions. Monthly exports are available in All editions, except for Database.com.
Export files are available to download for 48 hours after completion.
No. Recycle Bin data is not included in the exported data.
The export files are removed as soon as a new Data Export is queued up, even if you are within the 48 hour window. See 'Full Data Export' files not available after completing upload for more details.
No, once the files have been removed from the 'Setup' section, there is no way for either customers or support to recover or download them.
There is no SLA for Data Exports. It may be expected for a request to take longer than a week to complete. Support does not have a means to expedite an export.
As previously mentioned, heavy traffic can delay an export delivery. For example, assume that you schedule a weekly export to run until the end of the month, beginning April 1. The first export request enters the queue, but due to high volumes of requests, the export isn’t delivered until April 8. On April 7, when your second export request was scheduled to be processed, the first request is still in the queue. So, the second request isn’t processed and the new next scheduled export date will be updated to April 14.
Yes, if an export request is in progress or hasn't completed by the time the next scheduled export is supposed to start, the next scheduled export will be skipped in favor of the one in progress and the scheduled export's date will be automatically adjusted and set according to your export interval.
Once the in-progress export, which has superseded the next, completes, administrators can request an export manually via the 'Export Now' button. However, keep in mind that the export interval between requests will still apply. Requesting a manual export will automatically adjust your 'Next scheduled export' date to adhere to your organization's corresponding export interval.
Yes, see the Change date or delete scheduled data export article for more details. Deleting the job will also allow an Admin to change the 'running user' of a weekly Data Export.
If the size of data in the organization is large, multiple .zip archives are created. Each .zip archive file contains one or more .csv files and can be up to 512 MB (approximately). If the total size of the exported data is greater than 512 MB, the export generates multiple .zip files.
If you did not select all objects or select 'Include images, documents, and attachments' and 'Include Salesforce Files and Salesforce CRM Content document versions,' you may receive fewer files than with a complete data export.
The 'Files' feature in Salesforce allows you to upload files up to 2 GB. If your .zip files are substantially larger than 512 MB, it's likely that a User has uploaded a large file and it's being included in it's own .zip file. To identify potential large files, navigate to Setup, enter Storage Usage in the Quick Find box, then select Storage Usage. Scroll to the very bottom of the page and click the Overall Top Files by Storage Utilization link.
See Data export CSV file is too big to open for more details.
See Schedule Export option does not save for more details.
Although it is possible to schedule the data export in sandbox, it's expected behavior for it to never actually process. See the sandbox Product and Service Exclusions documentation for more details.
These alerts can originate from both production and sandbox organizations. Administrators may need to review scheduled export jobs in all environments.
Evaluate whether you can export required data via alternative means as outlined in our Export Data documentation. If this is not feasible, your request will need to be evaluated and approved on a one-off basis. Please log a case with Salesforce Support and be sure to include a detailed business impact and explanation, so that Salesforce Support may evaluate your request. Note: Creating multiple schedule export is currently not a Salesforce functionality yet. However, you can check and upvote for this Idea as a feature request Create multiple data export schedules.
See Request data export when your organization is locked for more details.
Formula and roll-up summary fields are always excluded from exports.
Currently, Data Export is not supported in Read-Only Mode. You will get an error 'Updates can’t be made during maintenance.' or an Internal Server Error ending in '250729683.'
Yes, archived records are included when you perform an export using Data Export service.
This feature is now deprecated. We are working on updating the aforementioned document to remove the reference.
The user who scheduled the export. The email address for this notification can’t be changed. To set a different user, the desired recipient will have to set up a new export schedule.
No impact on users while the Data Export is running on the backend. The data that is being added into the system by users would not be included when the Data Export is already running.
You should not remove permission to run the weekly export or deactivate the user that started the export. Their access is checked during the process and this can result in the process failing.
See also
Export Backup Data from Salesforce
Recover or restore lost or deleted records and data
Salesforce Support video:
How to Export Backup Data from Your Org
000383962

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.