Make a complete inventory
Write down your domain, current DNS provider, hosting control panel, website platform, databases, mailboxes, scheduled jobs and required software versions. A simple WordPress blog and a custom web app may need different steps.
Create backups before touching DNS
Export website files and databases, and keep the backup somewhere independent of the old host. For WordPress, also note theme and plugin versions. Make sure you know how to restore the backup if the new copy fails.
Prepare your new hosting
Create the destination account and databases, then upload the files and import data. Update configuration values carefully when database names, usernames or directories change. If you rely on HTTPS, arrange the certificate at the new host as well.
Test with a preview before changing the public domain
Ask your host for a supported preview method, staging hostname or temporary hosts-file setup. Check the home page, internal links, images, logins, forms and payments. A store should get extra attention to sessions, orders and emails.
Update DNS carefully
If you are changing nameservers, preserve the records needed for email. If you are only updating an A record, confirm it points to the new host. Allow for caching; do not shut down the previous server immediately.
Watch the first day after the move
Monitor errors, test logins and submissions, and confirm incoming email. Keep the previous hosting copy available until you are satisfied the transition has completed. If you used a temporary maintenance mode, disable it after testing.
For a larger application, consider a specialist migration plan that accounts for data created during the move. Ask Estha migration support what is available for your setup.