Salesforce has three native ways to get data out: the Data Export Service for a full backup, report exports for filtered lists, and Data Loader for one object at a time with exactly the fields you choose. Which one you need depends on whether you want a backup, a spreadsheet, or the raw material for a migration. This guide covers all three, with their limits from Salesforce’s documentation, then what a migration needs on top.
Which Salesforce export method should I use?
| Goal | Method | What you get |
|---|---|---|
| Back up everything, including files | Data Export Service | Zip of CSV files per object, optional attachments and documents |
| A filtered list for finance or sales ops | Report export | CSV or XLSX of the report’s rows |
| One object, specific fields, any time | Data Loader Export | CSV from a SOQL query you build |
| Deleted and archived records too | Data Loader Export All | Adds soft-deleted records and archived activities |
| Move to another CRM | API extraction plus mapping | Records with relationships, activities, files and owners |
How do I use the Salesforce Data Export Service?
The Data Export Service is the backup option. Trailhead describes it as producing a set of CSV files in a zip archive, emailed to you when ready.
- In Setup, enter Data Export in Quick Find, select Data Export, then Export Now or Schedule Export.
- Choose the file encoding.
- Tick the options for images, documents and attachments if you want files included.
- Optionally replace carriage returns with spaces, which helps if you will open the CSVs in a spreadsheet.
- For a schedule, choose the frequency, start and end dates and time of day.
- Under Exported Data, choose the objects. Salesforce suggests Include all data if you are unsure.
- Save. When the email arrives, download every zip file.
Limits to plan around:
- Frequency: manual exports once every 7 days (weekly) or 29 days (monthly). Weekly exports are available in Enterprise, Performance and Unlimited. Professional and Developer editions get backup files only every 29 days.
- Timing: Salesforce says it can’t guarantee when an export will complete.
- Retention: zip files are deleted 48 hours after the email is sent.
- Size: large exports are split into multiple files.
The Data Export Service is the only native route that includes attachments in bulk, so it is the one to run before a migration even if you also use Data Loader.
How do I export a Salesforce report?
Report exports suit lists people will work with in a spreadsheet, not migrations.
- From the Reports tab or the report run page, open the dropdown and choose Export.
- Pick Formatted Report to keep the header, groupings and filters, or Details Only for one row per record.
- Choose the format and click Export.
Salesforce’s limits for Lightning Experience: Details Only to XLS or CSV exports an unlimited number of rows and columns (your spreadsheet tool still has its own limits, commonly 1,048,576 rows). Formatted exports of tabular or summary reports, and Details Only exports to XLSX, are capped at 100,000 rows and 100 columns, with long text and rich text truncated to 255 characters. Formatted matrix reports stop at 2,000 rows.
How do I export Salesforce data with Data Loader?
Data Loader is a free client application from Salesforce. Its docs list it for Enterprise, Performance, Unlimited and Developer editions. To export:
- Open Data Loader and click Export, or Export All to include archived activity records and soft-deleted records.
- Log in and choose the object. Select Show all objects if yours isn’t listed.
- Choose the CSV file to write to.
- Build the SOQL query: pick fields, add conditions, review the query.
- Click Finish. Data Loader writes the CSV and shows a summary.
Things the docs call out:
- Relationship queries work for parent fields (for example
Account.Nameon contacts) and are case-sensitive. - Nested queries, child-object queries and polymorphic relationship queries are not supported.
- Compound fields cause errors; export their components instead.
- Data Loader does not export attachments. Use the weekly export for those.
What does a Salesforce export leave out for a migration?
Every native export gives you files keyed by Salesforce IDs. That is fine for a backup and hard work for a migration. What you still have to do:
- Rebuild relationships. Contacts reference
AccountId, opportunities reference accounts and contact roles, tasks referenceWhoIdandWhatId. In the new CRM every one of those has to be translated into a new record ID or association. - Translate the data model. Salesforce’s Lead object, record types and opportunity stages rarely have a one-to-one match. HubSpot, for example, has no separate lead object by default and no record types.
- Match owners. Owner fields hold Salesforce user IDs, which mean nothing elsewhere until you map them to users.
- Keep activity history. Emails, calls, events and notes are separate objects. They need their original dates and the right parent record.
- Move files. Attachments come out in the zip with IDs you must link back to the right records.
- Handle the gap. Users keep working after the export. Anything changed between export and go-live needs a second pass.
What should I keep from Salesforce besides data?
Before the org is switched off, document what doesn’t export as records: page layouts and record types per profile, validation rules, flows and any remaining Workflow Rules or processes, approval processes, report and dashboard definitions, and the list of connected apps and integrations. These define how the team works and become the build spec for the new CRM.
Should I export first, or migrate straight from Salesforce?
Export a full Data Export Service backup first, whatever you decide. It is your safety net and costs nothing.
For the migration itself, files are workable when you have a few objects, no activity history to keep and time to rebuild links by hand. Extracting through the API is better when the source is large, has history and custom objects, or needs a short cutover.
When to bring in FlitStack AI
FlitStack AI is a data-migration platform sold as software plus a done-for-you service. It connects to Salesforce through the API, so there is no 48-hour download window to manage. It maps objects and fields to the destination with AI-proposed mappings you review, validates every record, keeps timestamps and owners, and offers one-click rollback. A delta migration catches records changed during cutover.
See Salesforce to HubSpot or Salesforce to Zoho CRM, or the Salesforce migration hub. Loading into Salesforce instead? Read Data Loader vs Data Import Wizard. For a quote, book a free scoping call.