The site itself moves easily. What catches people out is the configuration that was never in WordPress — redirect rules, the platform mu-plugins, and whatever the disallowed-plugin list had quietly substituted.
A backup captures WordPress. It does not capture the settings that only ever existed in your account panel.
Redirects configured in the WP Engine interface are not stored in WordPress, so a database export leaves every one of them behind. We read them out and rebuild them at our edge before DNS moves.
Certain caching, backup and security plugins cannot run there, so sites often arrive missing functionality the platform had silently substituted. We identify what was replaced and put back an equivalent that runs here.
Platform mu-plugins load on every request and expect services that will not exist after the move. They come out during the copy rather than being left to throw errors on the live site.
Asset URLs pointing at their CDN domain end up saved in post content. Those are rewritten to your own domain so nothing keeps loading from an account you have closed.
Most accounts have a staging and a legacy environment alongside production. We check whether either is still referenced before anything gets switched off.
We do the work. You approve a preview on a temporary domain, and DNS only changes once you have looked at it and said so.
Most of what changes is configuration rather than raw capacity, which is why we benchmark your actual site rather than quoting you a generic number.
These are the specific things a WP Engine site needs attention on, as distinct from a general WordPress migration.
| Setting | What we do | Why |
|---|---|---|
| Platform mu-plugins | Removed during the copy rather than after cutover | They call services that stop existing the moment DNS moves, and the resulting errors surface on the live site rather than on staging. |
| Portal redirect rules | Exported and rebuilt as edge rules before DNS changes | Redirects configured outside WordPress are invisible to a database export, so they disappear silently at cutover and take their traffic with them. |
| Disallowed-plugin substitutions | Audited and replaced with equivalents that run here | A site told it could not use its caching or backup plugin has been running on a substitute, and nobody wrote down what that substitute was covering. |
| CDN asset URLs | Rewritten to your own domain across post content | Hard-coded CDN hostnames keep pointing at an account you are about to close. |
| Object cache | Redis enabled and warmed before the switch | Arriving with a cold cache makes the first hour after cutover the slowest the site has ever been, and that is the hour everybody is watching it. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, portal redirect rules ported, and a staged preview to approve before DNS changes.