Most people who want to leave a host don't, and it's almost never because leaving is actually hard. It's because leaving feels like defusing a bomb — one wrong move and the site goes dark, the email stops, the customers see an error. So they stay, paying the renewal hike, tolerating the slow support, because the fear of the move is bigger than the annoyance of staying. That fear is the whole reason lock-in works.
Here's the thing the fear hides: a website move is not a leap. It's a copy, then a test, then a switch — and through almost all of it, your old site stays live and untouched. You're not tearing anything down. You're building the new home quietly alongside the old one, checking it works, and only then redirecting the sign on the door. Done in that order, visitors never see a flicker.
▲ The why This is the doing of "Who owns your website?" That guide argues the exit is the measure of ownership. This is how you actually walk through it. Read it →Before you start: gather your keys
Ten calm minutes here prevents nearly every migration problem. You're just making sure you can actually reach everything that's "yours" before you move it. Don't change anything yet — only confirm you have access.
Confirm you can reach all of these
- Your domain registrar login. The account where your domain name lives — this is the one that matters most. If someone else holds it, sort that out first.
- A full copy of your site. All the files and any database — exported or downloaded, in your own hands, before you touch anything.
- Where your email lives. Is it with the host you're leaving, or separate (like a Google/Microsoft account)? If it's with the host, you'll move it too — know that now.
- Your current DNS settings. Screenshot or export them — the records that point your domain at things. You'll recreate these on the new side.
- Your new home, chosen. The new host or setup, signed up and ready to receive the copy.
You're not leaping off a cliff. You're building a second house next door, moving in quietly, and only changing your address once the lights are on.
The move, in five calm steps
This is the whole sequence. The order is the trick — the old site stays live until the very last step, so there's no moment where you're caught without a working site.
Copy everything out
Make a complete copy of your site — files and database — and keep it somewhere you control. Most platforms have an export or backup tool; if yours is genuinely standard files, this is just downloading them. Your live site doesn't change at all in this step. You're only taking a copy.
Build it on the new home
Upload that copy to your new host and set it up there. The new host gives you a way to view the site before it's public — a temporary address, or a small edit to your own computer's hosts file that points only your machine at the new server. The public still sees your old site the whole time.
Test it properly
On that private preview, click everything. Every page, every image, every link. Submit the contact form. Try the checkout. Check it on your phone. This is the step people skip and regret — fix problems now, while the old site is still the one everyone sees. Nothing is at stake yet.
Lower your DNS TTL
This is the one bit of jargon worth knowing, and it's the secret to zero downtime. TTL is how long the internet "remembers" where your site lives. A day or two before switching, lower it (to around 300 seconds). Now when you flip the switch, the world picks up the change in minutes instead of a full day.
Point the domain — and wait, watching
Now, and only now, update your domain to point at the new home (its nameservers or address records, at your registrar). This is the actual move. Because you lowered the TTL, it takes effect fast. Keep the old host running for a few more days while the change spreads worldwide — then, once everything's confirmed working, you can close the old account.
The two things people forget
Almost every migration headache comes down to one of these, and both are easy if you remember them up front:
- Email. If your email was hosted by the company you're leaving, it moves separately from the website — and it's the thing most likely to be forgotten until messages stop arriving. Know where your email lives before you start, and move or re-point it as part of the switch.
- The domain itself. Your domain is the one piece you most need to hold in your own name. If your old provider registered it "for" you and controls it, getting it under your own account is the real first step — because the domain is what you point at the new home. Hold the address, and you can move the house freely.
Notice that both come back to the same idea this whole hub keeps circling: the things you truly own — your domain, your files, your data — are the things that move with you. The move is really just exercising ownership you already had. Lock-in was only ever the feeling that you couldn't.
You don't have to do it alone
This sequence is genuinely doable by a careful non-expert, especially for a small, clean site — and now that you've seen the shape of it, the fear has somewhere to go: into a checklist instead of a knot in your stomach. Work through it at your own pace. Keep the old site live until you're sure. There's no prize for rushing.
And if at any point you'd rather hand it to someone who does this all the time — that's a fair choice too, not a failure. The point was never that you must do it yourself. The point is that you can leave, and nobody gets to hold your site hostage to stop you.
When you're ready
Want the move done cleanly, with nothing left behind?
I migrate sites the careful way — copy, test, switch, zero downtime — and hand you a clean static site you fully own at the end, on hosting with no lock-in waiting to trap you again. You leave once, and you never have to fear leaving again.
See clean-build & hosting services →The Field Manual · the doing, step by step
01How to actually leave a platform 02Make your forms keyboard-accessible 03Set up privacy analytics in an afternoon 04Get your domain into your own hands