How to Move WordPress Site to New Host Without Downtime (2026 Guide)

Learning how to move WordPress site to new host without breaking anything is a skill every site owner should have. Switching hosts does not have to mean downtime, lost posts, or broken images. The secret is simple: build and test the full copy of your site on the new host first, and only then point your domain at it.

Before You Start: The WordPress Migration Checklist

Never start a move without a safety net:

Take a full backup. Use UpdraftPlus or a similar plugin to save a complete copy of your files and database, and download it to your own computer.
Note your current setup. Check your PHP and MySQL versions under Tools > Site Health > Info, and confirm the new host matches or beats them.
Lower your DNS TTL 24 to 48 hours ahead. TTL (time to live) tells the internet how long to cache your domain’s DNS records. Dropping it to 300 seconds a day or two early makes the switch propagate much faster.
Pause major changes. Do not publish posts or accept orders during the migration window — content added afterward will not appear on the new site.
Gather your logins for both hosting panels and your domain registrar.

Method 1: How to Move WordPress Site to New Host with a Plugin

For most non-developers, a migration plugin is the safest route. All-in-One WP Migration and Duplicator both follow the same pattern: export on the old host, install fresh WordPress on the new host, then import.

All-in-One WP Migration Guide: Export and Import

Install and activate All-in-One WP Migration on your old site.
Go to All-in-One WP Migration > Export, choose Export to File, and download the .wpress file.
On your new host, install fresh WordPress and the same plugin.
Go to All-in-One WP Migration > Import, drag in your .wpress file, and confirm. The plugin replaces the fresh install with your old site.
When prompted, save your permalinks twice to flush the rewrite rules.

About file-size limits: many older guides claim the free version caps imports at 512 MB, but the plugin maker states the free plugin itself imposes no hard cap — the limit you see comes from your new host’s PHP upload settings, as explained in ServMask’s own breakdown of the upload limit. If your export exceeds it, ask your host to raise it, or buy the Unlimited Extension (about $69/year).

Duplicator Migration: The Package and Installer Route

Duplicator creates a package: an archive (a zip of your site) plus an installer.php file.

Install Duplicator on your old site, create a package, and download both files.
Upload both to the root folder of your new hosting account via FTP or your host’s file manager.
Visit yourdomain.com/installer.php and follow the steps: it extracts the files, connects the database, and updates URLs if your domain changed.
Delete the installer files immediately when finished — leaving them on a live server is a security risk.

Duplicator’s free version (Duplicator Lite) suits small to medium sites, while drag-and-drop imports and large-site support require Duplicator Pro — see Duplicator’s own free vs Pro comparison.

Method 2: How to Move WordPress Site to New Host Manually

This WordPress manual migration costs nothing and works on any host, and it is the fallback when a plugin import fails on a very large site.

Download your files. Connect to your old host with an FTP or SFTP client such as FileZilla and download everything — at minimum the wp-content folder and your wp-config.php file.
Export your database. In your old host’s control panel, open phpMyAdmin, select your database, click Export, choose Quick and SQL format, and download the file.
Create the new database. On your new host, create an empty database and a user with all privileges on it. Note the database name, username, and password.
Upload your files to the correct folder on the new host (usually public_html).
Import the database. Open phpMyAdmin on the new host, select the new empty database, click Import, and upload your SQL file.
Update wp-config.php on the new host so DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST match your new database credentials.
Search and replace only if your domain changes. Keeping the same domain? Skip this step. If the domain is changing too, use the Better Search Replace plugin or WP-CLI’s search-replace command. Never run raw SQL find-and-replace on the live database without a backup — it can corrupt serialized data.

Plugin Method vs Manual Method: Which Should You Choose?

	Plugin method	Manual method
Skill level	Beginner-friendly, no code	Comfortable with FTP and phpMyAdmin
Time	30 minutes to 2 hours for most sites	1 to 3 hours depending on site size
Cost	Free for most sites; paid extension for very large ones	Free
Best for	Bloggers and small business owners who want a safe, guided move	Developers, very large sites, and failed plugin imports

If you are moving mainly because your hosting bill jumped, compare plans before you commit. Our guide to the cPanel price increase and 2027 hosting costs explains what to watch for.

Switching DNS Without Downtime

Follow this order exactly:

Test on a staging or temporary URL first. Most hosts provide a temporary address, or you can preview the new site by editing your computer’s hosts file.
Point your DNS at the new host. Update the A record (or nameservers, if your new host asks for that) at your domain registrar.
Keep the old host live. Do not cancel it yet. During WordPress DNS propagation downtime windows, some visitors reach the old server while others reach the new one — keeping both live means nobody sees an error.
Wait for propagation. It can take up to 48 hours, but most visitors switch within a few hours, and your lowered TTL speeds this up.
Cancel the old plan only after a week with no issues, once you have confirmed no email accounts or subdomains still live there.

Post-Migration QA Checklist

Once DNS has settled, work through this checklist:

Resave permalinks (Settings > Permalinks > Save Changes) so no post returns a 404 error.
Check your SSL certificate. Visit your site with https:// and confirm the padlock shows.
Test contact forms by submitting a real message and confirming it arrives.
Purge all caches (plugin, host, CDN), then reload and look for broken images or styling.
Verify email and DNS records, including MX records.
Check Search Console and Analytics to confirm traffic is still recorded and no crawl errors spiked.

Prefer a professional to handle the move? See our services or contact us.

Common Mistakes to Avoid

Canceling the old host too early — the number one cause of data loss during a move.
Skipping the backup. Even a “simple” plugin migration can fail halfway.
Forgetting the permalink resave, which leaves posts returning 404 errors.
Changing hosts and domains at the same time without a plan. Do one change at a time when you can.
Ignoring PHP and MySQL versions. A site built on newer PHP can break on an older server.
Leaving installer files on the server. Delete Duplicator’s installer and archive after the move.

Newer server software can also unlock newer WordPress features — see the WordPress 7.2 beta features for 2026.

Frequently Asked Questions

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

For a typical small to medium site, the plugin method takes 30 minutes to 2 hours, plus DNS propagation time.

Will moving my WordPress site to a new host cause downtime?

Not if you build and test the site on the new host first, then switch DNS, keeping the old host live until propagation finishes.

Can I move my WordPress site without losing SEO rankings?

Yes, as long as your URLs stay the same, your content is identical, and the site is not offline for days. After the move, check Google Search Console for crawl errors.

What is the easiest way to move a WordPress site for a beginner?

All-in-One WP Migration is the simplest option: export a single file from the old site, install fresh WordPress and the same plugin on the new host, and import.

Do I need to change nameservers or just the A record?

Either works. Changing the A record to the new host’s IP address is the smaller change. Switching nameservers hands all DNS control to the new host.

Conclusion

Now you know how to move WordPress site to new host safely: back up everything, lower your DNS TTL, copy the site with a plugin or manually, test it on the new server, and only then switch your DNS, keeping the old host alive until propagation completes. Your visitors will never know your site moved at all.