When It's Time to Move Hosts
People move WordPress sites for a handful of reasons: slow loading even after optimization, frequent downtime, poor support, rising renewal prices or a site that has outgrown shared hosting. Moving is very manageable if you follow a clear process. The key is to copy and test first, then switch, and only then cancel the old host.
If you have not chosen a new host yet, see the best WordPress hosting guide and the managed WordPress hosting comparison. For a move from shared hosting to a managed cloud platform, the Cloudways review and Hostinger vs Cloudways are useful.
Before You Migrate: Preparation Checklist

Do these a day or two before the move:
- Choose and set up the new hosting plan, and note its server details.
- Take a full backup of the current site, files and database, and keep a copy on your computer.
- Check PHP and WordPress versions. Make sure the new host supports the PHP version your site and plugins need. You can see your current version under Tools → Site Health → Info → Server.
- Audit email. If your email runs on the old host, plan where it will live. Check your domain's MX records.
- Lower your DNS TTL to around 300 seconds (five minutes) at your DNS provider, 24 to 48 hours before the move. This makes the final switch take effect faster.
- Clean up the site. Delete unused plugins, themes, spam comments and old backups stored inside the site to make the transfer smaller.
- Pause changes. Plan a short content freeze during the move so no new posts, comments or orders are lost.
For WooCommerce stores, schedule the move for a quiet period, since orders placed on the old site after the copy will not appear on the new one.
Three Ways to Migrate WordPress
| Method | Effort | Best For | Watch Out For |
|---|---|---|---|
| New host's migration service or tool | Lowest | Most sites | Scheduling and access details |
| Migration plugin | Low | Small to medium sites | Plugin size limits and server timeouts |
| Manual migration | Highest | Large sites, developers, plugin failures | Database and configuration steps |
Method 1: Let Your New Host Migrate the Site
Many WordPress hosts include a free migration, either as a self-service tool or a request handled by their team. For example, Cloudways offers free WordPress migration with its plans and provides a migration plugin, and Hostinger provides a free automatic migration tool for WordPress sites.
The usual process:
- Submit a migration request or start the tool from the new host's dashboard.
- Provide access to your current site, such as a WordPress admin login, or install the host's migration plugin on the old site.
- Wait for the copy to complete.
- Test the migrated site using the temporary URL or preview domain the host provides.
- Switch DNS when you are happy, as described below.
This is the lowest-effort route and is ideal for most owners.
Method 2: Use a Migration Plugin
If your host does not offer migration, or you prefer to do it yourself, a migration plugin packages your site and restores it on the new server. Well-known options include Migrate Guru, Duplicator and All-in-One WP Migration. Free versions often have limits on site size or features, so check the plugin's details before starting.
A typical plugin migration:
- Install WordPress on the new host, using a temporary domain or the host's preview URL.
- Install the migration plugin on the old site, and on the new site if the plugin requires it.
- Create the migration package or start the transfer from the old site.
- Import or restore the package on the new site.
- Log in to the new site, using the old site's admin credentials, which have been copied over.
- Save permalinks once under Settings → Permalinks to refresh rewrite rules.
- Test thoroughly before switching DNS.
Method 3: Migrate WordPress Manually
Manual migration gives you full control and works when plugins time out on large sites. It requires access to files and the database.
Step 1: Copy the Files
Connect to the old server with SFTP or the host's file manager and download the whole WordPress directory, including wp-content (themes, plugins and uploads) and wp-config.php.
Step 2: Export the Database
Open phpMyAdmin or use your host's database tool. Select your WordPress database and export it as an SQL file.
Step 3: Create a Database on the New Host
In the new host's control panel, create a new database, a database user and a strong password. Give the user full privileges on the database.
Step 4: Import the Database
Open phpMyAdmin on the new host, select the new database and import the SQL file.
Step 5: Upload the Files
Upload the WordPress files to the new server's web root, often public_html.
Step 6: Update the Configuration File
Edit wp-config.php on the new server with the new database name, username, password and host:
define( 'DB_NAME', 'new_database_name' );
define( 'DB_USER', 'new_database_user' );
define( 'DB_PASSWORD', 'new_password' );
define( 'DB_HOST', 'localhost' );
Your host's documentation tells you the correct DB_HOST value if it is not localhost.
Step 7: Test Before Switching DNS
To view the new site before DNS changes, use the host's temporary URL if it supports WordPress, or edit your computer's hosts file to point your domain at the new server's IP address. Remove the hosts file entry when you finish testing.
If your domain is changing as well as your host, you will also need to search and replace the old domain in the database with a tool designed for serialized WordPress data, and set up 301 redirects from the old domain.
Changing Domain at the Same Time
If you are moving to a new domain as well as a new host, do it in two stages where possible: move hosts first and confirm everything works, then change the domain. Changing both at once makes problems harder to diagnose. A domain change also needs 301 redirects from every old URL and a change of address in Google Search Console.
Switching DNS Without Downtime
Once the new site works, point the domain to the new host:
- Find the new server's IP address or nameservers in your new host's dashboard.
- Update the DNS records at your domain registrar or DNS provider. Either change nameservers to the new host's, or update the A record (and AAAA record if used) to the new IP.
- Keep email records intact. If you change nameservers, recreate your MX and other email records at the new DNS provider first.
- Wait for DNS to update. With a low TTL, most visitors reach the new server within minutes to a few hours, though some networks can take longer.
- Set up SSL on the new host once the domain points there, if it is not issued automatically.
- Keep the old hosting active for several days, in case you need to roll back or copy anything you missed.
During the switch, some visitors see the old server and some the new one. That is why a short content freeze matters.
After the Move: Testing Checklist
| Check | What to Look For |
|---|---|
| Homepage and key pages | Load correctly, with images and styles |
| Admin login | Works on the new server |
| Permalinks | Posts load, no 404 errors |
| Forms | Test submissions arrive |
| Store checkout | Test order and payment notifications |
| SSL | Padlock shows, no mixed-content warnings |
| Sends and receives as expected | |
| Caching | Host or plugin caching set up and cleared |
| Search engines | Settings → Reading does not block indexing |
| Speed | PageSpeed Insights results on mobile |
| Backups | New host's backups are running |
| Cron and scheduled tasks | Scheduled posts and plugin tasks run |
Then submit your sitemap again in Google Search Console and keep an eye on crawl errors for a week or two.
Common Migration Problems and Fixes

