Migration planning

6 Ways to Export Salesforce Data and What Each One Misses

Salesforce data export compared: Data Export Service, reports, Data Loader Export and Export All, Bulk API 2.0 and the REST API. What each one misses.

Ayush BothraFounding Member, MigrateX

Published 10 min read

Salesforce data export: 6 ways to export, and what each one misses, with the Salesforce logo on a light poster
On this page

To export all your Salesforce data, use the Data Export Service for a no-code backup with files, Data Loader Export All or Bulk API 2.0 queryAll for deleted and archived rows, and the REST API for each file body. Report export and plain Data Loader Export are for lists. No single Salesforce route returns everything.

This guide is for Salesforce admins and operations leads who need their data out, for a backup, an audit or a move to another platform. Every limit comes from Salesforce's Help, Data Loader Guide or developer guides, as of November 2026. Salesforce's limit pages still use the legacy edition names; since 3 September 2026, Core replaces Enterprise Edition and Advanced replaces Unlimited, according to Salesforce's pricing page.

Which Salesforce export method does what?

Each route trades effort for completeness. The six side by side:

MethodWho can use itBuilt forFilesDeleted and archived rowsMain gap
1. Data Export ServiceWeekly Data Export permission; weekly on Enterprise, Performance, UnlimitedA full org backup, no codeYes, if tickedNot stated by SalesforceNo formula or roll-up fields; zips deleted after 48 hours
2. Report exportExport Reports permission; Essentials to Unlimited and DeveloperA list someone opens in a spreadsheetNoArchived activities excludedFormatted exports stop at 2,000 or 100,000 rows
3. Data Loader: ExportAPI Enabled and Read; Enterprise, Performance, Unlimited, DeveloperOne object to CSV, on demand or scheduledNoExcludedOne object per query, no child records
4. Data Loader: Export AllSame as ExportThe same, plus soft-deleted and archived rowsNoIncludedStill one object, no files
5. Bulk API 2.0 queryAPI Enabled; on by default on Enterprise, Performance, Unlimited, DeveloperMillions of rows, scriptedNot stated for queriesIncluded with queryAllNeeds code; results kept 7 days
6. REST and SOAP APIAPI EnabledFiles, related records, a moveYes, one request per fileIncluded with queryAll()Every call counts against the daily allocation

1. Data Export Service

What it is. Salesforce's backup service, under Setup > Data Export. It writes one CSV file per object into zip archives of up to about 512 MB each and emails the user who scheduled it.

Who can use it. Users with the Weekly Data Export permission, which Salesforce grants by default only to the System Administrator profile. Only active users can run export jobs. It does not run in sandboxes.

Built for. A dated copy of the whole org with no code.

Includes. Every object you select, plus images, documents, attachments, Salesforce Files and CRM Content versions when you tick the two "Include" options.

Misses.

  • Formula and roll-up summary fields, always, according to Salesforce's Help.
  • Chatter posts and comments beyond 1,000 characters.
  • Fields on person accounts that contacts do not share, in the contact file.
  • Objects created after you ticked "Include all data" on a recurring schedule, unless you tick it again.
  • Deleted records and archived activities: the Data Export article does not say. Salesforce's archived-activities article says only that they can be viewed "in exported data", so count them in your files.

Frequency and limits.

  • Weekly export on Enterprise, Performance and Unlimited Editions; monthly on all editions except Database.com.
  • Manual runs once every 7 days (weekly) or 29 days (monthly). Professional and Developer Editions export only every 29 days and schedule monthly only.
  • Salesforce does not guarantee a completion date, and heavy traffic can push a delivery back by a week.
  • Files download one at a time, 60 seconds apart. The zips are deleted 48 hours after the email, not counting weekends: an email sent on Friday means deletion on Tuesday.

Use it when you want a full safety copy, for example before a licence ends.

2. Report export

What it is. The Export action on any Salesforce report, from the Reports tab or the report run page.

