Okay, so I've been living in the new Salesforce Data Import Wizard for the past three weeks, migrating a client off of a patchwork system (a messy mix of HubSpot for marketing and a home-grown CRM for sales). I used the *old* import tool for years, so I was really curious to see if this long-awaited overhaul was just a coat of paint or a real game-changer for these kinds of single-tool migrations.
Here’s my deep dive, specifically from a migration perspective:
**What's noticeably better:**
* **The mapping UI is finally modern.** Dragging and dropping fields from source to target is smooth. It remembers your previous mappings, which is a huge time-saver when you're doing batches (like moving Contacts, then Accounts, then Opportunities).
* **Error handling is vastly improved.** Instead of a cryptic failure log, it now groups errors by type and even suggests fixes. For example, it flagged duplicate Account names based on our matching rules *before* the final import, which let us clean up the data mid-process.
* **Scheduling is built-in.** This was crucial for our cutover plan. We could map and validate the import of our 50k Contacts during the day, then schedule it to run at 2 AM, minimizing system lock-up for the sales team.
**Where it still feels a bit "meh":**
* **Complex relationships are still tricky.** Migrating Products with Pricebook Entries and then tying them to historic Opportunities still required a very staged, manual approach. It's not a one-stop shop for all data objects in a complex migration.
* **The sandbox limitation.** You can't use the new wizard in a sandbox to do a full test run unless you have "Enable Data Import Wizard" turned on at the org level, which our admin hadn't done. We had to do the dry-run in production on a Sunday, which was stressful.
**Our migration timeline with the new tool:**
1. **Data Audit & Clean (1 week):** Exported source data, identified custom objects, planned the import order (Static data -> Accounts -> Contacts -> Opportunities -> Activities).
2. **Mapping & Dry Runs (1 week):** This is where the new tool saved probably 2-3 days. The UI made iterating on mappings so much faster.
3. **Phased Cutover (1 weekend):** Accounts/Contacts went Friday night, Opportunities Saturday, Email Messages/Activities Sunday. The scheduling feature was the hero here.
4. **Validation & Cleanup (3 days):** Spot-checking records, fixing the ~5% that had errors (mostly due to legacy data quirks).
**Verdict:** It's a solid "B+". For migrating standard objects from a relatively clean source, it's excellent and a massive upgrade. For deeply complex, multi-object migrations with lots of custom relationships, you'll still need a blend of this tool, Data Loader, and some manual workarounds. But for a single-tool replacement project? I'd definitely recommend giving it a serious look.
Has anyone else used it for a full-scale migration yet? I'm particularly curious about how it handled custom objects or if you hit any API limits with large batches.
— Emma
If it's not measurable, it's not marketing.