Moving a website has a reputation for going wrong, and it is deserved — but the failures are almost always the same failure. Somebody changes the DNS first and then starts copying files, which guarantees a window where visitors are sent to a server that has nothing on it. Do the same steps in the opposite order and there is no window at all.
Before you touch anything: write down what exists
Make a list of every DNS record on the domain today. Not just the one pointing at the website: the mail records, the verification records for services you have connected, anything a tool added months ago that you have forgotten about.
This list is the whole safety net. The most common serious mistake in a migration is not losing the site — that is visible within a minute and easily fixed — it is losing the mail, because the mail records were never copied and nobody noticed until a customer said their message bounced.
Lower the DNS cache time a day ahead
Every DNS record has a time-to-live, which tells the rest of the internet how long it may remember the answer. If yours is set to four hours, then after you switch, some visitors keep going to the old server for four hours.
Set it to five minutes at least a day before the move. That single step turns the switch from a slow, uneven changeover into something that completes while you watch. Put it back to a normal value once you are settled.
Build the site on the new server first
Copy the files, restore the database, install the certificate, and get the site fully working on the new machine while the old one is still serving every visitor. Nobody is affected by any of this.
Then test it properly before anything is switched. You can reach the new server directly — by its address, or by pointing your own computer at it — so you can click through the whole site, log in, place a test order and read the error log, all while the public is still on the old host.
Switch the DNS, and keep the old server alive
Only when the new site is genuinely working do you change the record. With a short cache time, traffic moves over in minutes.
Do not cancel the old hosting that day. Leave it running for a week: some resolvers ignore the cache time, and it is your only cheap way back if something surfaces that testing missed. A week of overlap costs one month at most and removes the pressure from every decision that follows.
The part everyone forgets
Content written after you copied the database. If the site takes orders or comments, anything that arrived between the copy and the switch exists only on the old server. Either copy the database again immediately before switching, or accept a short read-only period — but decide which, deliberately, rather than discovering the gap afterwards.
Scheduled jobs also need moving, and they are invisible until something silently stops happening. Backups, report emails, feed imports, certificate renewals: none of them announce their absence.
Or let us do it
We move sites onto our hosting as a normal part of setting an account up, including the DNS work and the mail records. Tell us where the site is now and what it runs on, and we will tell you plainly whether it is a half-hour job or a genuinely complicated one — before you commit to anything.