Who can use it. Users with the Export Reports permission, on Essentials, Group, Professional, Enterprise, Performance, Unlimited and Developer Editions.

Built for. A filtered list for a spreadsheet: open opportunities, last quarter's cases, accounts by owner.

Includes. The report's rows and columns. "Formatted Report" keeps the header, groupings and filters and saves only to .xlsx; "Details Only" exports plain rows to .xlsx, .xls or .csv.

Misses.

  • Archived activities: Salesforce's Help says archived activities are not included in reports.
  • Files, and any record the report type does not return.
  • Long text: in Formatted and XLSX exports, Salesforce cuts long text and rich text fields to 255 characters.

Limits. Details Only as CSV or XLS in Lightning Experience has no row or column limit, but your spreadsheet application does. Formatted Report stops at 2,000 rows and 100 columns for matrix reports, and 100,000 rows and 100 columns for tabular and summary reports; the same 100,000-row cap applies to Details Only as XLSX.

Use it when a person needs a list, not a system.

3. Data Loader: Export

What it is. Salesforce's client application for bulk import and export, for macOS and Windows. Salesforce's Data Loader Guide says it outputs CSV files when exporting, and each export is a SOQL query on one object.

Who can use it. Users with the API Enabled permission and Read on the records, on Enterprise, Performance, Unlimited and Developer editions, per the Data Loader Guide.

Built for. Salesforce's Help page on choosing a data method sizes Data Loader for 5,000 to 5 million records. Its Data Loader Guide says it handles files of up to 150 million records with Bulk API 2.0 and recommends a Salesforce partner above that. For loads under 50,000 records into supported objects, Salesforce points to the Data Import Wizard, which imports only.

Includes. One object's fields, plus parent fields through a relationship query (for example, the account name on each contact).

Misses.

  • Attachments: "Data Loader currently does not support exporting attachments", says the guide, which suggests the weekly export instead.
  • Child records: nested queries and polymorphic relationships return an error, so a record's emails, comments and files are separate exports you rejoin by ID.
  • Soft-deleted records and archived activities (use Export All).
  • Compound fields such as addresses: select the individual components.

Frequency and limits. On demand, or scheduled from the Windows command line; Salesforce's guide describes nightly scheduled extractions run by an external scheduler. The command-line interface is Windows only. Data Loader uses the SOAP API by default and returns exported records in batches of 500 by default, 2,000 at most. Salesforce has scheduled the SOAP API login() call for retirement in Summer '27, which affects older Data Loader and integration logins.

Use it when you need one object, or a filtered slice of it, as a CSV.

4. Data Loader: Export All

What it is. The second export button in Data Loader. On the command line it is the extract_all operation, against extract for a normal export.

Who can use it. The same users as Export: API Enabled, and Read on the records.

Built for. Getting what a normal export hides. Salesforce's guide says to click Export All "if you want to also export archived activity records and soft-deleted records".

Includes. Live records, soft-deleted records, and archived Tasks and Events.

Misses. Attachments and child records, exactly as Export does. Check the IsDeleted column, or deleted rows will look live in the destination.

Use it when you need closed activities older than a year, or a record count that matches the source including deletions.

5. Bulk API 2.0 query

What it is. Asynchronous query jobs built for large volumes. You submit SOQL, Salesforce runs it and you download the results as CSV.

Who can use it. Users with the API Enabled permission. Salesforce enables Bulk API 2.0 by default on Performance, Unlimited, Enterprise and Developer Editions.

Built for. Whole tables of millions of rows, such as Cases, EmailMessage records, Tasks or history objects. Salesforce chunks large jobs automatically (PK chunking) where the object supports it, including custom objects and Sharing and History tables. Results are paged with locator and maxRecords, so the client is not bound to a set of files.

Includes. With operation query, rows that are not deleted or archived. With queryAll, also rows deleted by merge or delete and archived Task and Event records.

