- Salesforce Managed Services
Every Salesforce project eventually hits the same wall. The org is configured, the users are trained, and then someone asks how 400,000 records from the old CRM, 3 spreadsheets, and an ERP are going to get in there without breaking anything. That is where Salesforce data migration tools earn their keep. Some are free and built into the platform, some cost a few hundred dollars a month, and some are enterprise integration platforms that happen to be very good at moving data into Salesforce. Picking the wrong one is expensive in a way that rarely shows up on the invoice: broken lookups, duplicate accounts, and a sales team that stops trusting the CRM in week 2.
This guide covers the 10 Salesforce data migration tools we see most often in real migration work, what each one does well, where each one falls short, and which one fits which scenario. We also flag 2 tools that still appear on most “top 10” lists even though their vendors retired them.
Activity history is the hardest part of a CRM move and the least discussed. It carries the highest record volume in the project, depends on relationships that must exist before it loads, points at users who may have left the company, and touches fields Salesforce protects by default. None of that makes history impossible to move. All of it has to be decided before anyone opens Data Loader.
This Salesforce data migration checklist is built around that specific problem. It covers the full move from another CRM into Salesforce, and at every phase it calls out what history preservation demands that a standard record migration does not. We have run these projects for teams leaving HubSpot, Microsoft Dynamics, Zendesk, Freshdesk, Oracle, and homegrown systems. The pattern holds: the ones that kept their history planned for it in week one, and the ones that lost it found the gap in user acceptance testing with nine days left.
TL;DR
Ten Tools, From Free Wizards to Enterprise Platforms
This guide compares 10 Salesforce data migration tools across the same 8 criteria: Data Import Wizard, Data Loader, Dataloader.io, Salesforce Inspector Reloaded, Skyvia, Jitterbit Harmony, MuleSoft Anypoint, Informatica, Boomi, and Prodly, with real limits, pricing, and gotchas for each one.
Why Picking on Reputation Alone Backfires
Most “top 10” lists still recommend Jitterbit’s retired Cloud Data Loader and the discontinued Talend Open Studio or confuse metadata tools with record loaders. Pick wrong and you inherit broken lookups, duplicate accounts, record-locking errors, and a sales team that stops trusting the CRM.
Match the Scenario First, Then the Tool
Your scenario decides the shortlist: legacy CRM cutover, org-to-org consolidation, sandbox seeding, or ongoing ERP sync. Then success comes from the steps no tool automates, meaning external IDs on every object, parent-to-child load order, sandbox rehearsal, and reconciliation by counts rather than by eye.
What Salesforce Data Migration Tools Actually Do (and What They Don't)
Salesforce data migration tools move records into, out of, or between Salesforce environments. That covers 3 distinct jobs, and most tools only do 1 or 2 of them well:
- Loading records: inserting, updating, upserting, or deleting Accounts, Contacts, Opportunities, Cases, and custom object records from a CSV, a database, or another application.
- Transforming data on the way in: reshaping picklist values, splitting or merging fields, converting date formats, deduplicating, and resolving relationships so a Contact lands under the right Account.
- Keeping systems aligned: running scheduled or real-time syncs during a phased cutover, when both the old system and Salesforce stay live for a while.
Data Migration Is Not Metadata Deployment
A fourth job gets confused with the first 3. Salesforce separates data (records) from metadata (objects, fields, page layouts, flows, Apex classes). Tools like the Ant Migration Tool, Salesforce CLI, change sets, and DevOps platforms move metadata, and they do not move records.
Several ranking articles about Salesforce data migration tools list the Ant Migration Tool as a data migration option. It is a metadata deployment tool, and it will not load a single Contact. If your project needs both configuration and a data load, you need 2 different tools. We cover how the metadata side fits into a release process in our guide to Salesforce release management from sandbox to production.
Job | Example tools | What moves |
Data migration | Data Loader, Dataloader.io, Skyvia, Prodly | Records (Accounts, Contacts, custom objects) |
Data integration | MuleSoft Anypoint, Boomi, Jitterbit Harmony, Informatica | Records, on a schedule or in real time |
Metadata deployment | Salesforce CLI, Ant Migration Tool, change sets | Fields, objects, flows, code |
Four Migration Scenarios That Change Which Tool You Need
The right tool depends far more on your scenario than on record count. Each of these 4 scenarios favors a different class of Salesforce data migration tools.
Legacy CRM or spreadsheets into a new Salesforce org. HubSpot, Zoho, Dynamics, or a homegrown database is going away, and Salesforce is replacing it. Volume is moderate, transformation needs are heavy, and the migration happens once. If you are still weighing the move itself, our comparison of HubSpot and Salesforce for growing businesses covers the decision before the migration.
Salesforce org to Salesforce org. Mergers, acquisitions, divestitures, and org consolidations. The hard part is that record IDs differ between orgs, so every lookup and master-detail relationship has to be rebuilt. A tool that understands relational data sets saves weeks here.
Sandbox seeding. Developers and testers need realistic data in a Developer or Developer Pro sandbox, and copying production data raises privacy questions. This calls for filtering and data masking, run after every refresh.
ERP or database integration with an ongoing sync. SAP, Oracle, NetSuite, or a data warehouse needs to feed Salesforce continuously, and the initial load is just the first run of a pipeline. An iPaaS is usually the right answer. Our breakdown of ERP to Salesforce integration approaches for SAP, Oracle, and Dynamics goes deeper on the mapping decisions involved.
A fifth option is worth naming: sometimes you do not need to migrate at all. If the goal is to see warehouse or ERP data inside Salesforce without copying it, zero-copy real-time data access through Data 360 can replace a migration entirely for reporting and AI use cases.
How We Evaluated These Salesforce Data Migration Tools
We scored all 10 Salesforce data migration tools on the same 8 criteria. These are the questions we ask before committing to a toolset on our own projects.
- Volume ceiling. How many records can it move in a single job, and does it use Bulk API 2.0 for large loads? Salesforce’s own guidance is that any operation over 2,000 records is a candidate for Bulk API 2.0, which allows up to 150 million records per rolling 24-hour period and 150 MB of CSV per job.
- Operations supported. Insert only, or insert, update, upsert, delete, hard delete, and export?
- Relationship handling. Can it resolve lookups through external IDs, or move parent and child records together without a manual ID-mapping spreadsheet?
- Transformation depth. Does it offer field-level expressions, lookups, and deduplication, or does every change have to happen in Excel before the load?
- Automation and scheduling. Can a load run unattended, nightly, or on a trigger?
- Security and masking. Where does the data sit in transit, and can sensitive fields be anonymized for lower environments?
- Cost model. Free, per user, per record, or per connector, and where the price cliffs are.
- Skills required. Business admin, technical admin, or integration developer?
The 10 Salesforce Data Migration Tools Compared
The list runs from the simplest native option to full enterprise platforms. Ranking position reflects how often each tool is the right first choice for a typical mid-market Salesforce project, not which product is strongest in the abstract.
1. Salesforce Data Import Wizard
What it is: A browser-based import tool built into Setup on every Salesforce edition. No installation, no licensing, no API access required.
Best for: Business admins loading small, clean lists into standard objects, such as a trade-show lead list or a batch of new contacts.
Key capabilities:
- Imports up to 50,000 records per run, according to Salesforce’s Trailhead data import module.
- Supports Accounts, Contacts, Leads, Solutions, Campaign Members, and custom objects.
- Auto-maps CSV columns to fields when headers match, with a guided mapping screen for the rest.
- Runs duplicate matching against your org’s duplicate rules during the import.
- Lets you choose whether to trigger workflow rules and processes for the imported records.
Limits: It does not support Opportunities, Cases, or most other standard objects. It cannot delete or export records, and it cannot upsert on an external ID. There is no scheduling and no command line. We regularly see teams start in the wizard, get 3 objects in, and discover Opportunities are not on the list.
Our take: Perfect for what it is. Use it for one-time loads under 50,000 records into supported objects, and stop there.
2. Salesforce Data Loader
What it is: Salesforce’s free desktop client for bulk data operations, available for Windows and macOS. It reads from CSV files or a database connection and writes results back to CSV success and error logs.
Best for: Technical admins and developers running large one-time migrations or scripted recurring loads.
Key capabilities:
- Handles insert, update, upsert, delete, hard delete, export, and export all (which includes recycle bin records).
- Supports every standard and custom object.
- Salesforce’s Data Loader page states support for up to 5 million records per file with the original Bulk API and 150 million with Bulk API 2.0.
- Upsert against any external ID field, which is how you preserve relationships from a source system without a manual ID lookup.
- Drag-and-drop field mapping with saved mapping files you can reuse across loads.
- A command-line interface for automated, unattended jobs.
Limits: The command line is Windows only, which matters for macOS-based teams who want scheduled loads. It has no built-in transformation; every value has to be correct in the CSV before it goes in. Error handling is a CSV of failed rows that you fix and reload. Batch size, Bulk API mode, and serial vs parallel settings are easy to get wrong on objects with heavy automation or record locking, which is where most failed-load tickets come from.
Our take: Still the workhorse for most serious migrations, and the tool our own team reaches for first when the source data has already been cleaned. Its weakness is that it assumes the hard work happened before the load, which is the work most teams underestimate.
3. Dataloader.io by MuleSoft
What it is: A cloud-hosted data loader from MuleSoft, a Salesforce company, that runs in the browser and connects to your org through OAuth. Think of it as Data Loader with scheduling, cloud storage connections, and no install.
Best for: Admins who need scheduled imports and exports from Box, Dropbox, FTP, or SFTP without maintaining a desktop app or a Windows box for the command line.
Key capabilities:
- Insert, update, upsert, delete, hard delete, and export.
- Scheduled tasks on an hourly, daily, weekly, or monthly cadence.
- Smart lookup mapping: it can resolve a parent record by a field value such as an email or external ID rather than requiring the Salesforce ID in your file.
- Pulls source files directly from Box, Dropbox, FTP, and SFTP.
- Saved tasks you can rerun, plus per-row error reporting.
Limits: The free tier is capped at 10,000 records per month with 1 scheduled task and 1 Salesforce connection, and free tasks expire after 30 days, according to the Dataloader.io pricing FAQ. There is no data transformation beyond mapping, so it will not fix a picklist mismatch for you. Because it is cloud-hosted, your CSV passes through a third-party service, which some security teams will want to review first.
Our take: The best step up from Data Loader for teams that need scheduling. Per-user pricing gets steep once several admins need seats, so it fits 1 or 2 owners of a recurring process better than a whole team.
4. Salesforce Inspector Reloaded
What it is: A free, open-source browser extension for Chrome, Firefox, and Edge, maintained by the community and featured on the Salesforce Developers blog. It adds a data export, data import, and SOQL query layer on top of the Salesforce UI.
Best for: Admins and developers doing quick, mid-sized data fixes, exploratory exports, and migration validation without leaving the browser.
Key capabilities:
- Export any SOQL query result to CSV, Excel, or JSON, including a query plan to check performance on large objects.
- Import records by pasting CSV or Excel data directly into the browser, with insert, update, upsert, and delete operations.
- Auto-detects the object and operation from your pasted headers and lets you skip unmapped columns in bulk.
- Shows a red banner when you are connected to production, which has saved more than one admin from a bad afternoon.
- Doubles as a validation tool: run counts and spot checks on the target org right after a load.
Limits: It is not an official Salesforce product and is not covered by Salesforce Support. The project’s GitHub repository is the support channel. It consumes API calls like any other client, and it is not designed for multimillion-record loads or unattended runs. Browser extension policies in locked-down enterprises can block installation.
Our take: Every admin on our team has it installed. As a migration tool it is ideal for the 500 to 50,000 record fixes that happen after the main load, and for verifying the main load. Leave the main load to something else.
5. Skyvia
What it is: A cloud data platform from Devart that combines import and export wizards, bidirectional synchronization, replication to databases, backup, and a visual pipeline designer. It has a permanently free tier and a large connector library.
Best for: Small and mid-sized teams that need transformation, scheduling, and two-way sync without an enterprise integration budget or a developer.
Key capabilities:
- Import from CSV, Excel, cloud storage, databases, and other SaaS apps directly into Salesforce with no-code mapping.
- Expression-based transformations, lookups, and relation mapping to resolve parent records by external key.
- Bidirectional sync between Salesforce and a legacy CRM during a phased cutover.
- Replication of Salesforce data to SQL Server, PostgreSQL, Snowflake, and other targets for reporting or archiving.
- Scheduling from daily on lower tiers to per-minute on higher tiers.
Limits: Pricing is tiered by both features and monthly record volume, and advanced mapping features sit in the Standard tier and above. Skyvia’s own product pages state that the free Data Integration plan covers 10,000 records per month, which is fine for testing and small ongoing jobs but not for a real migration. Overage charges can surprise teams that did not model volume up front.
Our take: The most capable mid-priced option on this list. If Data Loader is too manual and MuleSoft is too much, Skyvia usually lands in the middle. Model record volume before you pick a tier.
6. Jitterbit Harmony
What it is: Jitterbit’s integration platform as a service (iPaaS), with a long history in the Salesforce ecosystem, prebuilt Salesforce connectors, and process templates for common pairings such as Salesforce with NetSuite, SAP, or Epicor.
Best for: Mid-market and enterprise teams whose “migration” is really the first run of a permanent integration between Salesforce and an ERP or operational system.
Key capabilities:
- Drag-and-drop mapping and transformation studio with scripting for edge cases.
- Prebuilt integration templates that shorten time to first load.
- Support for Salesforce Bulk operations for high-volume initial loads, then scheduled or event-driven syncs afterward.
- Central web console for monitoring jobs, queues, and error logs.
- On-premises agents for sources that cannot be exposed to the cloud.
Limits: This is the important one. Jitterbit’s free Cloud Data Loader, the tool most older listicles still recommend, was retired from general availability in November 2025 with development and registration discontinued. Jitterbit now directs those users to Harmony, which is a licensed enterprise platform, not a free utility. Plan and budget accordingly.
Our take: A strong choice when the ERP integration is the real project and the migration is its first milestone. For a one-time load, Harmony is more than you need.
7. MuleSoft Anypoint Platform
What it is: Salesforce’s own enterprise iPaaS. Anypoint provides API management, a large connector library, and the DataWeave transformation language, with a Salesforce connector that supports both standard and Bulk API 2.0 operations.
Best for: Enterprises with many systems to connect, an integration team in place, and a requirement that the migration pipeline become a governed, reusable API layer.
Key capabilities:
- Salesforce connector with Bulk API 2.0 support for initial loads of millions of records.
- DataWeave for complex transformation logic, including nested structures that flat CSV mapping tools cannot express.
- Reusable APIs, so the same pipeline that loads data on day 1 can serve ongoing sync and downstream consumers.
- Enterprise monitoring, retry policies, and error handling.
- Tight alignment with the wider Salesforce roadmap, including Data 360 and Agentforce.
Limits: Cost and skill. Anypoint is priced for enterprise integration programs, and building a migration flow requires MuleSoft development experience. For a one-time CRM cutover, it is heavy.
Our take: If you already own Anypoint, use it; there is no better-supported path into Salesforce at scale. Buying it purely for a migration rarely makes sense.
8. Informatica Intelligent Data Management Cloud
What it is: Informatica’s cloud platform for data integration, data quality, and master data management. Its Salesforce connector sits alongside profiling, cleansing, and deduplication services that most migration tools lack entirely.
Best for: Large enterprises where data quality is the primary risk: multiple source systems with conflicting customer records, regulated data, or a need for a golden record before anything lands in Salesforce.
Key capabilities:
- Data profiling to find the picklist inconsistencies, bad emails, and orphaned records before the load rather than after.
- Cleansing, standardization, and deduplication rules that run inside the pipeline.
- Master data management for building a single customer record from several sources.
- High-volume pushdown and parallel processing for very large loads.
- Governance and lineage, so you can show an auditor where every value came from.
Limits: Consumption-based enterprise pricing, a real learning curve, and implementation timelines measured in weeks. Overkill for a single-source migration of clean data.
Our take: When the data itself is the problem, Informatica fixes the problem instead of moving it. For everyone else, it is more platform than the project needs.
9. Boomi
What it is: Boomi’s low-code integration platform, with a visual process builder, a broad connector catalog, and a large partner ecosystem. It is a frequent choice for Salesforce plus NetSuite, Workday, or ServiceNow environments.
Best for: Mid-market and enterprise teams that want a low-code integration platform a technical admin can operate, with a migration flow that later becomes ongoing sync.
Key capabilities:
- Visual, drag-and-drop process design with reusable maps and functions.
- Salesforce connector supporting bulk operations for initial loads.
- Runtime “Atoms” that can run in the cloud or on-premises next to legacy databases.
- Built-in error handling, retries, and process monitoring.
- Prebuilt recipes and community-shared processes for common Salesforce integrations.
Limits: Licensing is connector-based, so cost grows with the number of systems, and per-connection pricing can surprise a small footprint. Transformation is capable but less expressive than DataWeave for deeply nested structures.
Our take: Boomi sits in the same tier as Jitterbit Harmony and Anypoint. The choice usually comes down to which platform your integration team already knows and which ERP is on the other end.
10. Prodly
What it is: A Salesforce-native data migration and DevOps tool built specifically for moving relational data sets between Salesforce orgs: production to sandbox, sandbox to sandbox, and org to org.
Best for: Org-to-org migrations after a merger or acquisition, sandbox seeding after every refresh, and moving configuration-heavy data such as CPQ price books, products, and rules.
Key capabilities:
- Moves entire relational schemas together, so Accounts arrive with their Contacts, Opportunities, Cases, Case Comments, and attachments in one run.
- Prebuilt templates for Sales Cloud, Service Cloud, CPQ, and Industries data sets.
- Filtering to seed a sandbox with a representative subset rather than all of production.
- Data masking for sensitive fields in lower environments, which Prodly positions as a privacy-compliance feature for sandbox seeding.
- Repeatable jobs, so every sandbox refresh gets the same seed data with one click.
Limits: It is a Salesforce-to-Salesforce tool and will not pull data out of HubSpot or an Oracle database. Licensing is a paid AppExchange subscription.
Our take: The one tool on this list that solves the org-to-org relationship problem outright. If your project is a consolidation of 2 Salesforce orgs, Prodly (or a comparable relational migration tool) will save you the ID-mapping spreadsheets that otherwise eat a week per object. Salesforce also maintains an open-source, Java-based org-to-org utility called Datafall on GitHub for teams that prefer scripting.
Tools We Left Off the List, and Why
A few names appear on nearly every competing list of Salesforce data migration tools. Some of them should not.
- Jitterbit Cloud Data Loader: retired in November 2025, as covered above, yet still recommended as “free” on multiple 2025 and 2026 articles.
- Talend Open Studio: the free, open-source edition was retired by Qlik on January 31, 2024 and is no longer hosted or updated. Talend lives on as a commercial product inside Qlik Talend Cloud, but the free version that made it a “top 10” staple is gone, and unpatched installs are a security risk.
- Ant Migration Tool and Salesforce CLI: metadata deployment tools that do not load records.
- Excel and Google Sheets: essential for preparation, but they are not migration tools. Spreadsheet-to-Salesforce connectors are excellent for small ad hoc loads and reporting, and not built for a full migration.
- Backup tools: built for backup and restore, not migration. Take a full backup before any migration; do not run the migration through the backup tool.
- CRM-to-CRM migration services: hosted services that copy HubSpot, Zoho, or Pipedrive into Salesforce with prebuilt mappings. Useful for a fast small-business cutover, with little control over transformation. Validate the result like any other load.
Side-by-Side Comparison
Here is how the 10 Salesforce data migration tools line up on the criteria above. “Max practical volume” reflects what each tool is designed for; every tool is ultimately bound by your org’s API allocations.
Tool | Type | Max practical volume | Operations | Relations | Transform | Schedule | Cost |
Data Import Wizard | Native, browser | 50,000 per run | Insert, update | Basic matching | None | No | Free |
Data Loader | Native, desktop | 5M (Bulk API), 150M (Bulk API 2.0) | All, incl. hard delete and export | Upsert on external ID | None | CLI (Windows) | Free |
Dataloader.io | Cloud loader | High (API-bound) | All | Lookup by field value | Mapping only | Yes | Free to $299/user/mo |
Salesforce Inspector Reloaded | Browser extension | Tens of thousands | Insert, update, upsert, delete, export | Manual | None | No | Free |
Skyvia | Cloud data platform | High (record-based pricing) | All plus sync and replication | Relation mapping | Expressions, lookups | Yes | Free to volume-based |
Jitterbit Harmony | iPaaS | Enterprise scale | All | Full | Full studio | Yes | Enterprise |
MuleSoft Anypoint | iPaaS (Salesforce) | Enterprise scale | All | Full | DataWeave | Yes | Enterprise |
Informatica IDMC | Enterprise data platform | Enterprise scale | All | Full plus MDM | Full plus data quality | Yes | Enterprise |
Boomi | iPaaS | Enterprise scale | All | Full | Visual maps | Yes | Enterprise |
Prodly | Salesforce-native org-to-org | Large relational sets | Org-to-org copy | Automatic, relational | Filtering, masking | Yes | Paid |
Which Tool Fits Your Migration?
Match the scenario, then pick from the Salesforce data migration tools above. This is the shortlist we hand clients at the start of a project.
- Under 50,000 clean records into Leads, Contacts, or Accounts: Data Import Wizard.
- A one-time migration of any size where the data has been cleaned in advance: Data Loader, in Bulk API 2.0 mode, loading in parent-to-child order with upsert on external IDs.
- Recurring loads from a file drop or SFTP, owned by one admin: Dataloader.io, or Skyvia if you also need transformation.
- HubSpot, Zoho, or Dynamics to Salesforce with messy picklists and a phased cutover: Skyvia for the sync, Data Loader for the final bulk pass.
- Post-load fixes, validation queries, and quick corrections: Salesforce Inspector Reloaded.
- Two Salesforce orgs becoming one: Prodly or another relational migration tool.
- ERP or warehouse feeding Salesforce indefinitely: MuleSoft Anypoint if you own it, otherwise Boomi or Jitterbit Harmony based on team skills.
- Multiple source systems with conflicting customer records and regulatory exposure: Informatica, or a data quality pass before any of the above.
Two caveats. First, the best answer is often 2 tools: a platform for the heavy load and a lightweight tool for the cleanup afterward. Second, tool choice rarely determines whether a migration succeeds. The next section is where projects are won or lost.
The Migration Steps No Tool Automates for You
Every one of these Salesforce data migration tools assumes 6 things have already happened. When they have not, the tool takes the blame for problems it did not cause.
Define what stays behind. Migrating 12 years of closed-lost opportunities and inactive contacts adds storage cost, slows reports, and pollutes AI features that learn from your data. Decide retention rules before mapping a field.
Build the mapping document. Every source field, its target field, its transformation rule, and its owner. Picklist values need a translation table (“CA”, “Calif.”, and “California” become one value). Record types and owners must exist in the target before the load.
Add an external ID to every migrated object. A custom External ID field holding the source system’s key makes upsert possible, keeps relationships intact, and lets you rerun a failed batch without creating duplicates. It is the highest-value configuration step in any migration.
Load in dependency order. Users and record types first, then Accounts, Contacts, Opportunities, cases, and activities. Children loaded before parents fail with invalid cross-reference errors, and parallel Bulk API batches on the same parent Account can hit record locks, so serial mode is safer on heavily related objects.
Decide, rule by rule, which automation to pause. Blanket-disabling every flow, trigger, validation rule, and duplicate rule is common practice and a mistake, because some rules exist precisely to catch bad legacy data. Document what you bypass, why, and when it goes back on. This is the point where a pre-migration Salesforce health check pays for itself, because it surfaces the automation you forgot existed.
Rehearse in a sandbox and reconcile with numbers. A full dry run in a Full or Partial sandbox, followed by row counts, sum totals on amount fields, and sampled record comparisons against the source. Sign off on counts, never on “it looks right.” Post-migration, ongoing data quality belongs to a data governance program rather than to the migration team, or the clean org you just built will drift within a quarter.
When a Tool Is Enough and When You Need a Migration Partner
A capable admin with Data Loader and a clean spreadsheet can migrate a 20,000-contact CRM in a weekend. We would never tell that admin to hire us.
The picture changes when 1 or more of these is true:
- More than one source system, with overlapping customers.
- Salesforce-to-Salesforce consolidation with custom objects on both sides.
- Regulated data (HIPAA, GDPR, financial records) that needs masking, audit trails, and documented handling.
- A hard cutover date tied to a contract expiry on the old system.
- Heavy automation in the target org that nobody fully understands.
- A migration that is really the first step of a permanent ERP integration.
In those cases, the tool is maybe 20% of the project. The other 80% is mapping, cleansing, sequencing, rehearsal, and reconciliation, which is where experienced hands change the outcome.
How VALiNTRY360 Approaches Salesforce Data Migration
The gap between the final full extract and go-live is where late-breaking history lives, and it is real. A week of freeze in a busy sales organization is thousands of activities, which is why the Salesforce data migration checklist treats the delta load as a planned step rather than a contingency.
- Set the freeze window and put it in writing. Users need to know exactly when the old CRM goes read-only.
- Run the delta extract on the source’s own modified-date field, not a filter someone maintains by hand.
- Load the delta with upsert on the legacy External ID, which is what that field was built for.
- Re-enable automation in the documented order, then verify one small transaction end to end before releasing users.
- Keep the rollback decision explicit. Name who can call it, set the deadline for the call, and define what rolled back means in practice.
- Export the loaded org before opening it to users. Cheap insurance, rarely done.
What to Do With the Legacy CRM After Go-Live
Do not switch it off on day one, and do not leave it editable. Set it read-only for 30 to 90 days so users can verify anything that looks wrong. Then take a final archive export, store it under your retention policy, and decommission on a date announced in advance. A legacy CRM left live and writable guarantees a permanent split in your customer record.
The Bottom Line on Salesforce Data Migration Tools
The 10 Salesforce data migration tools above cover every realistic scenario, from a 5,000-row lead list to a multi-org enterprise consolidation. The native tools are better than they get credit for, the mid-tier cloud tools add scheduling and transformation, and the iPaaS platforms belong in projects where integration outlives migration.
Choose by scenario, add an external ID to everything, load in order, rehearse in a sandbox, and reconcile with numbers. Do that and tool choice becomes a matter of convenience. Skip it and no tool on this list will save the project.
If you want help deciding which of these Salesforce data migration tools fits your org, or would rather have a partner own the whole migration, we are ready when you are.
FAQs
- Can Salesforce Data Migration Tools Preserve Existing Record IDs?
No. Salesforce generates new record IDs when records are inserted into a different org. To reconnect related records, migration teams typically preserve legacy IDs in external ID fields and use them to rebuild lookups during loading.
2. Can Salesforce Data Migration Tools Preserve Created Dates and Created By Values?
Yes, but only with the right permissions and migration method. Salesforce can allow authorized users to set audit fields such as Created Date and Created By when new records are inserted, helping preserve historical context from the source system.
3. Can Salesforce Data Migration Tools Handle Custom Objects?
Yes. Migration tools can load custom object records as long as the target objects, fields, permissions, and relationships already exist. Complex custom relationships still require careful sequencing, mapping, and external IDs to prevent broken references or duplicate records.
4. Can Formula Field Values Be Migrated Into Salesforce?
Formula fields are calculated by Salesforce and are read-only, so migration tools do not import values directly into them. Instead, migrate the source fields used by each formula and verify that calculated results match after the data load.
5. How Do Validation Rules Affect a Salesforce Data Migration?
Validation rules can reject incoming records when migrated values do not satisfy current business logic. Review affected rules before loading, decide which should remain active, and document any temporary exceptions so they can be restored immediately after migration.
6. Will Salesforce Flows and Triggers Run During Data Migration?
Flows, triggers, assignment rules, and other automation may run when records are inserted or updated, depending on configuration and the import method. Test representative batches first because automation can change values, create related records, or slow large migration jobs.
7. Can Salesforce Data Migration Tools Perform Incremental or Delta Migrations?
Yes. A delta migration moves records created or changed after the main rehearsal or initial load. This approach helps shorten final cutover downtime, but it requires reliable timestamps, source identifiers, repeatable mappings, and a clear rule for conflict resolution.
8. Do Salesforce API Limits Affect Data Migration Tools?
API limits matter because most high-volume migration tools consume Salesforce API requests. A job that performs well in a sandbox may behave differently in production, so teams should review production allocations, batch sizes, concurrency, and expected migration volume beforehand.
9. Can Salesforce Data Migration Tools Import Person Accounts?
Yes. Person Accounts can be imported when the target org has Person Accounts enabled and the appropriate record type configured. The migration file must map records correctly, and teams should test ownership, automation, relationships, and record-type behavior in a sandbox.
10. How Should Record Ownership Be Handled During Salesforce Migration?
Most migrations require owner mapping because source users may not exist in the target org or may be inactive. Build a user crosswalk before loading records, confirm permissions, and define fallback ownership for records whose original owners cannot be recreated.
11. Can Salesforce Data Migration Tools Move Tasks, Events, and Activities?
Migration tools can move activity records, but Tasks, Events, archived activities, and email-related records often need separate handling because their relationships and permissions differ. Confirm which activity objects are in scope and test reporting visibility after the migration.
12. Can You Roll Back a Salesforce Data Migration If Something Goes Wrong?
Many Salesforce migrations do not provide a simple one-click rollback. Safer projects use backups, small batches, external IDs, repeatable load files, and reconciliation reports so incorrect inserts can be identified, reversed, or reloaded without rebuilding the entire migration.
13. What If the Source CRM and Salesforce Have Different Data Structures?
The target schema does not need to match the source exactly, but every incoming value needs a destination or transformation rule. Create a field mapping document that covers renamed fields, merged fields, picklist translations, data types, and unsupported legacy attributes.
14. What File Format Is Best for Large Salesforce Data Migrations?
For large migrations, UTF-8 CSV files are generally the safest choice because they handle international characters consistently. Teams should also validate delimiters, date formats, decimal formats, line breaks, and leading zeros before loading production data.
15. When Should You Use a Custom API Instead of a Salesforce Migration Tool?
Choose a custom API approach when packaged tools cannot handle unusual transformations, specialized error recovery, proprietary source systems, or highly controlled automation requirements. Custom development adds flexibility, but it also increases testing, maintenance, security review, and long-term ownership responsibilities.