Step one: finish the new site first
Never switch the domain to a site that is not ready. Build or copy the new site on the new host, using the temporary address the provider gives you. Test the pages, forms, images and mobile layout there.
Also confirm that the new host has SSL ready for your domain, or knows how to issue it once the domain points over.
Step two: record what exists today
Log in to wherever DNS is managed and export or screenshot every record. Pay special attention to MX records for email, TXT records for SPF and verification, and any subdomains such as booking or shop that point to other services. These are often forgotten.
Identify whether your DNS is hosted at your registrar or with your old host. If it is with the old host and you plan to cancel that account, you must move DNS first.
Step three: choose the method
There are two ways to connect. You can change the A record (and the www CNAME) so they point to the new server, leaving DNS where it is. Or you can change the name servers to the new provider's, which hands over all DNS. The first is less risky if you use outside email, because your other records stay in place.
If you change name servers, recreate every old record at the new provider before switching.
Step four: lower TTL and switch at a quiet time
A day before, lower the TTL on the records you will change to something like 300 seconds. Make the switch during a quiet business hour, not on a Friday evening. After saving, check the site from a phone on mobile data and from another network to see whether the change has reached you.
During the transition some visitors see the old site and some the new one. Do not edit the old site meanwhile, or you may lose changes. If forms are used, test them on the new site.
Step five: verify and keep a rollback
Check the secure padlock, the www and non-www versions, redirects, email sending and receiving, and Search Console. Keep the old hosting account active for at least a couple of weeks. If something is wrong, you can restore the old records from your notes and be back in minutes.
Once everything is stable, raise the TTL again and cancel the old plan. If you want help with a handover, MCC Solutions can walk through the checks with you.
Mistakes that cause trouble
The most common slip is leaving both the old and new records in place, so some visitors land on the wrong server. Another is forgetting the www version, so one address works and the other shows an error. People also cancel the old hosting too early, then discover the domain's DNS was managed there.
Finally, remember redirects. If page addresses changed in the move, set up redirects from old to new so links and search results still land on the right page.
Common questions
How long will my site be down?
With the new site ready and a low TTL, often none. Some visitors simply move to the new server gradually.
Do I need to transfer the domain to change hosting?
No. Pointing DNS and transferring registration are separate. You can keep the domain where it is.
Why is my email broken after the switch?
Most likely the MX or SPF records were not copied when DNS changed. Restore them from your notes.
This guide is general information. Search engines change how they work and their guidelines; check Google's current documentation for your situation. Nobody can guarantee a ranking.