Before moving a website, document the current hosting, DNS, email, SSL, database and external dependencies, take a usable backup, test the new environment and plan how you will switch back if something goes wrong.
A hosting move is more than copying website files.
Moving a website to a new host can be straightforward, but only when the dependencies are known first. The website itself is often just one part of the setup.
1. Document the current environment
Record the current hosting account, PHP or application version, database, SSL setup, DNS records, cron jobs, email dependencies and any external services connected to the site.
2. Confirm what DNS is actually doing
Before changing nameservers or DNS records, identify where the website, email and other services are currently pointed. A hosting move should not accidentally move business email with it.
3. Take a usable backup
Keep a copy of the website files and database that can actually be restored. A backup that has never been tested is not the same thing as a known-good recovery point.
4. Plan the switch and rollback
Test the new environment before changing live DNS. Decide what will be checked immediately after the switch and what you will do if something does not work.