A step-by-step migration plan: full backups, lowering DNS TTL, copying files and databases, testing before the switch, moving email safely and what to check afterwards.
Moving a site to a new host sounds risky, but with a plan, visitors should not notice. The trick is to set up and test everything on the new host before you point your domain at it, and to keep the old host running until the change has fully taken effect.
Before you start
- Do not cancel the old hosting yet. Keep it until the move is complete and checked, ideally for a week or two.
- Find out where your DNS is managed. This might be your domain registrar, your old host or a DNS provider. You will need to log in there.
- Find out what the old host provides besides the website, especially email. Moving the website can break email if you are not careful.
- Pick a quiet time for the switch, such as when traffic is lowest.
Step 1: Take full backups
Download a complete copy of your site files and export the database (for WordPress and most content management systems). Keep them on your own computer as well as on the server. Note your software versions, such as PHP.
Step 2: Lower the DNS TTL
The TTL (time to live) on a DNS record tells other systems how long to cache it. A day or two before the move, lower the TTL on your domain's main records (often to 300 seconds, or five minutes). Then, when you switch, the change will spread much faster.
Step 3: Set up the new host
- Create the account and add your domain.
- Upload your files and import the database.
- Update configuration files with the new database details.
- Match the software versions to the old host where possible.
Many hosts offer a free migration service or a plugin that does this for you. It is worth using, but still check the result.
Step 4: Test before switching
Test the site on the new server before changing DNS. Options include a temporary URL from the new host, or editing your computer's "hosts" file to point your domain at the new server just for you. Check:
- pages, images and links load;
- forms send, and checkouts work if you run a shop;
- logins and admin pages work;
- the SSL certificate can be issued (some hosts can only do this after DNS has moved; plan for that).
Step 5: Handle email carefully
If email is hosted with your old provider, decide where it will live. Your MX records control where email is delivered. If you change the nameservers for your domain, you must recreate the MX, SPF, DKIM and DMARC records at the new DNS provider, or email may stop or be marked as spam. Copy every existing DNS record before changing anything.
Step 6: Make the switch
Update the DNS A record (or the nameservers) to point to the new host. Thanks to the low TTL, most visitors will reach the new server within minutes to hours. Avoid editing content on the old site during this period, or changes may be lost. For shops, consider briefly pausing orders.
Step 7: Check after the move
- Confirm HTTPS works and there are no security warnings.
- Test forms and email delivery again.
- Check search console tools for crawl errors.
- Make sure backups are running on the new host.
- Once everything has been stable for a week or two, set the TTL back to a normal value and cancel the old hosting, having downloaded a final backup.
Common problems
- Mixed content warnings: some links still use http://. Update them to https://.
- Broken permalinks: on WordPress, resaving the permalink settings often fixes it.
- Email stopped: almost always missing MX or other email DNS records.
Frequently asked questions
How long does DNS take to update?
Often minutes to a few hours with a low TTL. Some systems can take up to 48 hours.
Will moving hosts hurt my search ranking?
Not if URLs stay the same and the site works. Changing domain names is a bigger job and needs redirects.
Sources and further reading
- MDN: What is a domain name and DNS?
- Wikipedia: Time to live (DNS)
- NCSC: Email security and anti-spoofing
Facts checked on 20 October 2026. Spotted an error? Tell us and we will correct it.