Short answer: to migrate a WordPress site to a new host, back up your site, set up a fresh WordPress install on the new host, restore the backup there, test the copy and only then point your domain to the new server. Your old site stays online until you switch DNS, so visitors see no downtime as long as you test first.
This guide walks you through the whole process in plain language. You will learn why people switch hosts, what to prepare before you start, the three main ways to move your site, and the cleanup steps most guides skip. By the end you will be able to move your site with confidence, whether it is a simple blog, an online store or a large membership site.
Why Move Your WordPress Site to a New Host?
People rarely switch hosts for fun. There is almost always a reason that has been building for a while. Here are the most common ones.
- Slow loading speed. If your pages load slowly and your dashboard lags, a faster host can fix that quickly. Speed also affects rankings and conversions, so this is more than a comfort problem.
- Poor support. When something breaks at 2 a.m., you need a real answer, not a ticket that sits for three days.
- Rising prices. That cheap first year renews at a much higher rate. Many site owners fall into this trap when they see the renewal invoice.
- Outgrowing your plan. A small shared plan is fine for a starter blog. Once traffic grows, or you launch a store or membership site, you need more power and resources.
- Security and reliability. Frequent downtime, malware issues, or a setup that feels unstable are all valid reasons to move away.
- Whatever your reason, migrating a WordPress site to a new host follows more or less the same steps every time.
What You Need Before You Migrate (Pre-Migration Checklist)
This is the part most beginners rush, and it is exactly where migrations go wrong. Spend ten minutes here and you save yourself hours of stress later.
1. Create a full backup. Before you touch anything, make a complete copy of your website. That way your database, media, themes and plugins are saved in one package. Store it somewhere off your current host, such as your computer or cloud storage. If something goes wrong during the move, a clean WordPress backup lets you roll back in minutes.
2. Note your PHP version. Your new host may run a higher PHP version than your old one. Go to Tools, then Site Health, then Info, and check your server details. If the versions are very different, some plugins or themes can break after the move. Match the version where you can.
3. Lower your DNS TTL. TTL tells the internet how long to remember your old server address. Log in to your domain or DNS provider and reduce the TTL to a few hundred seconds (five minutes) at least a day before you migrate. This one change is the difference between a smooth switch and hours of some visitors seeing the old site while others see the new one.
4. Check your email. If your business email runs through your current host, moving can quietly break it. Confirm where your email lives before you move so messages keep arriving.
5. List your plugins. Write down the plugins that power key features, such as your payment gateway, reviews or booking tools. You will want to confirm each one works after the move.
Once these five boxes are checked, you are ready to choose a method.
3 Ways to Migrate a WordPress Site to a New Host
There are three common paths. Pick the one that matches your comfort level and your site size.
- Use a migration plugin. The easiest and safest option for most people. A plugin packs up your whole site and unpacks it on the new host. No code required.
- Let your host migrate it. Many hosts offer a free migration service and do the heavy lifting for you.
- Migrate manually. The hands-on route using FTP and your database. Best for advanced users or unusual setups.
We will start with the plugin method because it works for almost everyone.
How to Migrate a WordPress Site to a New Host Using a Plugin
A good plugin handles the boring parts: exporting your files and database, then restoring them on the new host. This is where Demi makes life easier. Demi is a free all-in-one tool that combines demo import, backup, migration and search and replace in one dashboard, so you do not need several plugins fighting each other. You can get it from the Demi page on WordPress.org and follow the site migration documentation alongside this guide.
Here is the full process.
Step 1: Set up your new host
Buy your new hosting plan and set up a fresh copy of WordPress on it. Most hosts offer one-click WordPress installs. You do not need to add any content. An empty WordPress install is all you need to receive your site.
Step 2: Install Demi on your current site
On your current (old) WordPress site, go to Plugins, then Add New, search for Demi, then click Install and Activate. You will see the Demi menu under Appearance in your dashboard.
Step 3: Create a backup and export your site
Open Demi and create a full backup. This packs your database, media, themes and plugins into a single file. Download the backup file to your computer. (Demi also has one-click demo import for starting new projects, but for a migration you only need the backup.)
Step 4: Install Demi on the new site
Log in to the fresh WordPress install on your new host. Install and activate Demi here too, exactly as you did on the old site.
Step 5: Import your site
In Demi on the new host, choose Import and upload the backup file you downloaded, then restore it. Demi rebuilds your site on the new server, including your content, settings and media. If your domain name is changing, use Demi’s search and replace tool afterwards to update old URLs, using a dry run first to preview the changes.
Step 6: Check that everything loaded
Browse your new site before you point your domain at it. Click around, open a few pages and check that your images, menus and key features are all in place.
That is the complete plugin method. For most websites, it takes minutes, not hours.
How to Migrate a WordPress Site Manually (Advanced)
If you prefer to stay in control, or your host has unusual limits, you can move your site by hand. This path has more steps and more room for error, so go slowly.
- Export your database. Open phpMyAdmin on your current host and export your WordPress database as a SQL file.
- Download your files. Connect with an FTP client such as FileZilla and download your full WordPress folder, including wp-content.
- Upload to the new host. Create a new database on the new host, then upload your files and import your SQL file.
- Edit wp-config.php. Update the database name, user and password in your wp-config.php file so WordPress can connect.
- Update your URLs. If your domain is changing, run a search and replace on the database to swap old URLs for new ones, taking care with serialized data.
The manual approach works, but it is the reason most people choose a plugin instead.
How to Migrate Through Your Hosting Provider
Plenty of hosts will move your site for you at no cost when you sign up. You give them your current login details, they handle the transfer, and you check the result. If you are short on time or nervous about the technical side, this is a stress-free choice. Just ask your new host whether free migration is included before you start.
Migrating a Store, Membership or Directory Site
Simple blogs are light. Stores, membership sites and directories are not. They carry far more data and far more risk, so a move deserves extra care.
Think about everything packed into a busy site like this:
- Hundreds or thousands of products or listings with images and details
- Member and customer accounts, some tied to recurring subscriptions
- Orders, invoices and checkout settings
- Custom forms, search filters and category settings
- Payment gateway and tax settings
- Years of reviews and comments
Losing any of this during a move is a real problem, which is why a full backup matters even more for these sites. Before you migrate, confirm your products, members and payment settings are all captured in your backup. Pause new orders or sign-ups while you move so nothing is lost between the backup and the switch. After you migrate, place a test order, submit a test form and run a search to confirm everything still works. Keeping this data intact also protects your search rankings, since broken pages and missing listings can hurt your visibility.
What to Do After Migrating (Post-Migration Checklist)
The move is not finished when the import bar hits 100 percent. These final steps lock in a clean result.
Test your whole site. Open key pages, fill out a form, and run a search. Click your most important links and load a few images to confirm nothing broke.
Re-save your permalinks. Go to Settings, then Permalinks, and click Save twice. This refreshes your link structure and prevents 404 errors.
Point your domain to the new host. Update your DNS records so your domain loads the new server. Because you lowered your TTL earlier, this switch happens quickly.
Confirm your SSL certificate. Make sure your new host has a valid SSL so your site loads over https with no security warnings.
Check your email again. Send a test message to confirm your business email still works after the move.
Update Google Search Console. If your domain changed, tell Search Console so your rankings carry over cleanly.
Keep your old host for a week or two. Do not cancel right away. Leave the old account active for seven to fourteen days as a safety net in case you need to roll back.
Common WordPress Migration Problems (and Fixes)
Even smooth migrations hit the odd snag. Here are quick fixes for the usual ones.
Blank white screen. Often a PHP version mismatch or a plugin conflict. Switch your PHP version to match the old host, or deactivate plugins one by one to find the culprit.
Broken images. Usually a URL issue. Re-save your permalinks and run a search and replace to fix old links pointing at the previous domain.
Cannot log in. After a migration your login details come from the site you imported. Use the username and password from your old site.
Upload size error. If your backup is larger than the new host’s upload limit, raise the PHP max upload and memory limits, or import in smaller pieces.
Mixed content warning. This appears when some links still load over http. A simple search and replace from http to https across your database clears it.
Conclusion
Moving hosts feels risky, but it does not have to be. When you prepare a backup, lower your DNS TTL, choose the right method and work through a post-migration checklist, you can migrate a WordPress site to a faster host without downtime and without losing data. A plugin keeps everything simple, and a single all-in-one tool makes it even simpler by handling your backup, your migration and your URL updates in one place.
Whether you are moving a small blog or a busy store, the steps above give you a clear path from start to finish. If you are weighing your options, compare the best WordPress migration plugins, or read the longer step-by-step WordPress migration guide.
Ready to move your site the easy way?
Demi gives you demo import, backup, migration and search and replace in a single free plugin, so you can move your WordPress site without the stress. Visit WP Demi to get started today.
FAQ’s
1. How long does it take to migrate a WordPress site?
With a plugin, most websites move in a few minutes. Larger sites and manual migrations can take longer, but the plugin method is the fastest for almost everyone.
2. Will migrating affect my SEO rankings?
Not if you do it right. Keep your URLs the same, re-save your permalinks, and update Google Search Console if your domain changes. A clean migration protects your rankings.
3. Can I migrate a WordPress site for free?
Yes. A free plugin like Demi lets you back up and migrate your site without a fee, and many hosts also offer free migration when you sign up.
4. Do I need to keep my old host after migrating?
Keep it active for one to two weeks. This gives you a safe fallback if you spot a problem and need to switch back quickly.
5. Can I migrate a large WordPress site without hitting a size limit?
Yes, as long as your server settings allow it. If your backup is larger than the upload limit, raise your PHP max upload and memory limits before importing.