Salesforce Data Migration UAT: How to Test CRM Data Before Go-Live

Salesforce migrations usually fail after the load report says they succeeded. The records are present, but a sales rep cannot find the right contact, a manager cannot see an opportunity, a case routes to no owner, a report drops a region, or an integration treats a migrated record as brand new.

Data migration UAT closes that gap. It tests migrated records in the business journeys they must support, with the real ownership, sharing, reporting, and downstream conditions that production creates.

Start with a migration inventory that business users recognise

List each source object, target object, critical field, relationship, transformation, data owner, and downstream dependency. Include the records that make up real work, not only the objects that are easiest to count.

• —Accounts, contacts, leads, opportunities, cases, products, contracts, and custom objects in scope.
• —Parent-child and many-to-many relationships, account hierarchies, contact roles, opportunity teams, case links, and ownership history.
• —Owners, queues, territories, business units, record types, sharing outcomes, and restricted fields.
• —Activities, notes, attachments, open tasks, historical transactions, and identifiers needed by connected systems or users.
• —Picklist translations, currencies, dates, derived values, status mappings, duplicate rules, and obsolete or inactive records.

Reconcile the load, then test the business outcome

Reconciliation establishes that the dataset is complete enough to investigate. UAT then proves that the data behaves correctly when a user works with it. Both are necessary, and neither substitutes for the other.

• —Reconcile record counts by object, source segment, status, region, owner, and other material business dimensions.
• —Sample high-value, complex, recently active, long-lived, duplicate-prone, and exception records rather than only clean records.
• —Open migrated records as the users who will own, sell to, service, approve, and report on them.
• —Create follow-on activity: update an opportunity, convert a lead, route a case, change an owner, submit an approval, or send a record through an integration.
• —Compare reports, dashboards, API outputs, and downstream data with the detailed Salesforce records and source evidence.

Test ownership, security, and relationship integrity

A migrated account may be technically accurate but operationally unusable if its owner is inactive, its contacts are not related correctly, its hierarchy is incomplete, or its sharing outcome exposes it to the wrong team. These defects affect every action taken after go-live.

• —Confirm active and inactive owners, queues, territory assignments, and reassignment rules produce the intended visibility.
• —Validate account hierarchies, parent records, contact roles, opportunity relationships, case links, and custom-object lookups.
• —Run scenarios for users who should have full, partial, and no access to the same migrated records.
• —Check historical and source identifiers remain available wherever an integration, reconciliation, or support process relies on them.

Rehearse the cutover and first operational day

The final migration needs a rehearsal that includes the delta records created while the first load was being tested. It should prove the sequence, time window, team access, communication, exception management, and first transactions the business will run after cutover.

• —Time the final extract, transformation, load, reconciliation, delta migration, access activation, and interface switch-over.
• —Run representative first-day activities across sales, service, management reporting, and connected systems.
• —Test the procedure for a missing, duplicate, misowned, or incorrectly mapped record, including whether it can be corrected without creating further inconsistencies.
• —Set measurable sign-off criteria for counts, reconciliations, sample results, operational scenarios, integration outcomes, and accepted residual risk.

“Migration is complete when a migrated record can be trusted in the next business process, report, integration, and customer interaction — not simply when it exists in Salesforce.”