Leaving WP Engine — How to Migrate Without Losing Rankings or Traffic

Last Verified: May 2026  |  Author: FBWH Editorial Team

Migration steps verified against WP Engine, Kinsta, Rocket.net, and Cloudways official documentation. Pricing sourced directly from each host's pricing page — May 2026.

WP Engine customers who decide to leave tend to stay longer than they should — not because the host is irreplaceable, but because migration feels risky. A site with established rankings, real traffic, and a business depending on it is not something you move carelessly. The fear of a rankings drop after migration is legitimate. It has happened to people who moved without a plan.

This guide is the plan. It covers what actually breaks when you leave WP Engine, how to protect your SEO through the migration, and where to go depending on what your site needs. Done correctly, a WP Engine migration is a half-day project with zero ranking impact.

Who this guide is for: WP Engine customers who have decided to leave or are seriously evaluating it. If you are still deciding whether to stay, the reasons people leave are covered in section 2 — read that first. If you have already decided Kinsta is the destination, see our step-by-step WP Engine to Kinsta playbook which covers the wizard, LargeFS, and the WooCommerce cutover sequence specifically.

Why People Leave WP Engine

WP Engine built its reputation on being the premium managed WordPress host for agencies and serious WordPress sites. That reputation is earned — the infrastructure is solid, the support is knowledgeable, and the tooling (staging, white-label portals) is genuinely useful for agencies. But there are specific, recurring reasons customers decide to leave.

Visit overage charges

WP Engine's plans are metered by monthly visits — not bandwidth, not storage, but visits. The Startup plan covers 25,000 monthly visits. The Growth plan covers 100,000. When you exceed your visit limit, WP Engine charges overage fees — $2 per 1,000 extra visits. A site that has a viral month, a successful campaign, or seasonal traffic spikes can face overage charges that are larger than the base plan cost. This is the single most common complaint from departing WP Engine customers.

Plugin restrictions

WP Engine maintains a list of prohibited plugins — plugins they will not allow on their platform due to security, performance, or compatibility concerns. The list includes some commonly used plugins. If your site depends on a plugin that WP Engine prohibits, you either find an alternative or you find a different host. This is a hard constraint with no workaround.

Price versus value at current tier

WP Engine's Startup plan at $25/month (annual) covers one site and 25,000 monthly visits. Rocket.net at $30/month covers one site with 250,000 visits and Cloudflare Enterprise included. Kinsta's Single 35k plan at $35/month covers one site with no visit overage panic — overages are billed at $0.50/1,000 versus WP Engine's $2/1,000, a quarter of the cost. For sites that have outgrown WP Engine's entry tier or are paying overage charges regularly, the price-versus-value calculation has shifted.

Ownership uncertainty

WP Engine's ownership history is worth one factual paragraph. The company has gone through significant private equity involvement — Silver Lake acquired a majority stake in 2018, and subsequent corporate changes have raised questions among some customers about long-term product direction. This is not a reason to leave in isolation, but for agencies with long client commitments, ownership stability is a legitimate evaluation factor.

What Actually Breaks When You Leave WP Engine

WP Engine has a specific infrastructure and workflow that creates predictable migration issues. These are the breakpoints to plan for — not generic WordPress migration problems, but WP Engine-specific ones.

EverCache and caching configuration

WP Engine uses their proprietary EverCache system — a server-level caching layer that handles page caching without a WordPress plugin. When you move to a new host, EverCache is gone. Your new host's caching system needs to be configured and verified. If you were relying on EverCache to cache pages that should not be cached — WooCommerce cart pages, for example — that exclusion logic needs to be recreated at the new host.

LargeFS media files left behind

If you use WP Engine's LargeFS feature to offload older media to Amazon S3, the migration team at your new host cannot see or access those files — they live in your S3 bucket, not on WP Engine's server. Migration tools copy what's on the server; LargeFS files are not. After migration, older media will return 404 errors unless you handle the S3 content separately, either by syncing it back via AWS CLI before migration or by continuing to use S3 with a plugin like WP Offload Media on the new host. If you're moving to Kinsta specifically, our WP Engine to Kinsta playbook covers the LargeFS workflow in detail.

WP Engine-specific plugins stop working

WP Engine installs several of their own plugins or mu-plugins on every site — WP Engine System, Force HTTPS, and others. These are designed to work with WP Engine's infrastructure and are non-functional on any other host. They will not cause errors on a new host, but they serve no purpose and should be deactivated and deleted after migration. Smart Plugin Manager (a paid add-on on Essential plans, included on Core) also stops working — your automated plugin update workflow needs a replacement.

Staging environment disappears

WP Engine's staging environment is one of their strongest features. When you leave, you lose it immediately. Your new host needs to have staging capability from day one — confirm this before migrating, not after. Kinsta, Rocket.net, and Cloudways all include staging on standard plans.

