Salesforce doesn’t back up data automatically. This means critical business information sits unprotected in Salesforce every day unless you take proactive steps to back it up. As a result, knowing how to export Salesforce data becomes a fundamental part of any data protection strategy.

Data loss happens more often than most teams expect. Routine maintenance can wipe out records. Deployments fail and corrupt object structures. Integration errors overwrite key values. Even simple human mistakes can delete entire datasets. Beyond backups, many organizations need to export data for audits, compliance reports, or Salesforce-to-Salesforce migrations.

This guide breaks down every method for exporting Salesforce data, from quick manual tools to advanced automation. Each approach comes with benefits and trade-offs in control, security, and compliance coverage that should be carefully considered.

Yes, there are several ways to export data from Salesforce. The native options are the Data Export Service (full, scheduled CSV backups), Data Loader (large, filtered exports and attachments), Reports (business-ready CSV or Excel), Workbench (quick SOQL-based pulls), and the REST and Bulk APIs (automated, enterprise-scale exports). The right choice depends on data volume, how often you export, and whether you need a true backup. The table below compares them at a glance.

Comparing Salesforce Data Export Methods

Each method fits a different mix of data volume, frequency, and technical comfort. Use this comparison to pick a starting point, then follow the step-by-step instructions further down.

5 Ways to Export Data from Salesforce

Salesforce offers multiple native export tools, each designed for specific use cases and technical skill levels. Choosing the right method depends on the type of data, export frequency, compliance requirements, and available internal resources.

Manual methods allow full control over what gets exported and when, which is ideal for ad-hoc reporting or one-time data pulls. Automated options reduce human error and run on set schedules, though native limitations exist around flexibility and frequency.

Most export needs fall into three categories:

1. Standard record data
2. Files and attachments
3. Metadata configurations

Not all tools support each category equally. Some are optimized for object-level data, while others are optimized for file storage, and a few support metadata extraction.

1. Use Salesforce Data Export Service for Full Data Exports

The Salesforce Data Export Service is the most accessible built-in tool for exporting data, designed for users who want a straightforward, no-frills solution. This web-based tool is particularly suited for small businesses or teams with occasional export needs and minimal technical know-how.

Export Process

1. Access the tool by navigating to Setup and searching for “Data Export” in the Quick Find box.
2. Choose between Export Now (for immediate, ad-hoc exports) or Schedule Export (for recurring exports on a weekly or monthly basis, depending on your Salesforce edition).
3. Select the Salesforce objects you wish to export (for example, Accounts, Contacts, Leads) and configure options such as file encoding, inclusion of attachments, and whether to replace carriage returns with spaces for compatibility with other systems.
4. Initiate the export. Salesforce prepares a ZIP archive containing CSV files for each selected object. You’ll receive an email with a download link when the export is ready.
5. Download the files within 48 hours, as Salesforce deletes export files after this period.

Limitations

• Scheduling is inflexible: only weekly or monthly schedules are available, and the timing of export completion is not guaranteed.
• File size restrictions: each ZIP file is capped at 512MB; larger datasets are split across multiple files.
• Data structure: exports are “flattened,” meaning relationships between records (such as parent-child links) are not preserved.
• Feature access: automated scheduling is only available to certain Salesforce editions (Enterprise, Performance, Unlimited).

Best for: small-scale backups, periodic compliance reviews, or one-off data migrations, where ease of use is more important than advanced customization.

2. Use Salesforce Data Loader for More Control

Salesforce Data Loader is a powerful client application for organizations that need to handle larger datasets or require more granular control over the export process. It supports both interactive and automated (scripted) exports, making it suitable for advanced users and IT teams.

Export Process

1. Install Data Loader from Salesforce Setup under Apps, Data Management, Data Loader.
2. Choose your preferred mode: the Graphical User Interface (GUI) for interactive, manual exports with drag-and-drop field mapping, or the Command-Line Interface (CLI) for automation and batch processing, which lets you schedule exports using tools like Windows Task Scheduler or cron jobs on Mac and Linux.
3. Authenticate using Salesforce credentials, with OAuth recommended for security.
4. Select the objects and fields to export, and use SOQL queries for advanced filtering.
5. Configure output options (file format, encoding, delimiters).
6. For automation, create scripts to run exports on a schedule, and include logging, error handling, and notifications to monitor success.

Limitations

• Batch and file size limits: each batch can process up to 50,000 records, and each CSV file is capped at 150 MB. Large data sets must be split across multiple batches and files.
• API usage: every export consumes Salesforce API calls, which are subject to daily limits based on your edition. Exceeding these limits halts further exports until the next reset.
• No real-time processing: Data Loader works only in batches and does not support real-time or event-driven exports.
• Automation complexity: scheduling automated exports requires command-line scripting and external schedulers, which may be challenging for non-technical users.
• CSV-only format: only CSV files are supported, requiring strict formatting and manual mapping for each object.

