How to move your website to a new host without it going down

Moving your website to a new host is one of those jobs that sits on the to-do list for months. You know you should do it — the current host is slow, or expensive, or someone has recommended somewhere better — but there’s a quiet dread attached to it. What if the site goes dark halfway through? What if customers land on an error page? What if your email stops working and you don’t notice for two days?

I understand the worry completely. But here’s the reassuring part: a website move going wrong is almost always the result of doing things in the wrong order, not the move itself being dangerous. Done carefully, in the right sequence, you can shift your entire site to a new home and have visitors notice nothing at all. In this guide I’ll walk you through exactly how, in plain terms, and I’ll be honest about when it’s fine to do it yourself and when you should hand it over.

Why migrations go wrong in the first place

Before I show you the safe way, it helps to understand the handful of mistakes that cause nearly all the horror stories. Once you can see them coming, they lose their power.

The domain “address book” is misunderstood

Your domain name (say yourbusiness.co.uk) doesn’t actually contain your website. It’s more like an entry in a giant address book that says “the website for this name lives on that particular server, over there.” That address book system is called DNS — the Domain Name System. When someone types your address, their computer quietly looks you up in the DNS address book and gets pointed to the right server.

The catch is a thing called TTL, which stands for “time to live.” To save effort, computers all over the world remember the address they looked up for a while, rather than checking every single time. The TTL is simply how long they’re allowed to remember it before checking again — often set to several hours. So when you change where your domain points, the change doesn’t reach everyone instantly. Some visitors keep going to the old address until their remembered copy expires. This delay is called propagation, and misunderstanding it is the single most common cause of a wobbly move.

Email gets forgotten

Your website and your email often share the same domain, but they’re frequently two separate services living in two different places. It’s very easy to move the website and accidentally break the email, because both are controlled by those DNS records. More on this below — it deserves its own section.

The two copies drift apart

Here’s a subtle one. You copy the site to the new host on Monday. You don’t switch over until Friday. In between, someone adds a blog post or a customer places an order on the old site. Now the two copies no longer match, and when you flip the switch, that Monday-to-Friday activity vanishes. The copy and the live site drift apart.

There’s no way back

Finally, people delete the old host the moment the new one looks fine. Then a problem surfaces on Saturday and there’s nothing to fall back to. A move without a rollback plan is a gamble.

The calm sequence that keeps you online

Every mistake above is avoided by following the same ordered steps. Think of it as moving house: you get the keys to the new place and set it up before you hand back the old keys.

Copy the site to the new host first — and switch nothing. Get a complete copy of your website running at the new host while your real site carries on exactly as normal. Your visitors are still going to the old place. Nobody notices anything, because nothing public has changed yet.
Test the copy properly at the new host. Good hosts give you a temporary web address — a preview link that lets you view the copy on the new server without touching your real domain. Use it to click through every important page. Check the contact form actually sends. Check images load. Check anything that takes payments or bookings. This is your dress rehearsal.
Lower the TTL a day ahead. Remember that “how long computers remember the address” setting? A day or so before you switch, reduce it to a short value (a few minutes). That way, when you do flip the switch, the world picks up the new address quickly instead of clinging to the old one for hours. You’re shortening the memory in advance.
Do the switch. Update the DNS address-book entry to point at the new host. Because you lowered the TTL yesterday, the change spreads fast. If the copy was tested and complete, visitors simply arrive at the new server. To them, nothing happened.
Keep the old host live for a safety window. Do not cancel or delete the old host straight away. Leave it running for several days. This is your safety net: if anything odd shows up, you can point the domain back in minutes. It also catches anything that was still trickling in to the old address during propagation.

That’s the whole thing. Copy, test, prepare, switch, keep a net. The order is what makes it safe. This is exactly the calm, staged approach I use when I handle migrations for people.

The email trap — check this before you touch anything