Misses.

  • Parent-to-child relationship queries, aggregate functions and compound address or geolocation fields are not supported; child-to-parent fields are.
  • File bodies: Salesforce's Bulk API 2.0 query pages do not cover base64 file fields, so files come through the REST API.
  • LIMIT and ORDER BY turn off PK chunking and can make large queries time out.

Limits. 10,000 query jobs and 1 TB of query results per rolling 24 hours, according to Salesforce's Bulk API limits. Results can be retrieved for 7 days after the job completes.

Use it when the tables are large and someone can script jobs and collect results within 7 days.

6. REST and SOAP API

What it is. Salesforce's standard APIs, which read records, related records and files one request at a time.

Who can use it. Orgs with API access, through a user with the API Enabled permission.

Built for. Files, records kept with their related records, and moves into another platform.

Includes.

  • File bodies. Salesforce's REST Blob Get resource returns binary data for Attachment, ContentNote, ContentVersion, Document and Note records. Each file is its own request; Blob Get cannot run inside a Composite API request.
  • The right files per record: find them through ContentDocumentLink, then download the ContentVersion. Salesforce warns that ContentVersion queries without an ID do not return every file a user can reach.
  • Deleted and archived rows: SOAP queryAll() retrieves "records that have been deleted or archived"; filter on isDeleted and isArchived.
  • Original email dates in EmailMessage MessageDate.

Misses. Nothing in principle; the constraint is calls.

Limits.

  • Enterprise Edition (and Professional with API access): 100,000 calls per rolling 24 hours plus 1,000 per Salesforce licence. Salesforce's example: 15 licences give 115,000.
  • Unlimited and Performance: 5,000 calls per Salesforce licence. Developer Edition: 15,000 a day.
  • 25 concurrent requests lasting 20 seconds or longer on production orgs and sandboxes. Calls from installed managed packages count against the same allocation.

Use it when you need files, need related records kept together, or are moving the data.

What does every Salesforce export route miss?

Four things decide whether a copy is complete. Check each before you trust it.

  • Archived activities. Salesforce archives Events that ended, and closed Tasks due or created, more than 365 days ago. They are not in reports and are not copied into new or refreshed sandboxes. Export All, Bulk API 2.0 queryAll and SOAP queryAll() are the routes documented as returning them.
  • Field history. Without Field Audit Trail, Salesforce keeps field history for up to 18 months, and up to 24 months through the API; it recommends Data Loader or queryAll() for history 18 to 24 months old. For long text fields (over 255 characters), history records only that a change happened, not the values.
  • Field Audit Trail data. With a Shield or Field Audit Trail licence, history is kept until deleted, for up to 200 fields per object, in the FieldHistoryArchive big object. Salesforce lists its access as API only.
  • Configuration. Flows, workflow rules and Apex triggers are metadata, not records. None of the six routes exports them as data.

Moving cases out of Service Cloud raises its own questions about comments, emails and Case History; our Salesforce case export plan covers them.

When do you not need a managed migration?

Often. If Salesforce stays and you need a copy, the Data Export Service and report export are enough, and neither needs a partner. If you are archiving into a data warehouse and have a developer, Bulk API 2.0 with queryAll gets you the tables. If you are moving a flat list of contacts or accounts with no activities, files or history, a CSV and the destination's importer will do.

You need more than an export when the data is going into another platform with its relationships intact: emails, comments and files rejoined to the right record, original dates and owners kept, and deleted or archived rows handled on purpose.

Which Salesforce export should you use for which job?

Match the route to the job:

Your jobUseWhy
Full backup before a renewal or licence endData Export Service, files tickedNo code, every object, files included
A list for a spreadsheet or another teamReport export, Details Only as CSVNo row limit on CSV
One object as a CSV, every nightData Loader Export from the Windows command lineSalesforce documents nightly scheduled extractions
Closed activities older than a year, or deleted recordsData Loader Export AllReturns archived and soft-deleted rows
Millions of rows for a data warehouseBulk API 2.0 with queryAllAutomatic chunking; 1 TB of results a day
Field history before it ages outBulk API 2.0 or Data Loader on the History objectsKept 18 to 24 months without Field Audit Trail
Files, or records with their emails and commentsREST API, alongside Bulk API 2.0Reads each file body per record
Moving to another platformAPI-based migration, tested on a sampleKeeps relationships, dates and owners

