Skip to content
Get a quote

Salesforce Data Import Wizard vs Data Loader

Short answer

For a full CRM migration, use Data Loader. The Data Import Wizard caps each import at 50,000 records and can't import opportunities, cases, campaigns or products. Data Loader works with any object, loads up to 150 million records through Bulk API 2.0 and can keep created dates. Use the Wizard for small contact or lead loads.

By

Side by side

Data Import WizardData Loader
Where it runsIn the browser, inside SetupDesktop app (Windows, macOS); command line on Windows only
Records per jobUp to 50,000Up to 150 million with Bulk API 2.0
ObjectsAccounts, contacts, leads, solutions, person accounts, campaign members, custom objectsAny object, including opportunities, tasks, events, EmailMessage
Not supportedOpportunities, cases, campaigns, contracts, products, assets, documentsNothing at the object level; field-level security still applies
MatchingBuilt-in matching for contacts, leads and accounts (Salesforce ID, name, email, external ID)Upsert on an external ID field
FilesCSV, up to 100 MBCSV; large jobs split into batches
Created datesNot supportedSupported when “Set Audit Fields upon Record Creation” is enabled

What the native tools do / where they stop

Both tools load files into one object at a time. Neither one reads from your old CRM, transforms values or keeps parent and child records linked across objects. You do that in the CSVs. Salesforce’s own guidance says to go to a partner or an AgentExchange product for anything larger than Data Loader handles.

What the docs don’t spell out is the load order. A migration is a sequence of Data Loader jobs, and each one depends on the IDs the previous one returned:

  1. Users (created in Setup, not loaded as data) and any record types.
  2. Accounts, upserted on a Legacy_ID__c external ID field.
  3. Contacts, with the account looked up through its external ID.
  4. Opportunities, then opportunity contact roles.
  5. Tasks and events, with WhoId and WhatId resolved from the success files.
  6. EmailMessage records (insert only via the API) and their EmailMessageRelation rows.
  7. Files and attachments, last.

If you skip the external IDs, every step means matching record IDs by hand in a spreadsheet. A rerun then creates duplicates.

Rules of thumb

  • Under 50,000 contacts or leads, no history: the Wizard is fine.
  • Opportunities, activities, custom objects or more than 50,000 rows: Data Loader.
  • You need the original created dates: Data Loader with audit fields, and only on insert.
  • Several source systems, several million activities, or attachments: script it against the Bulk API, or use a migration tool.

Where FlitStack AI fits

FlitStack AI loads Salesforce through its APIs in the right order: external IDs, lookups and audit fields included, with a sample run and rollback. See the Salesforce Data Loader guide for doing it yourself.

Questions, answered

A few useful answers.

Can the Data Import Wizard import opportunities?

No. Salesforce lists opportunities among the objects the Wizard can't import, along with assets, cases, campaigns, contracts, documents and products. Use Data Loader or the API.

Does Data Loader run on a Mac?

The desktop app runs on Windows and macOS. The command-line interface, which you'd use for scheduled or scripted loads, is supported on Windows only.

Do validation rules and flows run during a load?

Yes, with both tools. Records that fail a validation rule are rejected, and record-triggered automation fires. Admins often deactivate both for the load window and turn them back on afterwards.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote