Moving WordPress to a New Host, Without Downtime

Moving WordPress to a new host means copying your site's files and database to the new server, pointing your domain at it, and testing before you switch off the old one. It sounds daunting but it is a well-worn process, and many hosts will do it for you free.

The reason people put migration off is fear of downtime, but done in the right order there is no downtime at all — you build and confirm the new site before anyone visits it. Here is the full path, whether you migrate yourself or let the host handle it, plus the mistakes that cause the horror stories.

The easiest route: free host migration

If your new host offers free migration, use it — it is the simplest and safest option. Many mainstream WordPress hosts include a migration service or plugin that moves your site for you, often at no cost on at least some plans.

You provide access to the old site, they copy everything to the new server, and you verify it. If that is available, most of the steps below are handled for you, and the host's team catches the fiddly details. It is worth choosing a new host partly on whether it offers this, especially if you are not comfortable doing the transfer yourself.

Migrating yourself with a plugin

A migration plugin is the DIY method most people should use. Tools designed for this package your entire site — files, database, themes, plugins, media — into a single archive, which you restore on the new host.

1. Back up the current site fully before you start.
2. Install and run a migration plugin to package the site.
3. Create the site on the new host and restore the package there.
4. Test the new copy on a temporary URL before changing anything public.

The plugin handles the database details that make manual migration error-prone, so it is the right balance of control and safety for a typical site. Manual migration — copying files by FTP and exporting the database by hand — still works, but there is rarely a reason to take that harder path now.

Pointing your domain to the new host

The switch itself is a DNS change, and it is reversible. Once the site works on the new host, you update your domain's nameservers or DNS records to point at the new server. This propagates over a few minutes to a couple of hours.

Keep the old site running until the new one is confirmed live and correct — do not cancel the old host the same day. During propagation some visitors see the old server and some the new one, which is why both should be working copies. Once everything resolves to the new host and looks right, you can safely retire the old plan.

Test before you cut over

Testing on a temporary URL is the step that prevents visible breakage. Before you point the domain, check the migrated site on the host's temporary address: click through key pages, test forms and the checkout if you have one, and view it on mobile.

A staging-style dry run here means visitors never see a half-broken site — the same discipline covered in WordPress staging explained. Spend ten minutes on this and you avoid the most common migration embarrassment, which is pointing the domain at a copy that looks fine on the surface but has broken links or missing images.

Avoid the common migration mistakes

Most migration pain comes from a few avoidable errors: cancelling the old host before the new one is confirmed, forgetting to migrate the database along with the files, missing email accounts tied to the old host, and not updating hard-coded URLs.

Take a full backup first, keep the old plan for a week after cutover, and you have a safety net if anything is wrong. Choosing a new host with free migration removes most of this risk — compare options in the best affordable WordPress hosting ranking, where migration support is one of the things worth weighing alongside renewal price.

How long a migration actually takes

For a typical small site, the hands-on work is often under an hour, plus DNS propagation. Packaging the site with a plugin and restoring it on the new host takes minutes to tens of minutes depending on size; testing adds a little more. The longest wait is DNS propagation after you switch the domain, which can take anywhere from minutes to a couple of hours.

A large or complex site — a big store, thousands of posts, heavy media — takes longer to package and verify, and is where free host migration or a careful plugin process pays off most. Either way, plan the domain switch for a quiet period so the propagation window overlaps with low traffic.

After the move: the cleanup checklist

Once the new host is live and confirmed, tidy up so nothing bites you later. Update any hard-coded URLs, re-check that forms and email are working from the new server, confirm your SSL certificate is active on the new host, and make sure backups are scheduled there — the old host's backups do not follow you.

Only after a week of the new site running cleanly should you cancel the old plan, and export anything you still need from it first — email, files, a final backup. Keeping the old host briefly is cheap insurance; cancelling it the day you switch is the single most common way a migration goes from smooth to stressful.

The bottom line

Migrating WordPress is routine when you do it in order: back up, package, restore, test on a temporary URL, then switch the domain, keeping the old host live until the new one is confirmed. Free host migration removes most of the risk, and the cleanup checklist afterward stops small problems surfacing later. Choose a new host that makes migration easy — the best affordable WordPress hosting ranking flags which ones do — and a move that sounds scary becomes an unremarkable afternoon.