Inventory before moving
Record the current domain settings, DNS records, mailboxes, databases, cron jobs, redirects, SSL configuration and software versions. Create a list of third-party services such as payment gateways, analytics and transactional email that may depend on the old server.
Create verified backups
Download full copies of website files and databases before changing anything. Test that archives open and database exports contain expected tables. Preserve the old hosting account until the migrated site and email have been verified.
Prepare the destination
Create the domain, database users and mailboxes on the new platform. Match required runtime versions and extensions. Import files and databases, then update configuration values without changing the public DNS yet.
Test privately
Use a hosts-file preview or temporary URL to test key pages. Check forms, login, search, checkout, redirects, images and scheduled tasks. Review browser console and server logs. Testing before DNS changes prevents visitors from becoming the test team.
Switch DNS carefully
Lower DNS TTL ahead of a planned move when possible. Update only the required records and keep a copy of the previous values. DNS changes can propagate at different speeds, so both old and new environments should remain operational during the transition.
Verify after launch
Test from multiple networks, confirm HTTPS, send and receive email, inspect analytics and monitor errors. Take a fresh backup of the new environment. Cancel old hosting only after propagation is complete and every business-critical function is confirmed.