Two-factor authentication blocks migration access

If you have 2FA enabled on your WP Engine User Portal, your new host's migration team cannot log in with username and password — they'll hit a 2FA challenge they can't answer. The clean solution is to invite the migration team's email as a user in your WP Engine account before submitting the migration request, bypassing 2FA entirely. This is the single most common cause of migration delays per migrations team feedback across hosts.

Email configuration

If you are using WP Engine's outgoing email or relying on their SMTP configuration for WordPress transactional email, this stops working after migration. Configure WP Mail SMTP with a transactional email provider (Elastic Email, SendGrid, or Mailgun) before cutting DNS over. Test form submissions and WooCommerce order emails specifically.

SSL certificate

WP Engine provides SSL certificates through Let's Encrypt or their own certificate management. These do not transfer — WP Engine doesn't grant access to the cert files. Your new host provides their own SSL — Kinsta, Rocket.net, and Cloudways all include free SSL. For single-site migrations this is automatic. For agencies moving 20+ sites in batches to the same data center, Let's Encrypt rate limits apply (10 certs per hour per registered domain) and bulk cutovers need to be staggered.

Local development environment: If your team uses WP Engine's Local (formerly Local by Flywheel) for local WordPress development, the good news is Local works with any host — no replacement needed. Just point new local copies at the new host's SFTP credentials. If you're moving to Kinsta, DevKinsta is the Kinsta-native equivalent that integrates with the MyKinsta dashboard.

Pre-Migration Checklist

Do not touch DNS until every item on this list is complete. The checklist is not optional — it is the difference between a clean migration and a recovery operation.

• Full backup: Export a complete backup from WP Engine's dashboard — files and database. Download it locally. Do not rely on WP Engine's backup system after your account closes.
• Document your DNS records: Screenshot or export every DNS record — A, CNAME, MX, TXT (SPF, DKIM, DMARC). Your email configuration, domain verification records, and any third-party service integrations live here.
• Check LargeFS status: If LargeFS is active on your account, plan the S3 handoff before migrating (sync to local then re-upload, or continue serving from S3 on the new host).
• Invite the migration team as a WP Engine user: Bypasses 2FA blocker. For Kinsta, add migrations@kinsta.com. For Rocket.net and Cloudways, check their current migration support email.
• Identify prohibited plugins: Check WP Engine's prohibited plugin list against your installed plugins. If you are using any, find replacements and test them on staging before migrating.
• Document custom PHP settings: WP Engine allows PHP version selection and some custom PHP configuration. Note your current PHP version and any custom settings — you will need to replicate them on the new host.
• List all cron jobs: Check WP Engine's dashboard for any scheduled tasks or custom cron configurations. These need to be recreated at the new host.
• Lower DNS TTL: 48 hours before migration, lower your domain's DNS TTL to 300 seconds. This means DNS changes propagate in 5 minutes rather than 24–48 hours — your rollback window is minutes if something goes wrong.
• Set up email independently: Configure WP Mail SMTP with a transactional provider before the migration. Test it on the new host's staging environment before cutting over.

Quick Answer: The pre-migration checklist takes 2–3 hours. The migration itself takes 2–4 hours for a standard WordPress site. Budget a full day, do it on a weekday when you can monitor traffic and rankings in real time, and do not start on a Friday.

Where to Go — Kinsta vs Rocket.net vs Cloudways

WP Engine customers are not first-time site owners — they are people who chose managed WordPress hosting deliberately and understand what they are paying for. The right destination depends on why you are leaving and what your site needs.

Kinsta — best for agencies and high-volume WooCommerce

Kinsta is the most direct WP Engine replacement in terms of managed WordPress positioning. High-performance cloud infrastructure, isolated containers, staging on all plans, and a support team with genuine WordPress expertise. The visit-based plans (Single 35k, Single 65k, etc.) work like WP Engine's metered tiers but with overages at $0.50/1,000 instead of $2/1,000 — a quarter of the cost. There's also a bandwidth-based pricing track (Single 20GB, Single 40GB) for sites where bandwidth is a better fit. No prohibited plugin list.

For agencies migrating multiple client sites from WP Engine, Kinsta's Agency plan ($284/mo annual) includes unbranded WordPress admin and an agency directory. DevKinsta is Kinsta's local development tool. The transition workflow is the most like-for-like of the three options.

Honest caveats: Redis is a $100/mo per-site add-on at Kinsta, not bundled — for WooCommerce sites needing real object caching this is real spend. Premium Staging at $20/mo gives staging that matches live site resources. PHP resources are now a configurable pool per site via MyKinsta → Tools → PHP settings, adjustable without contacting support.

Decided on Kinsta? See our step-by-step WP Engine to Kinsta playbook covering the migration wizard, LargeFS handoff, 2FA workaround, and WooCommerce cutover sequence.

Rocket.net — best for speed-focused WordPress and WooCommerce

Rocket.net is the better choice if raw performance and global delivery are the priority. Cloudflare Enterprise on every plan, Redis free on all plans, Argo Smart Routing included, no prohibited plugin list, and flat pricing with no renewal jump. The $1 first month makes the initial cost low — the ongoing Starter rate of $30/month covers one site and 250,000 visits, far more than WP Engine's Startup plan at $25/month for only 25,000 visits.

ShopShield — Rocket.net's flash sale traffic management system — is a specific advantage for WooCommerce stores that run promotional events. WP Engine has no equivalent. If your store does regular sales or has experienced traffic spikes that caused checkout issues on WP Engine, this is a meaningful differentiator.

What Rocket.net does not have: WP Engine's white-label agency portals or a multi-tenant dashboard built for agency workflows. For solo site owners and WooCommerce operators, this is irrelevant. For agencies managing client sites with client-facing dashboards, Kinsta is a better fit.

Cloudways — best for developers and cost-conscious teams

Cloudways is the right choice if you want managed cloud infrastructure at a price point below Kinsta and Rocket.net, and you have the technical comfort to configure it. DigitalOcean, Vultr, Linode, AWS, or Google Cloud backend — your choice of provider and region. Entry price starts at $11/mo (DO Standard) or $14/mo (DO Premium NVMe). Object Cache Pro is free on 4GB+ servers (normally $95/mo). No visit metering, no prohibited plugins, flat monthly pricing.

For a developer-managed site or a team with a technical operator, Cloudways provides more flexibility than WP Engine at lower cost. The tradeoff is operational: Cloudways support is infrastructure-only — WordPress application-layer issues are out of scope. For non-technical site owners who valued WP Engine's fully managed approach, this requires more involvement than is comfortable.

The Migration — Step by Step

With the pre-migration checklist complete and your new host provisioned, the migration itself follows a clear sequence.

Step 1 — Use the team-handled migration first

Kinsta and Rocket.net both offer free unlimited migrations handled by their engineering teams — contact support and they handle the file and database transfer. Kinsta uses a 6-step wizard inside MyKinsta with WP Engine specifically listed as a supported source. Cloudways provides a WordPress Migrator plugin you run yourself. For most WP Engine sites under 2GB, the team-handled migration handles everything correctly. Use this path first.

Step 2 — Verify on staging URL before touching DNS

Every host provides a temporary staging URL — a subdomain where your migrated site is accessible before you change DNS. Spend time here. Check every page type: homepage, blog posts, product pages, cart, checkout, contact forms. Log in as a WooCommerce customer and complete a test order if applicable. Check that images load (this is your LargeFS check — older media especially), that custom fonts render, that JavaScript-dependent features work.

Specifically verify: WP Engine system plugins are deactivated and deleted, caching is working correctly on the new host's system, PHP version matches what you documented, and email sends successfully from the test environment.

Step 3 — Configure caching on the new host

This step is where WP Engine migrations most commonly go wrong. EverCache is gone — your new host's caching needs to be set up explicitly.