Best for: complex or high-volume exports, regular automated data backups, and environments where advanced filtering, scheduling, and error tracking are critical.

How to Export Attachments from Salesforce Using Data Loader

Standard record exports don’t include the actual files attached to your records. To export attachments from Salesforce using Data Loader, run an export against the file objects directly: query the Attachment object for classic Notes and Attachments, or ContentVersion for Salesforce Files. The Body field returns the file content as a Base64-encoded string, which you then decode to rebuild the original PDFs, images, and documents. This gives you precise, filtered control over which files you pull.

The trade-off is effort: decoding Base64 output and reassembling files is a manual, technical step. When you simply need every file in one pass, the Data Export Service is often the better choice, because selecting “Include images, documents, and attachments” packages the actual files into the export ZIP for you. Use Data Loader when you need targeted or filtered file exports, and the Data Export Service when you want a complete, low-effort capture of all attachments.

3. Use Reports Export for Business-Ready Data

For business users who need quick, formatted access to Salesforce data without technical setup, exporting from Salesforce Reports is the go-to method. This approach is ideal for executive summaries, operational dashboards, and ad hoc team reporting.

Export Process

1. Use Salesforce’s Report Builder to create and customize reports with filters, groupings, and summaries tailored to your business needs.
2. Click Export to download the report in Excel or CSV format, making it easy to share or analyze in other systems.
3. Set up subscriptions to automate recurring report deliveries via email, ensuring teams always have the latest information.

Limitations

• Row limits: standard report exports are capped at 2,000 rows (unless using Printable View).
• Flattened data: exported reports do not include relationships or metadata, just the summarized data.
• Permissions required: users must have the “Run Reports” permission to build and export reports.

Best for: executive-level reporting, team dashboards, and business-friendly exports that don’t require technical configuration or deep data relationships.

4. Use Workbench for Developer-Level Precision

Workbench is a browser-based tool designed for Salesforce admins and developers who need fast, precise, and highly customizable exports. It connects directly to the Salesforce API, making it ideal for advanced queries, troubleshooting, or targeted data pulls.

Export Process

1. Go to workbench.developerforce.com and log in with Salesforce credentials or a session token.
2. Select your environment (Production or Sandbox) and API version.
3. Use the SOQL Query feature to define exactly which records and fields to export.
4. Download the results as a CSV file for further analysis or archiving.

Limitations

• Technical knowledge required: users must be comfortable with SOQL and Salesforce’s data model.
• Manual process: no built-in scheduling or automation, so each export must be initiated manually.
• Not for large or recurring exports: best for one-off, targeted data pulls.

Best for: quick, precise exports, debugging, and on-demand developer tasks where installing additional software isn’t practical.

5. Use REST and Bulk APIs for Automated Salesforce Data Export

For enterprises and organizations building custom integrations or managing large-scale data operations, Salesforce’s REST API and Bulk API offer the most flexible and scalable export options. These APIs enable seamless integration with external systems, data lakes, or analytics platforms.

Export Process

1. Use the REST API for real-time, small-volume exports via HTTP requests.
2. Use the Bulk API for large, asynchronous data transfers, handling millions of records efficiently.
3. Set up authentication (OAuth tokens) and configure API permissions in Salesforce.
4. Craft SOQL queries within your API requests to define the data scope and fields.
5. Process and store the exported data in your external application, data warehouse, or cloud storage.

Limitations

• Developer resources required: setup, integration, and ongoing maintenance demand technical expertise.
• Governor limits: you must manage Salesforce API usage limits and implement robust error handling.
• Higher overhead: more complex configuration and monitoring compared to native tools.

Best for: automated, enterprise-scale data exports, custom application integrations, and continuous syncing with external reporting or analytics systems.

How to Export All Data from Salesforce

When you need a complete copy of your org, the Data Export Service is the most direct route. Go to Setup, search for “Data Export” in the Quick Find box, then choose Export Now for an immediate pull or Schedule Export for a recurring one. Under Exported Data, select “Include all data,” and check “Include images, documents, and attachments” if you need files as well. Salesforce assembles a set of CSV files, emails you a download link, and keeps the ZIP archive available for 48 hours.

Cadence depends on your edition: Enterprise, Performance, and Unlimited can export weekly, while Professional and lower editions are limited to monthly. Keep in mind that a full export is a flattened snapshot. It captures the records but not the relationships, automation, or metadata, so it works as a point-in-time copy rather than a restore-ready backup.

How to Export Salesforce Data to Excel

