Test a migrated website at the destination before sending all visitors to it. Use the preview method agreed for the hosting environment, such as an application staging address or a temporary local hostname override. Ensure that the method reaches the intended server and does not merely show a cached copy from the source.
Recommended workflow
- Confirm the preview destination and compare several current records or uploaded files with the source.
- Run a written functional checklist and inspect application logs for warnings or connection errors.
- Validate the final synchronization plan, DNS changes and rollback steps before authorizing the switch.
Check more than the homepage. Test authentication, search, forms, image uploads, database-driven pages and scheduled jobs that are important to the application. For an online store, use the supported test mode for payment and shipping integrations; a migration test should not accidentally place real customer orders or send duplicate notifications.
Compare application settings for the domain, database host, storage paths and outbound email. Check HTTPS coverage for the final public hostname and plan any redirects. Record the findings and resolve errors before the cutover. When testing is complete, synchronize changes made at the source during the review window, switch the agreed DNS records and repeat the essential tests using public resolution.