• Kinsta: Server-level caching and Edge Caching are enabled by default on every new site. Confirm cache exclusions for WooCommerce pages (cart, checkout, account) in the MyKinsta dashboard under Caching settings.
• Rocket.net: Cloudflare Enterprise caching is automatic. WP Rocket plugin is recommended — its integration with Rocket.net's infrastructure is pre-configured. Verify WooCommerce page exclusions in WP Rocket settings.
• Cloudways: Enable Varnish in the Application settings. Install Breeze (Cloudways' free caching plugin) and configure WooCommerce exclusions manually.

Step 4 — DNS cutover

With staging verified and caching configured, change your DNS A record to point to the new host's IP address. With TTL at 300 seconds, propagation takes under 5 minutes for most visitors. Monitor your site in real time — load it from your browser with cache cleared, check from a mobile device, use a tool like whatsmydns.net to confirm propagation globally.

Keep your WP Engine account active for 48 hours after DNS cutover — your rollback path if anything critical fails. Do not close the WP Engine account until you have confirmed everything is working on the new host for at least 24 hours.

SEO Protection — What to Watch and When

The SEO risk in any migration is real but manageable. The risks come from three sources: URL structure changes, crawl errors after migration, and performance changes that affect Core Web Vitals scores. Done correctly, none of these should cause ranking drops.

URL structure — do not change it

The single most important SEO rule in any migration: keep every URL identical. Same permalink structure, same slug format, same category paths. If a URL changes, Google treats it as a new page — and the old page's ranking authority does not transfer automatically. If you need to change URLs for any reason, set up 301 redirects from every old URL to the new one. Every URL. No exceptions.

Post-migration GSC monitoring

On the day of DNS cutover, open Google Search Console and monitor:

• Coverage report: Watch for a spike in 404 errors in the 24–48 hours after migration. Any 404 means a URL that existed on WP Engine does not exist on the new host — fix immediately with a 301 redirect.
• Core Web Vitals report: Check LCP, FID, and CLS scores 48 hours after migration. If scores improve — expected when moving to Kinsta or Rocket.net from WP Engine — your rankings will benefit over 4–6 weeks. If scores worsen, investigate caching configuration first.
• Index coverage: Confirm your sitemap is submitted and pages are being indexed. Submit your sitemap URL in GSC if it is not already registered.

Rankings dip briefly — this is normal: A small, temporary rankings fluctuation of 1–3 positions in the first week after migration is common and not a cause for concern. Google re-crawls migrated sites and re-evaluates them. If your content, URL structure, and internal linking are unchanged, rankings typically recover or improve within 2–4 weeks as Google registers the performance improvement on the new host.

Redirect any WP Engine staging URLs

WP Engine staging environments use wpengine.com subdomains. If any of your staging URLs were accidentally indexed by Google — which sometimes happens with incorrectly configured robots.txt — set up redirects from those staging subdomains to your live domain. Check GSC's Coverage report for any indexed wpengine.com URLs after migration.

Bottom Line — Who Should Go Where

FAQ

Does WP Engine offer a free migration to competitors?

No — WP Engine's free migration service moves sites onto WP Engine, not off it. Kinsta, Rocket.net, and Cloudways all offer free migrations from WP Engine. Contact your new host's support team and they handle the transfer. Rocket.net and Kinsta both include unlimited free migrations on all plans.

Will my Google rankings drop after leaving WP Engine?

Not if you keep URLs identical, configure caching correctly on the new host, and monitor GSC in the 48 hours after cutover. A temporary 1–3 position fluctuation in the first week is normal and typically self-corrects. Sites moving to Kinsta or Rocket.net usually see Core Web Vitals improvements that produce ranking gains over 4–6 weeks.

What happens to my WP Engine staging environment?

It disappears when your account closes. Set up staging on your new host before closing your WP Engine account. Kinsta, Rocket.net, and Cloudways all include staging on standard plans. Kinsta's Premium Staging Environments ($20/mo add-on) match live site resources for accurate pre-production testing.

Can I keep my WordPress plugins when I leave WP Engine?

Yes — with one caveat. WP Engine system plugins (WP Engine System, Force HTTPS, Smart Plugin Manager) should be deactivated and deleted on the new host — they are non-functional outside WP Engine. All other plugins transfer normally. Check WP Engine's prohibited plugin list before migrating — if you were blocked from using a plugin on WP Engine, you can install it freely on any other host.

How long does a WP Engine migration take?

For a standard WordPress site under 2GB: 4–6 hours including pre-migration checklist, migration, staging verification, and DNS cutover. For large WooCommerce stores with extensive product databases: plan a full day. Always start in the morning on a weekday so you have monitoring time before end of business.

Is Kinsta better than WP Engine?

For most use cases, yes — comparable infrastructure, far lower visit overage rates ($0.50/1,000 vs $2/1,000), no prohibited plugin list, and dual pricing models (bandwidth or visits). The agency tooling comparison is closer — WP Engine's white-label portals are mature, while Kinsta's Agency plan ($284/mo annual) offers unbranded WP admin. For individual sites and WooCommerce stores, Kinsta is the stronger product at a comparable base price, though add-ons like Redis ($100/mo) can stack.

What about WP Engine's 60-day money-back guarantee?

WP Engine offers a 60-day money-back guarantee on new accounts. If you are within that window and unhappy, you can claim a refund without needing to provide detailed reasons. Outside the 60-day window, WP Engine does not offer prorated refunds on annual plans — factor the remaining contract value into your migration timing decision.

Related Reading

• WP Engine to Kinsta — The Step-by-Step Playbook
• GoDaddy to Cloudways — What Breaks and How to Fix It
• Kinsta Full Review 2026
• Rocket.net Full Review 2026
• Kinsta vs WP Engine — Full Comparison
• Best Hosting for WooCommerce Stores Processing 200+ Daily Orders

Image Credits & Data Sources

WP Engine plan pricing and visit limits: wpengine.com/plans — verified May 2026. WP Engine prohibited plugin list: wpengine.com/support/disallowed-plugins. Kinsta migration documentation: kinsta.com/docs/wordpress-hosting/wordpress-migrations/migrating-to-kinsta. Rocket.net migration documentation: rocket.net/support. Cloudways migration documentation: cloudways.com/blog/migrate-wordpress-to-cloudways. All data verified May 2026.