How to Move Your WordPress Site to a New Host in 2026

I still remember the night my old host let me down. My blog had just been shared by a big newsletter, visitors were pouring in, and my site answered them with a white screen. I refreshed, I waited, I opened a support ticket, and I got a reply that basically said “try again later.” That was the night I decided to move. I was scared, because I had heard the horror stories: lost posts, broken images, weeks of lost Google traffic. But I moved anyway, and I have since moved three WordPress sites to new hosts without losing a single post. In this guide, I will show you exactly how to move your WordPress site to a new host in 2026, step by step, in plain words. If you own a WordPress blog, a small business site, or a news site like mine, and your host is slow, expensive, or unhelpful, this guide is for you. By the end, you will know which method fits your site, and you will have a checklist you can follow tonight.

Trust nudge: I am not paid by any host mentioned here. The steps below come from my own moves and from public migration guides I checked during my research, and where guides disagree, I tell you the safer option instead of the faster one.

What You Will Learn in This Guide

• How to back up your whole site so a failed move costs you nothing
• Which migration method fits your site: free host migration, plugin, or manual move
• How to copy your files and database to the new host without breaking links
• How to switch your DNS safely and avoid downtime
• How to test everything before you cancel your old hosting account
• The mistakes that break most migrations, and how to dodge every one
• Answers to the questions I get asked most about moving hosts

Before You Touch Anything: Back Up Everything Twice

I learned this lesson the hard way, so let me save you from it. On my very first move, I trusted a single backup file, and that file turned out to be broken. I spent a weekend rebuilding pages from Google’s cache. Never again. Now I make two backups before every move: one full backup through my hosting control panel, and one through a backup plugin. A full backup means two things: all your files (WordPress core, themes, plugins, uploads) and your database (posts, pages, comments, settings). If either half is missing, your site cannot be rebuilt. Good migration guides all start the same way: take a full backup of the files and database first, before you pick any method at all.

Keep those backups somewhere safe, not only on the old host. Download them to your computer. I also keep a copy on an external drive, because I follow the same habit I wrote about in my guide to backing up a computer with the 3-2-1 rule: more than one copy, in more than one place. While you are at it, write down three things from your old host: your database name, username, and password, plus your PHP version. You will need them later, and hunting for them mid-move is stressful. If your site earns money, pick a quiet time for the move, like a weekend night, and tell your readers with a short notice if you can. A calm move beats a fast move every time.

Pick the Right Migration Method for Your Site

I have used all three methods, and each one suits a different kind of site. The first method is the easiest: ask your new host to move the site for you. Many hosts offer a free migration service, and for a normal blog or business site, this is honestly the best choice. You give them your old login details, they copy everything, and you test the result. I used this for my smallest blog, and it took me about twenty minutes of actual work. The catch is that some hosts limit free migrations to one site, or take a few days during busy weeks, so ask about timing before you pay.

The second method is a migration plugin, and it suits small and medium sites where you want control. Popular plugins include Duplicator, All-in-One WP Migration, and Migrate Guru. With Duplicator, you build a package on the old site, download an installer file and a zip archive, upload both to the new host, and run the installer. It walks you through connecting the new database, and it handles the URL changes for you. I like plugins because they package everything into one tidy bundle, but free versions often limit site size, so check your site’s size first. If your uploads folder alone is several gigabytes, a plugin may struggle, and that is your signal to use the third method.

The third method is the manual move, and it suits large or complex sites, including multisite networks and stores with heavy custom code. You download the files with SFTP, export the database from phpMyAdmin, upload everything to the new host, import the database, and edit wp-config.php with the new database details. It sounds technical, and it is, but it gives you total control, and nothing hides from you. My news site moved this way, because I wanted to see every step. If the words SFTP and phpMyAdmin already scare you, do not force this method. Use the host migration or a plugin instead. Choosing the method you actually understand is not laziness. It is how you avoid breaking your site.

Move the Files and Database, Step by Step

Here is the manual path in plain steps, because even plugin users should understand what happens underneath. First, set up the new hosting account and create a fresh, empty database there, with a new database user that has all privileges. Write down the new database name, username, password, and host address. Second, download all your WordPress files from the old host’s public_html folder, and upload them to the new host’s root folder. Third, export the old database as a .sql file from phpMyAdmin, then import that file into the new database on the new host. Standard transfer checklists list exactly this order: export from phpMyAdmin, upload files, create the new database, import, then update wp-config.php.

Fourth, open wp-config.php on the new host and replace the old database name, username, and password with the new ones. Fifth, if your domain name is also changing, run a search-and-replace on the database so every stored link points to the new address. Plugins like Duplicator do this automatically, but manual movers must do it carefully, because WordPress stores full URLs inside post content and settings. Never edit the .sql file in a plain text editor and save it carelessly, because serialized data breaks if a string length changes. Use a proper search-and-replace tool that understands serialized data. If your domain is staying the same and only the host changes, you can skip the URL replace entirely, which is one reason a same-domain move is simpler than a domain change.

The DNS Switch: The Moment Everyone Fears

Here is the part I feared most on my first move, and it turned out to be the simplest part once I understood it. DNS is the system that tells the world which server your domain points to. Before you switch it, lower your DNS TTL a day or two in advance. TTL means “time to live,” and lowering it tells other servers to re-check your domain sooner. Migration guides recommend lowering the TTL in the preparation step so the change propagates faster when you switch, and one guide notes that with a lowered TTL, propagation can finish within minutes rather than the standard 24 to 48 hours. I lower mine to 300 seconds, which is five minutes, a full day before the switch.

Before you switch DNS, test the copied site on the new host using its temporary URL or your computer’s hosts file. Click through your homepage, a few posts, your contact form, and your checkout if you have one. Check that images load and menus work. Good guides insist on this: test the copied site on the new server before you switch, using a temporary URL or your hosts file. Only when the copy looks right do you change the nameservers or A records at your domain registrar to point at the new host. Then you wait. Some visitors will see the new site within minutes, others within a day, because DNS updates spread gradually. That is normal, not a failure. Do not panic, and do not change things twice in one hour.

Test Everything Before You Cancel the Old Host

This is the rule I never break now: keep your old hosting account active for at least a week after the move. Experienced movers say the same: keep your old host active until you are sure everything is stable. During that week, I run a checklist. I check HTTPS, because a missing SSL certificate will scare visitors with a warning. I submit the site to Search Console again if anything changed, and I resubmit my sitemap. I test every form, because contact forms fail silently more than any other feature. I test email sending, because a new server sometimes blocks it. I clear caches, including any CDN cache, so visitors see the new site instead of stale copies.

I also watch for the quiet problems. Mixed content warnings happen when some images still load over old http links. Broken internal links happen when a URL replace missed a corner of the database. A plugin that worked on PHP 8.1 may complain on PHP 8.3, so check your new host’s PHP version matches what your site needs. If you moved to a host you picked from a comparison, like the plans in our best WordPress hosting comparison for bloggers and news sites or our best cheap web hosting guide, this is the week to confirm the speed promise was real. Run a speed test on the new host and compare it with your old numbers. If it is slower, say so to support while you still have the old host as a fallback.

The Mistakes That Break Most Migrations

I have made, or watched friends make, every classic mistake, so here they are in one place. The first is cancelling the old host on day one. If the new copy has a hidden fault, you have just deleted your safety net. The second is skipping the backup because “the plugin will handle it.” Plugins fail too. The third is forgetting email: if your domain’s MX records point to your old host’s mail service, changing nameservers without copying those records will break your email. Copy your MX records before you switch DNS, and check them after. The fourth is moving during your busiest week. A sale, a launch, or a viral moment is the worst time to move, because every hour of confusion costs real money.

The fifth mistake is ignoring SSL. Set up the certificate on the new host before you go live, not after, so visitors never see a security warning. The sixth is forgetting to clear caches, which makes a perfect move look broken because your browser keeps showing the old site. If something looks wrong after a move, clear your browser cache and try a different browser before you panic. And the seventh mistake is moving to the wrong host for the wrong reason. Price alone is a bad reason. Compare real plans first: our Cloudways vs SiteGround comparison for WordPress speed, our Hostinger Premium vs Unlimited guide, and our best ecommerce hosting guide for WooCommerce stores all exist so you pick on evidence, not on a discount banner. If you are still weighing shared against cloud, our shared vs VPS vs cloud hosting guide will help you choose before you move, not after.

Frequently Asked Questions

Will moving hosts hurt my Google rankings?

Done properly, no. Keep the same URLs, keep the site fast, and avoid downtime, and Google will barely notice. Expect small, temporary ranking wobbles during any move, and resubmit your sitemap in Search Console after the switch. Big traffic losses come from broken URLs and long downtime, not from the move itself.

How long does a WordPress migration take?

A small blog with a plugin can move in an afternoon. A large site moved manually can take a day or two of careful work, plus up to 48 hours for DNS to finish spreading worldwide. The actual file copy is rarely the slow part. Testing and DNS waiting are.

Do I need to change my domain to change hosts?

No. Changing hosts and changing domains are two different jobs. If only the host changes, your domain stays the same, your URLs stay the same, and you skip the search-and-replace step. That is the simpler move, and the one most people actually need.

What is the easiest migration method for a beginner?

Ask your new host’s free migration service first. If they do not offer one, use a plugin like Duplicator or Migrate Guru for a small or medium site. Try the manual method only when you are comfortable with FTP and phpMyAdmin, or when your site is too large for a plugin.

Should I cancel my old hosting right after the move?

No. Keep it active for at least a week, and longer if your site earns money. That week is your safety net while you test forms, email, HTTPS, and speed. Cancel only when the new site has run cleanly for several days.

What if my site shows a blank page after moving?

Check wp-config.php first: one wrong database detail causes a blank or error page. Then check the PHP version on the new host, deactivate plugins one by one if needed, and clear all caches. If you have your backups, you can always restore and try again calmly.

Will my emails break when I move hosts?

They can, if your MX records are not copied. Before switching DNS, note your email records from the old host, and make sure the same records exist after the switch. Test sending and receiving email on the new setup before you cancel anything.

Final Thoughts

I started this guide with the night my old host failed me, and I will end with what that night taught me. A slow or unhelpful host is not something you have to live with. Moving feels scary because the steps are unfamiliar, not because they are hard. Back up twice, pick the method you understand, test before you switch, and keep the old host for a week. That is the whole secret, and it has worked for me three times now. Your site deserves a host that answers fast and loads faster. If you move this week, congratulations in advance: you are about to give your readers a better experience, and yourself one less worry. Now tell me in the comments: what pushed you to move, speed, price, or support? I read every answer, and your story might help the next reader pick their new home.