This is the one I most want you to remember, because breaking your own inbox is a genuinely stressful way to spend an afternoon.

Your mailboxes — the addresses like hello@yourbusiness.co.uk — are very often provided by a completely different service from your website. You might have your site on one host and your email with Google Workspace, Microsoft 365, or a separate mail provider. All of them are steered by special DNS entries called MX records (the “MX” just means “mail exchange” — they’re the address-book lines that say where email for your domain should be delivered).

Here’s how the trap springs: when you move hosts, some setups replace your entire DNS address book with the new host’s default one. If that default doesn’t include your existing MX records, your email suddenly gets delivered to the wrong place — or nowhere. The website looks fine, so nobody realises for hours.

So, before you change a single thing, find out where your email actually lives:

Ask yourself: where do you log in to read your business email? If it’s Gmail, Outlook, or a named provider’s webmail, your mailboxes are almost certainly not on your website host.
Look up your MX records. You can do this with a free “MX lookup” tool online — type in your domain and it lists where your mail is routed. Write down exactly what it shows.
Whoever runs the migration must carry those exact MX records across to the new setup, unchanged.

Get this written down first and the email trap simply can’t catch you. If you’d like a second pair of eyes on where things point before you begin, that’s part of what I check in a Free Site Check.

Your pre-move checklist (works with any provider)

You can use this with any host, whether you’re doing it yourself or briefing someone else. Tick every box before you switch anything.

Take a full backup of the current site. Files and any database. This exists whatever the plan is — it’s the ultimate rollback.
List everything that’s moving. The website pages, images, any forms, any shop or booking system, any special features. If you don’t know it exists, you can’t test it later.
Write down your DNS and email details. Note your current MX records (where email goes) and any other custom records. Know who your domain registrar is and that you can log in.
Copy first, switch nothing. Confirm the new host has a working copy and a temporary preview address before any public change.
Agree a switch time. Pick a genuinely quiet period for your business. Avoid your busiest trading hours and avoid Friday afternoons — you want people around if something needs a look.
Lower the TTL a day before. So the switch propagates in minutes, not hours.
Agree a safety window. Decide how many days the old host stays live (several is sensible) before anyone cancels anything.
Have a test plan. A short list of the exact pages and functions you’ll click through on the new copy — and again right after the switch.
Freeze changes during the move. No new orders, posts or edits on the old site between the copy and the switch, so the two can’t drift apart.

When to get help (and when DIY is fine)

I’m genuinely happy for you to do this yourself if it fits, so let me be straight about where the line sits.

DIY is reasonable when you have a small brochure or marketing website — a handful of pages, no shop, no live bookings, no logins — and you’re a confident owner who’s comfortable poking around a control panel and following steps carefully. For a simple site, the worst realistic outcome is a short wobble that fixes itself as the address propagates. If you can tolerate the site looking odd for an hour on a quiet Sunday, and you’ve taken that backup, you can absolutely manage a straightforward move. Work slowly and don’t skip the test step.

Get help when money is moving through the site. If you run e-commerce, take bookings, host member logins, or the site is actively earning while people use it, the maths changes. An hour of downtime isn’t just inconvenient — it’s lost orders, lost bookings, and a dent in trust that costs more than any hosting saving. The same goes for anything with a database that’s constantly changing, or setups where email and website are tangled together in ways you can’t confidently untangle. That’s precisely when the drift problem and the email trap bite hardest, and when a calm, rehearsed hand is worth it.

It’s also worth reading up on what happens after the move. A host change is a good moment to think about what website maintenance actually involves, and — since fresh servers are worth keeping tidy — to know what to do in the first hour if your site is ever hacked.

The core message is simpler than the dread suggests: a website move is not a leap of faith. It’s a sequence. Set the new place up, rehearse on it, prepare the address book, switch, and keep the old place as a net. Do it in that order and the day you move hosts becomes the day nothing dramatic happened at all — which is exactly how a good migration should feel.