On many WP Engine sites, some of the most important settings are not in WordPress at all. Redirect rules, access rules, response headers, and cache exclusions are set in WP Engine's User Portal, and a copy of the WordPress files and database leaves every one of them behind. Most migration surprises from WP Engine start here, so this checklist does too.
Export these from the User Portal first
| In the User Portal | Why it matters |
|---|---|
| Redirect rules | Old links and campaign URLs depend on them; WP Engine allows around a thousand per site, so busy sites often have hundreds |
| Web Rules Engine: IP allow and deny rules, headers, rewrites | WP Engine does not support .htaccess, so rules that elsewhere live in that file are here |
| Cache settings and exclusions | Pages that must never be cached, such as carts, members' areas, or forms with tokens |
| Domains and SSL | Every domain and redirecting domain that must keep working |
| CDN and edge security settings | Firewall and bot settings that protect the site today |
| SFTP and SSH users | Who has access, so it can be granted again deliberately, not copied blindly |
A screenshot or export of each page is enough. eWay recreates the rules on the new platform, in the web server, CDN, or WordPress as fits each one.
Media that is not in the backup
If your site uses WP Engine's LargeFS to keep media in Amazon S3, those files are not included in WP Engine backup points. They have to be copied from S3 separately, and a migration that only restores the backup will be missing images and documents. Check the User Portal for LargeFS, or ask eWay to check during the inventory.
Who does what
| Your organization | eWay |
|---|---|
| Add eWay as a user on the WP Engine account | Inventory the site, plugins, and User Portal settings |
| Confirm the WP Engine contract end date | Build the AWS environments from infrastructure as code |
| Name a person who can approve DNS changes | Remove WP Engine-specific plugins and settings |
| Make the decisions below | Copy files and database, recreate rules, rehearse the cutover |
| Test on the temporary address and sign off | Run the cutover, verify, and monitor |
Things that change for your team
- Staging. WP Engine's copy-to-staging buttons are replaced by eWay's environments and deployment workflow; see Dev, Test, and Live environments.
- Plugin updates. If you used WP Engine's automatic plugin updates, eWay takes over updating and testing plugins.
- Backups. WP Engine backup points stay on WP Engine. Download a final full backup before the account closes and keep it.
- Disallowed plugins. Plugins WP Engine blocked may be allowed again, but should still be reviewed before you turn them back on.
Decisions only you can make
- The cutover window, away from campaigns, events, or deadlines.
- The content freeze, a few hours without publishing during the final copy, and who tells editors.
- What to leave behind: inactive plugins, unused themes, and old staging copies.
- Who signs off that the new site is ready.
Your test checklist
- Your top pages, plus a sample of old URLs from the redirect list
- Every form, including that its email arrives; see contact form emails not arriving
- Sign-in, editing, publishing, and media uploads
- Logged-in or personalized areas, which depend on the cache exclusions
- Integrations such as payments, CRM, or newsletter sign-ups
Common surprises
- Links in content that still point to the WP Engine temporary domain, which stop working when the account closes
- Form emails that relied on the old host's mail handling; test each form after the move
- Integrations that allow-list WP Engine's addresses
Cutover day
eWay lowers DNS caching times in advance, freezes content, runs the final copy, and switches DNS. The WP Engine site is left unchanged until you accept the new one, so switching DNS back is the rollback. Keep the WP Engine plan active until you have signed off and downloaded a final backup.
How eWay runs WP Engine migrations
A single WordPress site typically takes six to ten weeks from start to cutover. eWay builds the environment on a temporary domain, recreates every User Portal rule, rehearses the DNS and certificate cutover, and plans for no unplanned downtime. Every changed URL gets a managed redirect, and 404s are monitored after launch.
What to include in a support ticket
- The WP Engine install names and live domains
- Screenshots or exports of the User Portal pages above
- Your contract end date and dates to avoid
eWay customers can open a ticket in the support portal or email support@ewaycorp.com. Related reading: keeping redirects and search rankings when you move and managing DNS.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article