| Problem | Likely Cause | Fix |
|---|---|---|
| "Error establishing a database connection" | Wrong details in wp-config.php | Check database name, user, password and host |
| Posts return 404 errors | Rewrite rules not refreshed | Re-save permalinks; check .htaccess or server rules |
| Images missing | Uploads folder not copied fully | Re-upload wp-content/uploads |
| Mixed-content warnings | Some URLs still use http:// | Update site URLs and run a safe search and replace |
| White screen | PHP version or plugin conflict | Check error logs; match PHP version; disable plugins |
| Plugin migration times out | Site too large for server limits | Use host migration, a different plugin or manual method |
| Email stopped working | MX records lost during DNS change | Restore MX records at your DNS provider |
Migrating a Large or Busy Site
Large sites need extra care:
- Exclude unnecessary files from the transfer, such as old backups stored in wp-content and cache folders, which can be enormous.
- Move the database separately if a plugin times out, using command-line tools or your host's import tools for large SQL files.
- Plan a final sync for active sites: copy everything, test, then re-sync recent posts, comments or orders just before switching DNS.
- Ask the new host for help. Many WordPress hosts will handle large migrations, which is often faster and safer.
Choosing a Host You Won't Need to Leave
Moving hosts is manageable, but most people would rather do it once. When comparing hosts, look beyond the first-term price: check renewal pricing, backup frequency, staging, support quality and how easily you can scale. Our best WordPress hosting guide, the Cloudways review and the WPX hosting review cover options at different price points.
After the move, follow our WordPress speed optimization guide to get the most from your new server.
Final Thoughts
A safe WordPress migration follows one rule: copy, test, switch, then cancel. Prepare by backing up and lowering DNS TTL, choose the migration method that suits your site, test on a temporary URL, switch DNS during a short content freeze and keep the old host running for a few days. Done that way, most visitors will never notice the move, apart from a faster site.
For more help, browse all our WordPress guides.
Frequently Asked Questions
How Long Does It Take to Migrate a WordPress Site?
A small site can be copied in under an hour with a plugin or host migration service. DNS changes can take a few hours to fully take effect, so plan the switch and keep the old hosting active for a few days.
Will Migrating WordPress Cause Downtime?
It does not have to. Copy the site to the new host, test it there, then switch DNS. Visitors reach the old site until DNS updates, and the new site afterwards. Avoid publishing changes during the switch.
Will Moving Hosts Affect My SEO?
If the domain, URLs and content stay the same, a host move should not hurt SEO. Problems usually come from broken URLs, missing redirects, mixed content or the new site accidentally blocking search engines.
What Is the Easiest Way to Migrate WordPress?
The easiest way is usually your new host's free migration service or tool. Many WordPress hosts include one. Migration plugins are the next easiest and work with almost any host.
Do I Need to Move My Domain When I Change Hosts?
No. You can keep the domain at its current registrar and simply point its DNS records to the new host. Moving the domain is a separate, optional task.
What About My Email?
If your email is hosted with your old web host, it will stop working when you cancel that hosting unless you move it. Check your MX records and plan your email move before changing DNS.
Moving to Faster Hosting? Cloudways Includes a Free WordPress Migration
Check the current plans, site limits and refund terms on the official Cloudways website.
See Cloudways Plans