Salesforce Data Loader is the standard Salesforce tool for importing, exporting, updating, and deleting large volumes of CRM data. While the Salesforce UI’s Import Wizard handles small CSV imports (up to 50,000 records), Data Loader handles volumes from 50,000 to 150 million records, supports all standard and custom objects, and enables operations (hard delete, export all) unavailable in the standard UI. Every Salesforce administrator who manages data migrations, bulk updates, or regular data exports needs to understand how Data Loader works and when to use it.
When the process is defined, imports and exports become easier to repeat without surprises.
Bulk operations should feel deliberate, not risky.
A proper setup also reduces the chance of avoidable errors during bulk changes.
It is especially valuable when the job needs to be repeatable and accurate rather than fast and improvised.
For teams that do recurring data maintenance, that control is hard to replace.
The real advantage is control: admins can decide what comes in, what goes out, and how the mapping works before the action runs.
That makes it one of the most important utility tools in Salesforce administration.
Salesforce Data Loader is useful when teams need to import or export data in bulk rather than one record at a time. It gives admins a practical way to move large sets of data when the task is too big for manual updates.
Data Loader vs Import Wizard: When to Use Which
| Scenario | Use Data Loader | Use Import Wizard |
|---|---|---|
| Record volume | Up to 150 million records | Up to 50,000 records |
| Objects supported | All standard and custom objects | Leads, Contacts, Accounts, Opportunities, custom objects only |
| Operations | Insert, Update, Upsert, Delete, Hard Delete, Export, Export All | Insert, Update, Upsert only |
| Automation/scheduling | Yes (command-line mode) | No |
| Technical complexity | Moderate (requires field mapping, login configuration) | Low (wizard-guided) |
Installing and Configuring Data Loader
Salesforce Data Loader is a Java-based desktop application available for Windows and macOS. As of Spring 2021, Data Loader requires Java 11 or later (OpenJDK is recommended).
To download and install:
- In Salesforce: Setup ? Data ? Data Loader
- Download the platform-appropriate installer (Windows .exe or macOS .dmg)
- Install Data Loader and launch it
- Provide your Salesforce login credentials (or configure OAuth login for improved security – not Username/Password flow)
For production org access, Data Loader connects to https://login.salesforce.com. For sandbox org access, change the server to https://test.salesforce.com in Data Loader settings.
Data Loader Operations
Insert
Creates new records in Salesforce from a CSV file. Each row in the CSV becomes a new Salesforce record. Required fields must be included in the CSV; the Salesforce ID field should not be included (Salesforce generates the ID for new records).
Best practice: always run a test Insert in a sandbox with a small sample (100 records) before running a large Insert in production. Check the error log file that Data Loader produces to verify the field mappings are correct before committing to the full volume.
Update
Updates existing Salesforce records from a CSV. The CSV must include the Salesforce ID column (the 18-character record ID) to identify which record to update. All other columns in the CSV update the corresponding fields on the matching record. Fields not included in the CSV are left unchanged.
Upsert
The most commonly used operation for data migrations and integrations: Upsert combines Insert and Update in a single operation. For each row in the CSV, Salesforce checks if a record with the specified External ID field value already exists. If it does, the record is updated. If not, a new record is created. External IDs must be custom fields marked as External ID in Salesforce’s field setup.
Upsert is essential for data synchronisation: it prevents duplicate creation when the source system sends a record that might already exist in Salesforce (because it was previously imported) and updates existing records instead.
Delete and Hard Delete
Delete moves records to the Salesforce Recycle Bin (recoverable for 15 days). Hard Delete permanently removes records without moving them to the Recycle Bin – use with caution. Both operations require the Salesforce ID column in the CSV. Hard Delete requires the “Bulk API Hard Delete” permission and should only be used when permanent removal is required (GDPR deletion requests, removing test data from production).
Export and Export All
Export queries Salesforce using SOQL (Salesforce Object Query Language) and exports the results to a CSV file. Export All includes records that are in the Recycle Bin (deleted records) – useful for data auditing and recovery. Export is limited to the records the logged-in user can see based on their profile and sharing settings.
Field Mapping
After selecting the CSV file and the target Salesforce object, Data Loader requires you to map each column in the CSV to a Salesforce field. The mapping screen shows the CSV headers on the left and Salesforce field API names on the right. Data Loader can auto-map fields when the CSV header matches the Salesforce API field name exactly (case-insensitive).
Save the field mapping as a .sdl file after configuring it – saved mappings can be reloaded for repeated operations, saving re-configuration time for recurring imports or exports.
Batch Size and the Bulk API
Data Loader uses Salesforce’s Bulk API for operations above the standard API batch limit. The Bulk API processes records asynchronously in batches – allowing very large volumes to be processed without hitting API limits. The default batch size for Bulk API operations is 2,000 records per batch. For most use cases, the default is appropriate. For very large imports (millions of records), increasing the batch size to 10,000-50,000 can improve throughput if the source data is clean and consistent.
The Bulk API 2.0 (available in Data Loader version 41+) simplifies large-volume operations with improved error handling and status tracking.
Error Handling
After each Data Loader operation, two output files are produced:
- Success file: records successfully processed, with their Salesforce IDs
- Error file: records that failed, with the error message explaining why (required field missing, validation rule violation, duplicate rule triggered, field value too long, etc.)
Always review the error file before considering an operation complete. For large imports with many errors, fix the error file CSV and re-run with just the failed records – Data Loader processes only the rows in the error file without re-processing the successful ones.
Command-Line Mode for Automation
Data Loader can be run in command-line (batch) mode for scheduled or automated operations. Create a process-conf.xml configuration file specifying the operation, object, CSV file, field mapping, and login credentials, then run process.bat (Windows) or process.sh (Mac/Linux) from the command line. This enables scheduled nightly data exports, automated data synchronisation, and integration pipelines without manual Data Loader UI interaction.
Alternatives to Data Loader
For Salesforce administrators who find Data Loader’s Java application cumbersome, alternatives include:
- Salesforce’s own Import Wizard: for volumes under 50,000 with simple objects
- Dataloader.io: a browser-based data loader that connects to Salesforce via OAuth – no Java installation required, with a scheduling feature in paid tiers
- Coupler.io / Skyvia: cloud-based data integration tools for recurring Salesforce data operations
- MuleSoft or Boomi: for enterprise integration scenarios requiring ongoing data synchronisation with other systems
Is Salesforce easy to learn for beginners?
Salesforce has a learning curve, but its official free training platform Salesforce Trailhead provides structured paths from beginner to advanced. Most users handle day-to-day tasks within 2-4 weeks. Admin and developer skills take 3-6 months to develop proficiently.
What are the biggest Salesforce mistakes to avoid?
Top mistakes include: over-customizing before understanding your process, skipping user training, importing dirty data without cleansing, and not establishing naming conventions. Avoid these four and your implementation will be significantly more successful.
How often does Salesforce release new features?
Salesforce releases major updates three times per year in Spring, Summer, and Winter releases. Salesforce previews upcoming features in sandbox environments 4-6 weeks before each release.
Does Salesforce offer customer support?
Yes. Support is available via chat, email, and phone depending on your plan tier. Enterprise plans include dedicated customer success managers. The Salesforce Trailblazer Community offers extensive peer and official support.
Can Salesforce integrate with other business tools?
Yes. Salesforce AppExchange offers 7,000+ apps. Common integrations include Slack, DocuSign, Zoom, and ERP systems via MuleSoft.
The best Data Loader workflow is the one that keeps bulk actions deliberate. If the import or export is rushed, the risk of bad data goes up fast.
Common Challenges with Salesforce Data Loader and How to Solve Them
Problem: Getting Your Team to Consistently Use Salesforce
Adoption gaps occur when teams revert to old habits after initial training. Fix: Identify the 2-3 daily workflows where Salesforce adds the most value for your specific role. Focus training on those workflows first. Use Salesforce in-app guidance to provide contextual help at the moment of need rather than relying solely on one-time classroom training.
Problem: CRM Data Quality Degrading Over Time
CRM data decays at approximately 30% per year as contacts change roles and companies. Fix: Schedule a quarterly data quality audit. Use Salesforce deduplication tools to merge duplicate records. Establish data entry standards enforced through validation rules. Consider a data enrichment tool like Clearbit or ZoomInfo to update stale records automatically.
Problem: Salesforce Reports Not Matching Actual Business Results
Reports are only as accurate as the data entered. Discrepancies between CRM reports and actual revenue indicate data entry gaps. Fix: Audit closed-won records against actual invoices monthly. Make CRM data the source of truth for commission calculations so reps have a direct incentive to enter accurate data.