The quickest way to export Salesforce data to Excel is through Reports. Build a report with the fields and filters you need, click Export, and choose Excel (.xlsx) or CSV. A CSV opens directly in Excel or Google Sheets, and .xlsx preserves basic formatting. For data that lives outside a report, Data Loader and Workbench both produce CSV files that open cleanly in Excel.

Excel is convenient but has limits. Formatted report exports cap at about 2,000 rows, and spreadsheets slow down or truncate well before Salesforce’s record counts get large. For big datasets, export with Data Loader or the Bulk API and load the data into a database or BI tool instead of relying on Excel alone.

Best Practices for Managing Exported Salesforce Data

Exported Salesforce data needs the same level of protection as your production environment. Without proper safeguards, even a routine export can become a liability.

• Use encryption to protect files during transfer and while stored. AES-256 or similar protocols ensure sensitive data isn’t exposed if files are intercepted or misplaced.
• Apply role-based access controls so only authorized team members can view, move, or process exported data. Keep access logs to support compliance reviews.
• Follow clear retention and purge policies based on your industry’s requirements. Set time limits for how long exported files are kept, track export versions when needed, and remove outdated files automatically.
• Maintain documentation for each export process. Include timing, file scope, storage locations, and recovery procedures. This helps during audits and makes internal reviews easier.

These practices close the gaps left by native tools, so every export meets your security and compliance standards.

Limitations of Native Salesforce Export Tools

Native Salesforce export tools serve basic needs but leave major gaps in long-term data protection and operational continuity.

• Lack of real-time or continuous backup: these tools create static snapshots, frozen in time. Any changes, deletions, or corruption between scheduled exports go unrecorded and unrecoverable.
• Limited metadata support: native exports don’t capture validation rules, automation settings, or object relationships in full. CSV files strip away structure, making recovery tedious and error-prone. Rebuilding an org from exports requires manual reconstruction of dependencies.
• Manual workflows introduce operational risk: someone needs to run the export, verify completion, and store the files securely. Missed steps, such as forgotten passwords, failed transfers, and lost files, can derail recovery when it matters most.
• Regulation pressure: SOX, HIPAA, and GDPR require audit trails, verifiable data integrity, and strict access control. Periodic manual exports rarely meet these benchmarks.
• Restoration challenges: native tools don’t offer point-in-time recovery. Teams must rebuild from raw files, often with formatting issues, missing relationships, or outdated content, so downtime increases and data loss compounds.
• Correct ordering: you must know the proper order to restore parent-child record relationships. An automated tool understands these relationships and restores them in the correct order.
• Full export issues: it is difficult to get all the data exported from your Salesforce org. Many export tools don’t export everything, and if you don’t export everything, you can’t restore everything.

These limitations turn native exports into a false sense of security. They might check a box, but they won’t protect your business when real data loss or audit pressure hits. That’s why many organizations turn to automated backup solutions built specifically for Salesforce. But before diving into backup tools, it’s crucial to understand how exports and backups differ, and why your organization likely needs both working together.

Export vs. Backup: Why You Might Need Both

Exports and backups solve different problems. Teams often confuse the two, but relying on one while ignoring the other leaves protection incomplete.

Exports create static snapshots. Quarterly sales data for dashboards, customer lists for marketing analysis, or datasets for migrations all fall under this category. Once generated, that data remains unchanged. This is useful for reporting and planning, but not for recovery.

Backups are continuous systems built for resilience. They capture every change, track every deletion, and provide restore points for the entire environment, including metadata and object relationships. When a failed integration corrupts records or a user deletes accounts by mistake, only a backup can reverse the damage.

The gap becomes clear during disruption. A weekly export can’t recover data lost the day after it ran. It also can’t rebuild dependent fields, restore automation rules, or re-link related objects. Backups fill that gap.

Both tools serve a purpose. Use exports for operational tasks, such as reporting, analysis, and migrations. Use backups for compliance, disaster recovery, and long-term data integrity. A strong data strategy includes both.

Go Beyond Salesforce Data Export with Automated Backup

Manual exports solve short-term problems, such as compliance reports, data migrations, and periodic reviews. But as systems grow and risks multiply, those snapshots become inefficient. One missed export or lost file can mean days of lost records and hours of manual recovery.

Restoring data is the real challenge. Native exports don’t capture metadata, relationships, or custom logic. What comes back is often incomplete, disconnected, or outdated. Rebuilding takes time. Downtime stretches, and teams wait. Automated backup changes the equation.

That’s where Flosum comes in. Flosum’s Backup and Archive offers continuous protection, capturing every change in real time. Data, metadata, and relationships are all preserved and restorable to any point, with no need to piece things together and no risk of missing something critical. What was once a time-consuming task becomes a silent safety net.

To see how automated, in-platform backups can simplify recovery and strengthen compliance, book a demo and explore what Flosum can do behind the scenes.

Frequently Asked Questions