If you are moving, the next read depends on where: the Salesforce to HubSpot migration page, the Salesforce to Dynamics 365 Sales migration page, or, for Service Cloud cases going to Zendesk, how Salesforce cases, emails and files become Zendesk tickets. Details by product are on the Salesforce Sales Cloud and Salesforce Service Cloud platform pages, and checking a copy against the source is covered in our guide to data migration validation.

Facts checked November 17, 2026 from Salesforce Help: Export Backup Data from Salesforce, Salesforce Help: Choosing a Method for Importing Data, Salesforce Data Loader Guide (Version 68.0, Winter '27, PDF), Salesforce Help: Export a Report, Salesforce Developer Limits: API Request Limits and Allocations, Salesforce Developer Limits: Bulk API and Bulk API 2.0, Salesforce Bulk API 2.0 Developer Guide, Salesforce Bulk API 2.0 Developer Guide: Understanding Bulk API 2.0 Query, Salesforce Bulk API 2.0 Developer Guide: Create a Query Job, Salesforce SOAP API Developer Guide: queryAll(), Salesforce REST API Developer Guide: Get Blob Data, Salesforce Help: Work with Archived Activities, Salesforce Help: Field History Tracking Overview, Salesforce Help: Field Audit Trail, Salesforce Object Reference: ContentVersion, Salesforce Object Reference: ContentDocumentLink, Salesforce SOAP API: End-of-Life Policy and Salesforce Sales Pricing. No vendor paid for this article. How we research

Salesforce data export FAQ

How do I export all my Salesforce data?

Combine routes. Run the Data Export Service with both "Include" options ticked for a full backup with files. Add Data Loader Export All, or Bulk API 2.0 with queryAll, for soft-deleted records and archived Tasks and Events. Export the History objects for field history. Formula and roll-up fields are not in the backup, so record their definitions.

How often can you run the Salesforce Data Export Service?

Enterprise, Performance and Unlimited Editions can export weekly; every edition except Database.com can export monthly. Manual runs are allowed once every 7 days for weekly export and every 29 days for monthly. Professional and Developer Editions export only every 29 days, and Salesforce does not guarantee when an export completes.

Does Data Loader export attachments and files?

No. Salesforce's Data Loader Guide says Data Loader does not support exporting attachments and suggests the weekly Data Export instead. Data Loader uses base64 fields only to upload attachments and Salesforce CRM Content. For file bodies by API, Salesforce's REST Blob Get resource returns each ContentVersion or Attachment, one request per file.

How do I export deleted or archived Salesforce records?

Use Data Loader's Export All button, the extract_all command-line operation, a Bulk API 2.0 job with operation queryAll, or SOAP queryAll(). Salesforce documents each as returning soft-deleted records and archived Tasks and Events. Reports never include archived activities, and a normal Data Loader Export skips soft-deleted records.

Why are formula fields missing from my Salesforce backup?

The Data Export Service always excludes formula and roll-up summary fields, according to Salesforce's Help. They are calculated from other fields, so the backup keeps only the inputs. Before you leave, list each formula's definition and rebuild it as a calculated field in the destination, then compare a sample of results.

How long does Salesforce keep field history?

Without Field Audit Trail, Salesforce keeps field history for up to 18 months, and up to 24 months through the API; it suggests Data Loader or queryAll() for history 18 to 24 months old. With Field Audit Trail, history stays in the FieldHistoryArchive big object until deleted, and Salesforce lists its access as API only.

Written by

Ayush Bothra

Founding Member, MigrateX

Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.