---
title: "Data Import Wizard vs Data Loader for a CRM migration"
description: "The Import Wizard handles 50,000 records and a short object list; Data Loader handles any object and up to 150M records. Which one a migration needs."
url: "https://flitstack.ai/answers/salesforce-data-import-wizard-vs-data-loader"
---

# 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.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Ask us about your migration ](https://flitstack.ai/contact) [Read the full guide →](https://flitstack.ai/guides/salesforce-data-loader)

## Side by side

|                 | Data Import Wizard                                                                           | Data Loader                                                       |
| --------------- | -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Where it runs   | In the browser, inside Setup                                                                 | Desktop app (Windows, macOS); command line on Windows only        |
| Records per job | Up to 50,000                                                                                 | Up to 150 million with Bulk API 2.0                               |
| Objects         | Accounts, contacts, leads, solutions, person accounts, campaign members, custom objects      | Any object, including opportunities, tasks, events, EmailMessage  |
| Not supported   | Opportunities, cases, campaigns, contracts, products, assets, documents                      | Nothing at the object level; field-level security still applies   |
| Matching        | Built-in matching for contacts, leads and accounts (Salesforce ID, name, email, external ID) | Upsert on an external ID field                                    |
| Files           | CSV, up to 100 MB                                                                            | CSV; large jobs split into batches                                |
| Created dates   | Not supported                                                                                | Supported 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](https://flitstack.ai/guides/salesforce-data-loader) for doing it yourself.

![Aditya Kumar](https://flitstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://flitstack.ai/about/aditya-kumar)

Founder, FlitStack AI

Aditya Kumar is the founder of FlitStack AI and Jetstack AI, both built at Ambrstack. FlitStack AI migrates CRM and business data between platforms; Jetstack AI is the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about CRM data, migrations, HubSpot architecture and automation from the work of building them.

[More from Aditya](https://flitstack.ai/about/aditya-kumar) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

On this page

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.

## Related

### [Salesforce Data Loader vs Data Import Wizard vs dataloader.io: which should you use?](https://flitstack.ai/guides/salesforce-data-loader)

[Read →](https://flitstack.ai/guides/salesforce-data-loader)

### [Migrate to Salesforce](https://flitstack.ai/migrations/crm/salesforce-sales-cloud)

[Read →](https://flitstack.ai/migrations/crm/salesforce-sales-cloud)

### [HubSpot to Salesforce migration](https://flitstack.ai/migrations/crm/hubspot/to/salesforce-sales-cloud)

[Read →](https://flitstack.ai/migrations/crm/hubspot/to/salesforce-sales-cloud)

### [Zoho CRM to Salesforce migration](https://flitstack.ai/migrations/crm/zoho-crm/to/salesforce-sales-cloud)

[Read →](https://flitstack.ai/migrations/crm/zoho-crm/to/salesforce-sales-cloud)

## Sources

1. [Salesforce Trailhead: Import data (Data Import Wizard and Data Loader)](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_data_management/lex_implementation_data_import)
2. [Salesforce Help: Data Import Wizard limits](https://help.salesforce.com/s/articleView?id=sf.import_limits.htm\&language=en_US\&type=5)
3. [Salesforce Help: Choosing a method for importing data](https://help.salesforce.com/s/articleView?id=import_which_data_import_tool.htm\&language=en_US\&type=5)
4. [Salesforce Developers: Data Loader command-line parameters](https://developer.salesforce.com/docs/platform/data-loader-impl/guide/loader-params.html)
5. [Salesforce Help: Enable Set Audit Fields upon Record Creation](https://help.salesforce.com/s/articleView?id=000386699\&language=en_US\&type=1)

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](https://flitstack.ai/contact)
