Flywheel vs WP Engine: Same Company, Different Fit

Bramble + Oak is a 4-person creative studio in Vancouver — 2 designers, 1 part-time dev, 1 owner/PM. They do branding + web for small-luxury hospitality and restaurant clients across BC and Alberta. At the time I worked with them (spring 2025), they ran 9 client WordPress sites — all Tailwind-styled, Gutenberg-heavy, small traffic (avg 4K monthly sessions), but each one bespoke and beautiful. Agency revenue CAD $18,000/mo, hosting was a line item, not a retainer driver. The decision was between Flywheel Freelance ($115/mo, 10 sites, Blueprints included) and WP Engine Professional ($58/mo, 5 sites, bulk management). On spreadsheet math WP Engine was 2x cheaper per-site. But two workflow factors flipped it. Factor one: Blueprints. The studio had developed a Gutenberg-block-based 'house style' starter site — custom blocks for menu cards, gallery grids, reservation embeds. Blueprints let them clone this starter as a new site in 90 seconds. On WP Engine, kickoff took 2-3 hours of manual clone-import-reconfigure. Across 9 client kickoffs a year, Blueprints was saving ~20 hours of senior designer time annually. At CAD $110/hr effective rate, that's $2,200/yr — more than the Flywheel-vs-WP-Engine annual delta of ~$684. Factor two: client hand-off UX. Flywheel's Growth Suite let them present each client with their own dashboard (Flywheel-branded, not their studio's — that's the only wart) where the client paid Flywheel directly for their site's hosting. Studio billed separately for design retainer. Clean separation, no 'I'll ask about the hosting invoice' awkwardness. WP Engine's agency dashboard requires the studio to hold the bill and rebill — more admin overhead. Outcome: chose Flywheel. Twelve months later they grew to 11 sites, paid the small overage, and stayed put. Honest caveat: if they'd been a dev-led shop doing 30+ sites, WP Engine Growth or Scale would have won on dev tooling + price per site. Flywheel is genuinely a fit for the designer-led 5-15 site studio — a narrower niche than either host advertises.

Since WP Engine acquired Flywheel in 2019, the two have shared infrastructure back-end but separate product UIs. Moving between them is genuinely different from a cross-host migration — it's an internal transfer handled by their shared migration team. Day -7: open a support ticket with whichever host you're leaving and request 'platform transfer to [Flywheel/WP Engine].' They'll typically ask about site sizes, current plan, and destination plan. No free migration plugin needed — they handle it server-side. Expect 3-5 business days lead time because the migration team is shared and often backlogged. Lower DNS TTL to 300s at the registrar as usual. Day 0 (transfer day): both hosts clone your site's files + DB to the destination platform. Because they share the same AWS backend, this is faster than a true migration — typically 1-4 hours per site depending on size. You get a destination-side URL (*.flywheelsites.com or *.wpengine.com) to test on. Gotchas to verify: caching configuration doesn't carry over (Flywheel's FlyCache and WP Engine's EverCache use different cache-purge rules), admin users do transfer cleanly, but any custom cron jobs don't — document and recreate. SSL: both auto-provision post-DNS flip. Day 0 DNS cutover: flip A records at the registrar. TTL of 300s means propagation in 10-30 minutes. SSL issuance 5-15 minutes after DNS resolves. Critical post-flip step: if you were on Flywheel with Fastly CDN and move to WP Engine default Global Edge Network, cache rules don't migrate — pages may serve stale content for up to 24 hours until the new CDN's cache populates. Purge cache explicitly on day 0. Reverse direction (WPE → Flywheel) has the same gotcha. For a multi-site move: I typically batch in waves of 3-5 sites over a week. Day 0 move the most-trafficked sites first (they get the most verification attention), day 3 move middle-tier, day 5 move the long tail. This lets you catch platform-level issues before they affect every site at once. What typically breaks: (1) Flywheel has Blueprints — those don't transfer to WP Engine. Any 'template site' you relied on for kickoff has to be recreated as a manual starter in WP Engine. (2) WP Engine's environment model is 3 (Dev/Staging/Prod) vs Flywheel's 2 (Staging/Prod) — moving WPE → Flywheel collapses your Dev environment; document what was in it first. (3) Growth Suite client-billing arrangements on Flywheel don't exist on WP Engine's side; you'd have to re-engineer billing flow. This last one is usually what stops agencies from leaving Flywheel.

WP Engine acquired Flywheel in June 2019 for an undisclosed sum widely reported in the $100M+ range. The first 2-3 years post-acquisition Flywheel maintained product independence — separate UI, separate roadmap, separate support team. From 2022 onward the consolidation pressure became visible to agencies running both. Infrastructure consolidation: Flywheel was originally on Google Cloud, WP Engine on AWS. By 2023 Flywheel migrated most of its workloads to WP Engine's AWS infrastructure. Customers didn't see the underlying change, but it explains why Flywheel's formal uptime SLA language got softer in 2023-2024 (it's now a shared-fate with WP Engine's AWS, which is 99.95% on Growth+ plans). Product roadmap divergence: WP Engine poured engineering resources into Atlas (headless WordPress, launched 2020, major updates 2023-2025), Smart Search (2024), and AI copilot features in 2025. Flywheel's visible roadmap since 2022 has been maintenance-mode: Blueprints improvements, Growth Suite tweaks, no major new primitives. This is the signal agencies debating Flywheel should watch. No official end-of-life has been announced, and Flywheel has enough paying agency customers that sunsetting it would cost WPE significant churn — but the feature velocity gap is real. Genesis + StudioPress bundled with WP Engine plans (2018 acquisition) is included free; Flywheel customers don't get it bundled. For designer agencies that standardized on Genesis child themes, this alone is often why they stayed on WP Engine when deciding. PHP 8.3 became min for WordPress 6.8 in early 2026; both hosts shipped 8.4 in 2025. Both ban caching plugins (use their own EverCache/FlyCache) and most backup plugins. Plugin blocklist is nearly identical between the two — shared ops team standardized it in 2023. For Canadian agencies: both bill in USD, neither has a Canadian data centre (both use US-East + US-West + EU-Central), and both invoice from US entities. Latency from Ontario/Quebec to US-East-1 (Virginia) is typically 20-40ms — acceptable for most WP workloads. BC-based agencies should pick US-West-2 (Oregon) as the origin, which both hosts offer. Neither host is the right pick if you have Canadian privacy-law clients demanding CA-resident data — for that, Kinsta's Toronto GCP region is the cleanest option in this price tier.