Both load CSVs into Salesforce. The size of the job and the depth of features decide which one fits.
Side-by-side
| Feature | Data Loader | Import Wizard |
|---|---|---|
| Max records per job | 5,000,000 | 50,000 |
| Operations | Insert, Update, Upsert, Delete, Hard Delete, Export, Export All | Add (Insert), Update, Upsert |
| Object support | All standard + custom | Accounts/Contacts, Leads, Solutions, Campaign Members, Person Accounts, custom |
| Export records? | Yes | No |
| Delete records? | Yes (soft + hard delete) | No |
| Where it runs | Desktop app (Java) + new web version + CLI | Browser, inside Salesforce Setup |
| Installation | Required (desktop) | None — runs in Setup |
| Scheduling | Yes (via CLI) | No |
| API used | SOAP API or Bulk API | Bulk API (server-side) |
| Batch size control | Yes (200 SOAP / 10,000 Bulk) | No (managed by server) |
| Duplicate handling | Via org duplicate rules only | Built-in dedup UI for Leads/Accounts/Contacts |
| Trigger auto-assignment rules | Through API headers (not Data Loader GUI) | Yes, checkbox in the UI |
| Edition requirement | Enterprise / Performance / Unlimited / Developer / Database.com | All editions, including Essentials/Professional |
When each one is the right pick
Use the Import Wizard when:
- You have under 50,000 records.
- The object is one the wizard supports.
- You want a simple, browser-based flow with built-in duplicate matching.
- You’re on an edition without full API access (Professional, Essentials).
- You need to fire auto-assignment rules through a clicky UI.
Use Data Loader when:
- You have over 50,000 records, or expect to.
- You need to load to an object the wizard doesn’t support (Opportunities, Cases, Products, Quotes, most platform objects).
- You need delete, hard delete, or export.
- You want scheduled jobs through the CLI.
- You’re building an integration, not running a one-off admin task.
- You need fine control over batch size, Bulk API mode, and serial vs parallel processing.
The narrowest difference that matters in interviews
If an interviewer wants one differentiator, give them: “Data Loader handles every object and every operation including delete and export, up to 5 million records, with a CLI for scheduling. The Import Wizard is browser-only, caps at 50,000 records, supports only a handful of objects, and can’t delete or export.”
A real-world rule
If you find yourself running the same Import Wizard load every month and wishing it was scheduled, that’s the signal to migrate the job to a Data Loader CLI batch. The 50,000-record cap is rarely the reason — the lack of automation usually is.
Don’t forget the web Data Loader
Salesforce now ships a third tool — the web-based Data Loader in Setup — that splits the difference: in-browser like the wizard, but more capable. It’s becoming the default for many admins. In an interview, if relevant, mention that the landscape now has three tools, not two.
Verified against: Salesforce Help — Choose Between the Data Import Wizard and Data Loader, Data Loader Guide, Metadata API Developer Guide. Last reviewed 2026-05-17 for Spring ‘26 release.