Migration planning follows a consistent pattern regardless of type. The specific tools differ but the workflow is the same.
- Inventory the source
List every record, every configuration, every user, whatever the migration covers. Comprehensive inventory drives accurate planning.
- Design the target
Document the target state: schema, configuration, license assignments. Cross-check against business requirements before any migration starts.
- Plan the cutover
Pick the cutover date, plan the rollback option, communicate the timeline to stakeholders. Coordinate with the Salesforce account team for platform migrations.
- Test in non-production
Run the migration in sandbox or scratch org. Verify outcome; fix issues; re-test. Production migration should be the third or fourth dry-run, not the first.
- Execute with monitoring
Run the production migration during the chosen window. Watch dashboards, logs, error queues. Have the rollback option ready.
- Validate post-migration
Verify outcomes against the design. Resolve any unexpected issues. Communicate completion to stakeholders.
- Migration is overloaded vocabulary. Confirm which type you''re discussing before assuming tooling.
- Production-first migration usually fails. Test in sandbox or scratch first; production should not be the first dry-run.
- Rollback plans are critical. Some migrations are not reversible (Hyperforce); know the constraints in advance.
- Coordinated cutover matters for multi-system migrations. Source-system shutdown, data freeze, target activation must align.