Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.
I’ve moved a lot of client sites onto WP Engine over the years, and the Site Migration plugin does most of the heavy lifting. You install it on the old site, paste in a connection string, and it copies the database and files across. Here’s how it works in 2026, plus the snags that tend to stop a migration halfway.
Before you start
Both the old site and the new WP Engine environment need to meet these minimums:
- WordPress 5.0 or newer
- PHP 7.4 or newer
- MySQL 8.0
- The WordPress REST API turned on
- A current browser (Chrome, Firefox, Safari, or Edge)
You also need a WP Engine plan with an empty environment to migrate into. If you’re still picking one, my WP Engine plans comparison covers the differences. Take a backup on your current host before you begin. The plugin doesn’t change the source site, but it’s cheap insurance.
Step 1: Prepare the WP Engine site
- Log in to the User Portal and open Sites.
- Click the environment you’re migrating into.
- Open Site migration in the left menu (it sits under Manage if the menu is collapsed).
- On the Automated migration tab, click Install plugin.
- When the success message shows, copy the connection information. You will paste it into the old site in a minute.
Step 2: Install the plugin on your old site
- Download the Site Migration plugin ZIP from the same screen in the User Portal.
- Log in to wp-admin on your current host (not WP Engine).
- Go to Plugins > Add New Plugin > Upload Plugin, choose the ZIP, then install and activate it.
Step 3: Run the migration
In the old site’s wp-admin, open Site Migration, click Start a new migration, paste the connection information, and click Connect. Then pick a migration type:
| Type | What it copies | When to use it |
|---|---|---|
| Full site migration | All database tables and wp-content files, and it updates your domain in the database (serialized data included) | Most sites. Start here. |
| Customize the migration | Only what you pick: tables, media, themes, plugins, must-use plugins, other wp-content files, and root files | When you need root files, want to skip large folders, or are re-syncing |
Add an email address if you want status updates, click Start Migration, and keep the status page open. A full migration skips logs, backups, caches, and any plugins WP Engine doesn’t allow.
Step 4: Sync again right before you switch DNS
If the old site keeps getting new posts, orders, or comments while you test, run the plugin a second time just before go-live. You can reuse a saved profile, or build a custom one that only copies changed tables, media uploaded after a set date, and plugins or themes you added or updated.
Step 5: Test, add your domain, and go live
- Check the site on its WP Engine URL. If something breaks, compare the PHP and WordPress versions with your old host first.
- Add your domain in the User Portal.
- Point DNS to WP Engine. If you use the Advanced Network or Global Edge Security, SSL and the CDN are set up for you.
- Run a search and replace if any pages still reference the old domain.
- Review cache exclusions for things like login or checkout pages.
My WP Engine go live checklist post walks through the portal’s own checklist for this part.
Common problems and fixes
| Problem | What to do |
|---|---|
| Redirects or access rules stopped working | WP Engine doesn’t read .htaccess. Recreate those rules in the Web Rules Engine. |
| Migration slows down or gets blocked | Security plugins with a firewall, like Wordfence, can rate limit the plugin. Pause the firewall during the move. |
| Failed loopback request error | The old server has to resolve its own hostname. Turn off Cloudflare Under Attack mode while you migrate. |
| Stalls on a LiteSpeed host | WP Engine’s support article has a short .htaccess snippet for the source site that usually fixes it. |
| Destination is password protected | Enter the Basic Auth username and password when the plugin asks. |
| Multisite network | Convert the WP Engine site to multisite first. You can move a whole network, not single subsites. |
If it still fails, contact WP Engine support with the environment name, the error message, and the migration ID from the error page or failure email. Business plans also include managed migrations, so WP Engine will do it for you.
Need a home for the site first? Every WP Engine plan includes the migration plugin, staging, and daily backups.
FAQ
Is the WP Engine migration plugin free?
Yes. The Site Migration plugin is free to use for moving a site into a WP Engine environment.
Will my site go down during the migration?
No. Your old site stays live the whole time. Visitors only reach the WP Engine copy after you point DNS to it.
Can I migrate a single site out of a multisite network?
No. The plugin can move a whole network into a WP Engine site that has already been converted to multisite, but not individual subsites.