How to Move Your Website to a New Host (Without Downtime)
Moving hosts goes smoothly when you do it in the right order: copy everything, test the new copy privately, then switch the domain over — and keep the old host running until you are sure nothing was left behind.
Common signs of this issue
- Your current host is slow, expensive, has poor support, or keeps suspending the site for using too many resources.
- Your web designer is gone and the site sits on hosting you do not fully control.
- Your hosting plan is ending, the host is shutting down, or it was bought by a company you do not want to stay with.
- You want to move but are worried about the site going down, email breaking, or losing Google rankings.
- You are not sure where your domain, website, and email each live — and suspect they may be at three different companies.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Map what lives where before you start. Write down three things: where the domain is registered, where its DNS is managed, and where email is hosted (Microsoft 365, Google Workspace, or mailboxes at the current host). Moving the website is one job; these are separate things that can break along the way.
- Take a full backup you control — files and database — and download it to your own computer or cloud storage. A backup that exists only on the old host's server does not count if the old account is closed.
- Lower the DNS TTL a day or two ahead. TTL is how long the world caches where your domain points. Dropping it to a few minutes (300 seconds is common) on the records you will change means the switch spreads quickly and can be undone quickly. This works when you change individual records; a change of nameservers is cached at a higher level and can still take up to 48 hours.
- Copy the site to the new host without touching the domain yet. Many hosts offer free migration or a migration plugin for WordPress. For sites with a shop or bookings, plan a short content freeze so no orders or entries land on the old copy after it has been copied.
- Test the new copy privately before anyone else sees it. Use the new host's temporary or preview address if it has one, or edit your computer's hosts file so your machine alone sees the new server under your real domain. Click through every important page, log in, submit the forms, and check that images load.
- Recreate every DNS record, not just the website one. If you are switching nameservers to the new host, all records move with them — so the mail (MX) records and the email authentication records (SPF, DKIM, DMARC) must be copied across exactly, or email will stop. If you only change the website's A record, email records stay where they are.
- Switch the domain, then check SSL. Point the website record (or nameservers) to the new host. Most hosts issue a free certificate automatically once the domain points at them, which can take a little while. Confirm the padlock appears for both the www and non-www versions of your address.
- Cancel the old host last. Keep it for at least a week or two after the switch, until the site, the forms, and email have all been confirmed working from the new server. Only then download a final backup and cancel.
What this usually means
A website move is really two separate events: copying the site and switching the domain to the copy. Downtime happens when those two get squashed together — the domain is pointed at the new host before the site is fully there, or the old host is cancelled while half the world is still being sent to it. Keep them apart, test in between, and the visitor never notices the move.
Email is the part most likely to go wrong, because it is invisible until customers say their messages are bouncing. It hangs off the same domain settings as the website, so changing where the domain points can quietly change where mail goes too. If your mailboxes are hosted at the old web host, they need their own migration plan — the mail has to be copied and your email apps pointed at the new server — before the old account is closed.
Search rankings are generally safe in a straightforward host move, because the addresses of your pages do not change. They are at risk if the move also changes the domain, switches from www to non-www or back, or restructures page addresses. In any of those cases, old addresses need 301 redirects to the new ones, and it is worth watching Search Console for error spikes during the following weeks.
What not to do
- Don't cancel the old hosting until the new site and email have run cleanly for at least a week. The old account is your rollback and your source for anything that was missed.
- Don't switch nameservers without first copying every DNS record, especially mail and email authentication records.
- Don't transfer the domain registration to a new company in the same week as moving the hosting. Do one move at a time.
- Don't make edits or take orders on the old site after it has been copied. Anything added there after the copy will not exist on the new host.
- Don't judge the move by what your own computer shows. Your browser and network cache old settings, so check with a DNS lookup tool and a phone on mobile data.
- Don't move a site that is currently broken or hacked and expect the new host to fix it. Clean it up first, or you will just carry the problem across.
When to get help
A simple brochure site with email hosted elsewhere is a job many owners can do with a host's free migration service. It is worth bringing in help when several risky pieces meet at once: mailboxes that live at the old host, a shop or booking system that cannot lose orders during the switch, a domain change on top of the host change, or DNS records nobody has documented. Someone who does migrations routinely will copy the records correctly, test the new copy privately, time the switch for a quiet hour, and check email and SSL afterwards, which is exactly where do-it-yourself moves tend to come undone.
Could your hosting be the problem?
If your host is slow, unreliable, or hard to deal with, moving to a better one can clear up issues like this for good. One we genuinely recommend is Instant Access Internet Services — a smaller, compassionate company with 30 years in the business, known for being one of the fastest, with great management and low pricing. (Just a recommendation — no affiliate link, no kickback.)
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
How do I move my website to a new host without downtime?
Copy the site to the new host first, test it privately using a temporary address or your hosts file, then point the domain to the new server. Lower the DNS TTL a day or two ahead so the switch spreads quickly, and keep the old host running until everything is confirmed working.
Will moving hosts break my email?
It can if the mail records are not carried over. If you change nameservers, every DNS record, including MX, SPF, DKIM, and DMARC, has to be recreated at the new DNS provider. If your mailboxes live at the old web host, the mail itself also needs to be moved before that account is closed.
How long does DNS take to update after moving hosts?
If you lowered the TTL in advance and only changed individual records, most visitors switch within minutes to an hour. A nameserver change can take up to 48 hours to reach everyone. During that window some visitors see the old server and some see the new one, which is why the old host must stay live.
Will moving hosts hurt my Google rankings?
Not usually, if your domain and page addresses stay the same and the site stays up. Rankings are at risk when the move also changes the domain or page addresses without 301 redirects, or when the site is down or broken for days.
Do I need to move my domain name too?
No. Your domain registration can stay where it is; you only need to update where it points. Moving the registration is a separate job and is best done on its own, well before or after the hosting move.
When should I cancel my old hosting?
After the new site, forms, SSL, and email have all worked from the new host for at least a week, and after you have downloaded a final backup from the old account. Cancelling early saves little and removes your only rollback.