
Andrew Hanna

Andrew Hanna

The short answer: use the Data Import Wizard for simple loads under 50,000 records, Data Loader for larger or scheduled loads up to 150 million records, and an org-to-org tool when you need to copy related records between production and sandboxes. That last job, the one Salesforce teams do most often, is where native tools stop and SFDMU or a DevOps platform's data deployment takes over.
They are tools that insert, update, upsert or export records in a Salesforce org at a volume or complexity that manual entry cannot handle. They fall into four groups:
Use the Data Import Wizard. It is built into Setup, needs no install and handles up to 50,000 records at a time. Watch out: it supports a limited set of objects and gives little control over relationships.
Use Data Loader. According to Trailhead, it handles 50,000 to 150 million records, objects the wizard does not support, and scheduled loads such as nightly imports. Watch out: it works from CSV files on a local machine, so exports, mappings and error files live outside Salesforce.
Use SFDMU or a DevOps data deployment. Watch out: plain file loaders break lookups between orgs, because record IDs differ in every org.
Use an ETL or integration platform. That is integration rather than migration, and it needs its own monitoring.
For the end-to-end process around whichever tool you pick, follow our step-by-step data migration guide.
Both come with Salesforce and both are file-based. The wizard suits admins importing Accounts, Contacts, Leads or custom object records from a spreadsheet. Data Loader suits volume and can use the Bulk API for large jobs. The Trailhead large data volumes module recommends the Bulk API for anything from a few thousand to millions of records, and loading parents before children.
Where they stop: neither knows about your release process. There is no dependency check across orgs, no masking, and no record of which data shipped with which release.
export.json file. It runs locally, so someone on the team owns the
scripts.
If the goal is a test-ready sandbox rather than a one-time move, see how to seed a Salesforce sandbox with realistic data. If your org is moving to Hyperforce, that is Salesforce moving your org's infrastructure, not you moving records, so work from our Hyperforce migration checklist instead.
Open Migrate Data in the Data Management tab, pick a source and a destination org, turn on PII masking if you need it, start the migration, then review its progress and results. The Migration Details page shows the execution timeline, the Migrated Objects table filters by success and failed status, and built-in dependency checks reduce migration surprises. Full steps are in the data migration and masking guide.
Two things matter in a DevOps workflow. Migrate Data is an action in the visual automation flow builder, so metadata and data move in the same release flow. And sandbox seeding runs as part of environment setup and release pipelines, so refreshed sandboxes and scratch orgs come back populated without a manual script run. Before a large write, the Backups view captures a known-good state you can restore from, as described in backup and restore. See data deployment for how it fits the pipeline. Deploy data is on every plan, including the free Essentials plan.
What is the best free data migration tool for Salesforce?
Data Loader for file-based loads and SFDMU for org-to-org moves. Neither carries an extra license cost, and SFDMU needs the Salesforce CLI.
How many records can Data Loader handle?
Up to 150 million records, per Trailhead. The Data Import Wizard handles up to 50,000 records at a time.
Can I migrate data between sandboxes with Data Loader?
Only by exporting and reimporting CSVs and remapping lookups by hand. An org-to-org tool handles the relationships for you.
Do Salesforce data migration tools mask PII?
The native file loaders do not. Salesforce Data Mask & Seed, Copado, Gearset and Serpent all offer masking.
More how-to playbooks for Salesforce DevOps teams live in SF Guides.
Commitment free!