How to Move WordPress to a New Host: Step-by-Step Guide

You move WordPress to a new host by backing up your files and database, copying them to the new server, testing the site there, and then pointing your DNS at it. Testing before the DNS switch is what keeps the move from causing downtime.

A host move fixes server problems, and sometimes the problem is WordPress itself. We cover both below, and if you decide to rebuild instead of relocate, our Wordpress migration service programs are one way to do that.

How do you move WordPress to a new host step by step?#

Start by checking that the new host runs a PHP version and database version your WordPress install supports. Do this before you buy anything, because a mismatch shows up later as a white screen.

Next, take a full backup. You need two things: the files (at minimum the wp-content folder and wp-config.php) and a database export. A backup plugin works, and so does WP-CLI's database export command or phpMyAdmin. Store the copy somewhere other than the old server.

Then build the site on the new host. Upload the files, create an empty database, import your export, and update the database name, user and password in wp-config.php. If you're testing on a temporary URL rather than your real domain, run a search-replace on the database so internal links don't point back to the old address.

Don't change DNS yet. Test first. Edit the hosts file on your own computer so your domain resolves to the new server's IP address, and you'll see the new site while everyone else still sees the old one. Click through your key pages. Submit every form, log in, check that images load, confirm permalinks and redirects work, and run a test checkout if you sell anything.

How do you handle SSL and DNS without downtime?#

SSL needs to be settled before you touch DNS. Most hosts issue free certificates through Let's Encrypt, but some can only issue one once your domain points at them. Check how your host does it so you aren't surprised mid-switch. After the certificate is live, look for mixed-content warnings, which usually come from old http:// image or script links in the database.

A day or two before the move, lower the TTL on your DNS records to something short, such as 300 seconds. A short TTL means the change spreads quickly when you flip it. Leave your MX records alone unless your email is moving too, since changing them by accident is how businesses lose mail for an afternoon.

On switch day, pause content edits and new orders for a short window so nothing lands on the old server after you've copied it. Update the A record to the new IP. Keep the old hosting account running for at least a few days, because some visitors will still reach it while DNS settles.

After the switch, confirm your tracking pixels are firing and scan for new 404 errors. Then resubmit your sitemap in Google Search Console. Cancel the old host only once all of that looks clean.

Will a new host fix what's wrong, or should you move off WordPress?#

Whether a new host is enough depends on what made you want to move in the first place. If the complaints are about server performance, a better host is the right fix and the steps above are all you need. Plenty of owners should stop there.

If the complaints are about the site itself, a host won't change much. Think of the plugin and theme updates, the security patches, the page builder that makes every edit a chore, or the developer you have to call for a small text change. Those travel with the site to any host.

That's the case Captive Studio is built for. We're part of the agency Captive Demand, and we rebuild your WordPress site on our own platform, hosted on Vercel. You edit the site by asking in chat, and a real web team handles the rest. There are no plugins to update.

The way in is a free WordPress migration, normally a $5,000 project. We rebuild the site pixel-perfect in 2 business days. We keep your URLs and SEO tags intact, and your tracking pixels move with the site. Then you get a 3-day free trial. Captive Studio is invite-only for now. You can read more in our free WordPress migration service post, or see how chat editing works on the AI website editor page.

Quick answers about moving WordPress to a new host#

How long does it take to move WordPress to a new host?

The copy itself can take an hour or so for a small site. Plan extra time for testing on the new server and for DNS to settle after the switch.

Will I lose SEO rankings if I change hosts?

Rankings shouldn't drop just because the host changed, as long as you keep your URLs, redirects, title tags and meta descriptions identical and confirm the site loads over HTTPS. Check Search Console afterward for new errors.

Do I need to take my site offline during the move?

Visitors keep reaching the old server until DNS points to the new one, so the site stays up during the move. Just pause content changes and orders briefly around the switch so nothing is lost.

When should I leave WordPress instead of just changing hosts?

When your frustration is with updates, plugins, security upkeep or hard-to-make edits, those problems follow you to any host.

If you'd rather stop maintaining WordPress altogether, take a look at our Wordpress migration service programs and see whether Captive Studio is a fit.