Product facts · Guide
How to Migrate a WordPress Site to WP Engine
Short answer
To migrate a WordPress site to WP Engine, use the free WP Engine Site Migration plugin, or ask WP Engine's specialists to handle the move. Download the plugin from the User Portal, install it on your old site, and connect it with the URL and secret key. Test the copy, then add your domain and point DNS at WP Engine.
Key takeaways
- The WP Engine Site Migration plugin is free, and you download it from the User Portal, not WordPress.org.
- A full migration copies all database tables and wp-content files, and updates domain names automatically.
- Small sites can take under an hour, while larger sites may take several hours.
- On the Advanced Network, SSL is installed automatically through Cloudflare.
- Add the domain in the User Portal before changing DNS, and verify it with a _wpe-verification TXT record.
- WP Engine does not host email; use a third-party host with an SMTP plugin.
What is the fastest way to migrate a WordPress site to WP Engine?
The fastest way is the free WP Engine Site Migration plugin, since it copies the site in the background while your old site stays live.
WP Engine offers two routes: the plugin for a self-service move, or an expert-led migration by its specialists, including the final switch, as its migration page explains. The expert route suits large, custom, or high-traffic sites, where specialists oversee the process and validate the site in a staging environment.
Small sites can take under an hour, while larger sites may take several hours. DNS propagation can take 24 to 72 hours globally, though the site stays reachable during that time, according to the same page.
A manual move with SFTP and phpMyAdmin is also possible if the plugin cannot be used. WP Engine's own guide points to a manual migration guide for that case.
| Route | Cost | Best for |
|---|---|---|
| Site Migration plugin | Free | Most sites, quickest route |
| WP Engine specialists | Qualifying plans | Large, custom, high-traffic sites |
| Manual SFTP and database | Free | Full control over the move |
What do you need before you start?
You need a WP Engine account, a plan with room for the site, and access to your current site.
Make a full backup of the old site and keep a copy on your own computer before you start. Learn WordPress gives the same advice in its migration lesson, and a backup is your way back if the move stalls.
Set up the destination environment in the User Portal first. The plugin needs a WP Engine environment to copy the site into, so create the site before you start the move.
Gather your current host login details and your domain registrar login. You will need the registrar login to change DNS later, and the plugin needs admin access to the old site.
If you have not picked a plan yet, see how much WP Engine costs first.
How do you migrate yourself with the WP Engine Site Migration plugin?
Download the plugin from the User Portal, install it on your old site, and connect it with the URL and secret key.
- In the WP Engine User Portal, open the Sites page and click your new destination environment.
- In the left-hand menu, select Site migration under the Manage section, then open the Automated Migration tab.
- Scroll down and click Install plugin. A green check mark appears with the message “Your WP Engine site is ready for migration!”, and Connection info is generated.
- Leave that window open, since the Connection info holds a URL and a secret key you will enter on the old site.
- Click Download Site Migration plugin in the User Portal to save the plugin ZIP file.
- On the old site, go to Plugins, then Add New Plugin, click Upload Plugin, choose the ZIP file, click Install Now, then Activate Plugin.
- On the old site's dashboard, open the Site Migration page in the sidebar and click START A NEW MIGRATION.
- Paste the Connection info and click CONNECT. For your first run, choose MIGRATE THE FULL WORDPRESS SITE.
- Enter an email address for status notifications, then click START MIGRATION.
A full migration copies all database tables and files in the wp-content folder, apart from disallowed plugins and files such as logs, backups, and caches. It also updates every instance of the domain name in the database automatically, as WP Engine's migration guide explains.
Get the plugin from the User Portal, not from WordPress.org. The old plugin listing on WordPress.org was closed on 3 May 2024, and the closure is permanent.
You can pick CUSTOMIZE THE MIGRATION instead of the full site option to include or exclude specific files and folders before the move starts.
How do you ask WP Engine's specialists to migrate your site?
Choose a plan, then ask WP Engine's migration specialists to handle the move, including the final switch.
The specialists oversee the process, validate your site in a staging environment, manage the DNS transitions, and help protect SEO. That specialist help suits large, custom, or high-traffic sites, according to WP Engine's migration page.
Expert-assisted migrations are offered for qualifying plans, though WP Engine does not list the qualifying plans on that page. Ask support whether your plan qualifies before you plan around the service.
The team validates the site in a staging environment before it goes live. That check is the same one you should do yourself after a plugin migration.
Support is available by chat on all plans and by phone 24/7 on all plans except the entry-level Startup plan. The average response time is under 3 minutes, as WP Engine's migration guide states.
How do you test the migrated site before going live?
Test the copy on WP Engine and confirm everything loads as expected before you go live.
In most cases, a migration causes no downtime, since the move happens in the background while your old site stays live. The risk is avoided by testing the migrated site before switching DNS, as WP Engine's migration page explains.
- Click through your main pages and check that images load.
- Submit a contact form and confirm it sends.
- Log in to wp-admin on the copy and open the dashboard.
- Check menus, widgets, and any custom post types.
Each site can have up to three environments: Production, Staging, and Development. Production shows by default, and you can view the others with the down arrow below the site name, according to WP Engine's Sites page guide.
Use the staging environment to test the copy without touching the live site. WP Engine describes its staging as one-click, so you can spin up a copy to test changes and push it live after.
See whether WP Engine includes backups to confirm what protection the copy has after the move.
How do you point your domain to WP Engine?
Add the domain in the User Portal first, then point DNS at your registrar, using the values WP Engine shows you.
Adding a domain in the User Portal should be done before you change DNS records, so traffic can be routed to the right environment. A new domain must be added in the User Portal to route the domain to the intended site, as WP Engine's domain guide explains.
- From the Sites page, select the environment name.
- Choose Domains from the secondary left-hand menu.
- Click Add Domain on the right and enter your domain name.
- Choose whether to also add the common variant, such as www or non-www.
- Set the domain as Primary if it is the main domain, then click Add domain.
Domain ownership must be verified when pointing DNS to WP Engine. Add a TXT record named _wpe-verification with the value copied from the User Portal, or use the automatic Entri Connect option.
Get the exact DNS values from the Domains tab. Open the three-dot menu next to the domain, select View DNS details, and update your records at your registrar to match. Delete any old A records or CNAME records, as WP Engine's migration guide advises.
For the Advanced Network, the CNAME value is wp.wpenginepowered.com, the same for every environment. The alternative is two A records: 141.193.213.10 and 141.193.213.11. CNAME flattening is preferred, according to WP Engine's Advanced Network guide.
Environments created after May 2023 already use the Advanced Network. Older ones must switch first, from Domains, then the three-dot menu, then Switch Network. Pointing DNS alone will not enable it and can take the site offline.
DNS propagation can take 24 to 72 hours globally. Our guide to how long DNS propagation takes explains the wait in more detail.
What happens to SSL and email after the move?
On the Advanced Network or Global Edge Security, SSL is installed automatically through Cloudflare, so no extra SSL is needed.
Check the SSL column on the Domains page for a green check next to the domain. Most domains sit on the Advanced Network or Global Edge Security, so the certificate is already handled, as WP Engine's SSL guide explains.
The Legacy Network is the exception. There, add a free Let's Encrypt certificate from Sites, then the environment, then SSL, then Add certificate, then Get Let's Encrypt. DNS must be pointed to WP Engine first to avoid errors.
A Let's Encrypt certificate typically installs within a few minutes, though it can take up to 24 hours. It expires after 90 days, and WP Engine tries to renew it 22 days before expiry.
WP Engine provides free single-domain certificates only. A wildcard, EV, or multi-domain certificate needs a purchased third-party SSL, and the Lite and Startup plans cannot import third-party certificates.
Email is a separate matter, since WP Engine does not provide MX or DKIM records for email hosting. Use a third-party email host with an SMTP plugin, such as WP Mail SMTP or Post SMTP, as WP Engine's email guide advises.
Port 25 is blocked on WP Engine servers. Use port 2525, or ports 587 and 465, and note that Microsoft 365 can only use port 587.
What mistakes should you avoid?
The most common mistakes are changing DNS too early and downloading the plugin from the wrong place.
- Changing DNS before the migrated copy is tested.
- Downloading the migration plugin from WordPress.org, where it is closed.
- Adding the domain at the registrar before adding it in the User Portal.
- Leaving old A or CNAME records in place after the switch.
- Skipping the _wpe-verification TXT record for domain ownership.
- Assuming WP Engine hosts your email.
Keep the old host active until the new site has served traffic for a day or two. Our guide to changing hosting without losing SEO covers the wider checklist for a safe switch.
If the plugin fails, check the Connection info first, since a wrong URL or secret key is the usual cause. The migration status email will tell you whether the run finished or failed.
Frequently asked questions
Is WP Engine migration free?
Yes. The WP Engine Site Migration plugin is free, and you download it from the User Portal. WP Engine also offers expert-assisted migrations for qualifying plans, where specialists oversee the process, validate the site in staging, and manage the DNS transition.
How long does a WP Engine migration take?
Small sites can take under an hour, while larger sites may take several hours. DNS propagation can take 24 to 72 hours globally, though the site stays reachable during that time. Test the copy before you switch DNS, since that is what avoids downtime.
Can I download the WP Engine migration plugin from WordPress.org?
No. The old plugin listing on WordPress.org was closed on 3 May 2024, and the closure is permanent. Download the plugin from the WP Engine User Portal instead, using the Download Site Migration button on the Site migration page for your destination environment.
How do I get SSL after migrating to WP Engine?
On the Advanced Network or Global Edge Security, SSL is installed automatically through Cloudflare, and no extra SSL is needed. Check the Domains page for a green check in the SSL column. On the Legacy Network only, add a free Let's Encrypt certificate from the SSL page.
Does WP Engine host my email?
No. WP Engine does not provide MX or DKIM records for email hosting. Use a third-party email host with an SMTP plugin, such as WP Mail SMTP or Post SMTP. Port 25 is blocked, so use port 2525, or ports 587 and 465, and note that Microsoft 365 can only use port 587.
Do I add my domain in WP Engine before or after changing DNS?
Add the domain in the User Portal before you change DNS, so traffic can be routed to the right environment. Then verify ownership with the _wpe-verification TXT record, and update your DNS records at your registrar with the values shown under View DNS details for the domain.
Sources
- Migrate WordPress to WP Engine WP Engine
- How to Migrate from Kinsta to WP Engine WP Engine
- Add a Domain in the User Portal WP Engine
- SSL Certificates WP Engine
- How to Send Email on WP Engine WP Engine
- wp-site-migrate Plugin WordPress.org
- Migrating Your Site Part 1: Changing to a New Host and Domain Learn WordPress
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
