Want to work smarter with AI? See how Agentforce fits your business.
You prove a CRM migration worked by testing it in layers before anyone switches over. First reconcile record counts for every object, then spot-check sample records field by field, compare key reports between the old and new systems, and finally have real users complete their daily tasks in Salesforce. Only when agreed go/no-go criteria are met should the team move across, and the old CRM should stay read-only until the new org has proven itself.
The Validation Layers
| Test | What It Checks | Pass Criteria |
|---|---|---|
| Record count reconciliation | Every source record arrived, by object | Counts match, or differences are explained and approved |
| Field-level spot checks | Values, dates and picklists loaded correctly | Sample records match the source field by field |
| Relationship checks | Contacts, deals and activities link to the right accounts | No orphaned records |
| Attachment and notes checks | Files and notes sit on the correct records | Samples open and are linked correctly |
| Report comparison | Pipeline, revenue and activity totals agree | Key totals match the old system |
| Failed record review | Load errors were captured and fixed | Error log is empty or fully resolved |
User Acceptance Testing
User acceptance testing asks the people who use the data every day to work in Salesforce with migrated records. Reps look up their own accounts, update deals and log activities; managers run their forecasts and dashboards; service teams open existing cases. Real users notice problems that automated checks miss, such as a missing field on a layout or a stage that no longer makes sense.
Parallel Run
A short parallel run lets a pilot group work in Salesforce while the old system remains available for reference. It confirms that daily processes, automations and integrations behave as expected under real use before the whole team depends on them.
Go/No-Go Criteria
- All critical record counts reconcile
- No open severity-one defects from testing
- Key reports match the old system
- Integrations and automations pass their tests
- Users have completed training and signed off UAT
- A rollback plan is ready if go-live fails
When to Turn Off the Old System
Do not delete the old CRM straight after cutover. Set it to read-only, keep a full export as an archive, and retire it only after the business has worked in Salesforce through a full reporting cycle without needing to go back.
Who Should You Hire?
Ask any partner for their validation checklist and UAT plan before signing. Folio3 builds reconciliation, UAT and go/no-go gates into its Salesforce migration services.
After cutover, Salesforce support and maintenance services help fix issues users raise in the first weeks.
People Also Ask
- What tests should you run after a Salesforce data migration?
- What is user acceptance testing in a CRM migration?
- What are go/no-go criteria for a CRM cutover?
- When is it safe to turn off the old CRM after migration?
- How do we test that a CRM migration actually worked before we switch everyone over and turn off the old system?
Need confidence before you switch off the old CRM?
Talk to Folio3 about a migration validation and UAT plan with clear go/no-go gates.
Plan migration testing with Folio3 →