Free server migrationYou test it before anything moves. Then you decide.
Every host offers free migration, so the word free is not the promise here. These two are: the copy is running and reachable for you to break before a single DNS record changes, and we never ask you to cancel your old provider first.
The part that matters
Nobody is afraid of the invoice. They are afraid of the downtime.
A migration goes wrong in one of three ways: the site is down longer than promised, something is quietly missing for a week, or you cancelled the old host and cannot go back. Here is what each of those costs here.
What we will not do
No cut-over you have not tested first.
The staged copy runs on its own address, and you browse the real site on the new server with a single line in your hosts file. Run your test suite against it, log into the admin, place a fake order. Only when you are satisfied does anything change — and the old server is still serving every visitor the entire time.
Pick where it lands- We do not touch your old hostNo credentials changed, nothing deleted, nothing cancelled.
- You keep it a weekCancel it yourself, once you are certain. Never before.
- No contract for the helpNo minimum term in exchange. Leave next month if it disappoints.
- We will tell you not toIf moving is a bad idea for you, you hear that before you have paid.
The process
Five steps, and one of them is you saying no.
Timings are what a straightforward move actually takes. Something unusual takes longer and you are told which day, not left to guess.
-
01
Day 0
We look at what you actually have
You describe it or you give us read access to look. We come back with what will move cleanly, what needs rebuilding, and how long the cut-over will be. If something is a bad idea we say so before you have paid for it.
-
02
Day 0 – 1
The target is built and staged
Your new machine is provisioned and the first full copy runs while the old one stays live and serving. Nothing has moved yet and nothing is at risk.
-
03
Day 1 – 2
You test it before anything changes
The staged copy is reachable on its own address, with a hosts-file entry so you can browse the real site on the new server. Break it, poke it, run your test suite.
-
04
Cut-over
A final sync, then DNS
An incremental catch-up of anything that changed, then the DNS move at a time you choose. Typical unreachability is under five minutes; for a static site it is the TTL and nothing else.
-
05
Day 2 – 9
The old one stays where it is
We do not touch your previous host and we never ask you to cancel it first. Keep it a week, confirm everything, then cancel it yourself once you are certain.
What moves
Including the parts that usually get lost. Mail folder state and database character sets are where most migrations quietly fail, and they are both on this list on purpose.
- Whole servers
- Block-level, disk for disk A running Linux machine anywhere else becomes a running machine here with the same filesystem, users, services and cron. Usually the cleanest option and almost always the fastest.
- Control panels
- cPanel, Plesk, DirectAdmin, CyberPanel Account by account, with mail, databases and DNS zones. The panel licence comes with the plan, so you are not paying twice during the overlap.
- Websites and databases
- Files, MySQL, PostgreSQL, Redis Including the awkward parts: character sets that were wrong in the original, stored procedures, and the one cron job nobody documented.
- Containers and clusters
- Docker, Compose, Kubernetes Registries, volumes and secrets. We will read your compose file and tell you what will break before it breaks rather than after.
- Object storage
- S3, B2, Wasabi, Spaces Bucket to bucket, with checksums verified on arrival. Egress on our side is free, so a re-run costs nothing if the first pass finds a mismatch.
- IMAP, with folders and flags intact The part most migrations get wrong. Read state and folder structure survive, and the cut-over is timed so nothing is delivered into the old server after DNS moves.
Coming from
Named, because “we support any provider” reads as nobody in particular.
Where it lands is your decision and it is a legal one before it is a technical one — the eight regions are chosen for their law as much as their latency, and they all cost the same. The jurisdictions page sets out what each one actually protects you from.
Before you commit to moving.
Is it really free, or free above some size?
Free, with no size threshold and no minimum term attached to it. The reason is straightforward commercially: a migration that goes badly produces a refund and a customer who leaves, so doing it properly is cheaper for us than charging for it. There is no line on any invoice for this.
How much downtime should I actually plan for?
For a static site or one with a read-mostly database, the DNS TTL and nothing more — drop the TTL to 300 seconds a day ahead and the visible interruption is under five minutes. For a busy write-heavy database it is the final incremental sync, usually two to fifteen minutes, and you choose the hour. Anything longer than that we tell you in advance rather than discovering together.
Do I have to give you root on my old server?
It is the fastest path and it is not the only one. You can run the copy yourself with instructions we write for your specific setup, or give us a read-only account, or hand over a snapshot. If you do give us access, rotate the credentials afterwards — advice we give every customer and which applies to us exactly as much as to anyone else.
What if it goes wrong halfway?
Nothing has changed yet, which is the entire point of the order of operations. Your old host is untouched and still serving; the failed copy is on our side and costs you nothing. We work out what happened and run it again, or tell you honestly that this particular setup is not worth moving.
Can you migrate me away from you later?
Yes, and with the same help. Snapshots are downloadable, object storage is S3 and egress is not billed, and nothing is stored in a format that only works here. A host that makes leaving difficult has stopped competing on being worth staying with.
I am being shut down by my current host. How fast?
Say so and it is scheduled the same day. It is the case we are best at, and the one where the usual advice to test everything first gets compressed — but you still see the copy before DNS moves, even if that window is an hour instead of two days.
Will you migrate something you would not host?
The two prohibited categories, no, and that answer does not change. Everything else on the acceptable use policy is welcome, including the material your previous host asked you to remove — that is a large share of why people arrive here.