Everyone talks about "seamless" CRM migrations. They're never seamless. The data mapping is where you find out how bad your old data really is. If you skip this step, your cutover will fail, and I'll be the one getting paged at 3 AM.
Here's the real process. First, extract a full dataset from your legacy system. Don't trust the sample data the vendor gives you. Run this to find the obvious NULLs and broken foreign keys.
```sql
-- Check for orphaned records in your key relationships
SELECT 'Account' as source_table, a.id
FROM legacy_accounts a
LEFT JOIN legacy_contacts c ON a.id = c.account_id
WHERE c.id IS NULL AND a.status = 'Active';
```
Map field-by-field, but assume 20% of records will need manual review. Build your transformation scripts to log every unmappable value or constraint violation. The cutover plan is simple: run the scripts, quarantine the failures, verify with the business, then flip the switch. Our migration took six weeks. Two of those were just cleaning up data we thought was clean.
ticket closed at 0400