I migrated my 47th WordPress site off WordPress last week. The decision rule that's never failed me: if you spend more time fighting WordPress than building features, leave.

That sounds reductive, I know. But after years of building on WordPress — and years of pulling projects off it — I've distilled the "should I stay or should I go" question into something more structured. A five-question framework that gives you an honest, quantifiable answer. No vibes. No tribal loyalty to PHP or React. Just a checklist that maps to real pain points.

Let me walk you through it, then we'll talk about where to go, what it costs, and the mistakes that'll wreck your migration if you're not careful.

Table of Contents

The 5-Question Framework: Should You Leave WordPress?

I've used this framework with clients, with my own projects, and with dev teams evaluating their stack. Five yes-or-no questions. Each one targets a specific category of WordPress pain — plugin bloat, cost, security, performance, and velocity.

1. Do You Have More Than 20 Active Plugins?

Twenty is the number. Not because there's something magical about it, but because that's the threshold where WordPress stops being a CMS and starts being a Frankenstein monster held together by add_filter hooks and prayer.

Every plugin is a dependency you don't control. Every plugin update is a potential breaking change. And in 2026, the WordPress plugin ecosystem has a security problem that's hard to ignore: Patchstack reported over 11,300 plugin CVEs in 2025 alone, a 42% increase over the prior year. More plugins means more attack surface.

Go count your active plugins right now. I'll wait.

If you're at 30+, you're almost certainly running plugins that duplicate functionality, conflict with each other, or exist only because WordPress doesn't natively do something that modern frameworks handle out of the box — things like image optimization, caching, SEO meta tags, or form handling.

2. Are You Paying More Than $100/Month for Managed Hosting?

WordPress is "free" software that somehow costs a fortune to host well. If you're on WP Engine, Kinsta, or Flywheel, you're likely paying $30-$115/month for a single site. Scale that to 5-10 sites and you're looking at $300-$600/month.

Meanwhile, a statically generated site on Vercel or Netlify? Free tier handles most marketing sites. Even a headless CMS + Next.js setup on Vercel Pro is $20/month. That's not an apples-to-apples comparison (WordPress includes a database, admin UI, etc.), but that's the point — you're paying for infrastructure you might not need.

If your hosting bill makes you wince, that's a signal.

3. Have You Been Hacked or Had Downtime in the Last 12 Months?

This is a binary question and it matters more than most developers admit. WordPress powers ~40% of the web, which makes it the single biggest target for automated attacks. Brute force login attempts, SQL injection through outdated plugins, malware injected via nulled themes — I've seen all of it.

If you've been hacked, you know the drill: Sucuri scan, database cleanup, password rotations, client panic. If you've had downtime because a plugin update borked your site at 2 AM, you know that feeling too.

Modern static sites and server-rendered apps with no public admin panel simply don't have this attack surface. There's no /wp-admin to brute force. There's no xmlrpc.php to exploit. The security model is fundamentally different.

4. Are Your Core Web Vitals Failing on Mobile?

Google's Core Web Vitals are table stakes for SEO in 2026. And WordPress sites consistently struggle here. A 2025 HTTP Archive analysis showed that roughly 71% of WordPress origins failed the mobile CWV assessment — compared to significantly better pass rates for sites built on frameworks like Next.js and Astro.

The culprit? Render-blocking CSS from themes and plugins. Unoptimized images served without modern formats. Excessive DOM size from page builders. JavaScript that wasn't needed in the first place. You can throw caching plugins at the problem, but you're treating symptoms, not causes.

Run your site through PageSpeed Insights. If your mobile LCP is above 2.5 seconds and your CLS is failing, WordPress itself might be the bottleneck.

5. Does Your Team Want to Ship Features Faster Than WP Allows?

This is the question that matters most to engineering teams. WordPress's development model — PHP templates, the loop, hooks and filters, the Gutenberg block API — is a specific way of building. It's not bad. But it's slow compared to component-based development with React, Vue, or Svelte.

If your team spends more time:

  • Wrestling with the Block Editor's React-but-not-really architecture
  • Writing custom PHP to work around theme limitations
  • Debugging plugin conflicts after updates
  • Waiting for full-page cache invalidation

...than actually building features your users want, that's your answer.

Modern frameworks let you ship faster. That's not opinion — it's physics. Component-based architectures with hot module reloading, TypeScript, and API-driven content beat the WordPress development loop on iteration speed every time.

Scoring Your Answers

Here's the decision matrix. Simple on purpose:

Yes Answers Recommendation Rationale
0-1 Stay on WordPress Your problems are manageable. Optimize what you have.
2 Stay, but plan Start prototyping alternatives. You're approaching the tipping point.
3 Start migrating The pain is real and it's not going away. Begin planning your exit.
4-5 Leave now WordPress is actively costing you time, money, and security. Prioritize migration.

I've applied this to probably 60+ projects at this point. It's never given me a false positive. The clients who scored 3+ and stayed on WordPress? They came back 6-12 months later, and the migration was harder and more expensive by then.

What to Migrate To (Mapped to Use Case)

This is where most "leave WordPress" articles fall apart. They'll tell you to use Next.js for everything, or they'll list 15 CMS options without telling you which one fits your situation. Let me be specific.

Marketing Sites and Blogs

Recommended stack: Astro + a headless CMS (Sanity, Storyblok, or Contentful)

Astro was basically designed to replace WordPress for content sites. It ships zero JavaScript by default, generates static HTML, and supports partial hydration for interactive components. Your lighthouse scores will go from "disappointing" to "perfect" overnight.

We build a lot of these at Social Animal — our Astro development capabilities are heavily oriented toward exactly this migration path. Pair Astro with Sanity Studio and your content editors get a better authoring experience than WordPress ever gave them.

E-commerce

Recommended stack: Next.js + Shopify (headless) or Medusa.js

If you're running WooCommerce, you already know the pain. WooCommerce is powerful but brittle under load, slow without serious caching infrastructure, and expensive to customize. Shopify's Storefront API with a Next.js frontend gives you cart functionality, checkout, and inventory management without running your own database.

For teams that want full control and self-hosting, Medusa.js has matured significantly in 2026 and is worth evaluating.

Web Applications (Dashboards, Portals, SaaS)

Recommended stack: Next.js (App Router) + headless CMS for content sections + your own API

If you've been hacking WordPress into an application with custom post types, ACF, and REST API endpoints... stop. WordPress was never meant to be an application framework. Next.js with server components, server actions, and middleware gives you a real application architecture.

Content-Heavy Editorial Sites

Recommended stack: Next.js or Astro + Sanity or Strapi

Editorial teams need structured content modeling, draft previews, and collaborative editing. This is where a headless CMS shines. Sanity's real-time collaboration is years ahead of WordPress's Gutenberg editor. Strapi gives you a self-hosted option with a clean admin panel.

Use Case Recommended Frontend Recommended CMS Hosting Estimated Monthly Cost
Marketing site / blog Astro Sanity or Contentful Vercel / Netlify $0-$20
E-commerce Next.js Shopify Storefront API Vercel $29-$79 (Shopify) + $20 (Vercel)
Web application Next.js Sanity (for content) Vercel / AWS $20-$100
Editorial / publishing Next.js or Astro Sanity or Strapi Vercel $0-$99

Compare that to your current WordPress hosting bill. For most teams, the infrastructure costs drop by 30-60%.

Migration Timeline and Cost (Real Numbers)

I'm going to give you the numbers nobody wants to publish because they're afraid of scaring clients. These are based on real migrations we've done and observed in 2025-2026.

Small Site (Under 50 Pages, Simple Blog)

  • Timeline: 3-5 weeks
  • Cost: $5,000-$12,000 (agency) / 40-80 hours (in-house)
  • Key tasks: Content export and restructuring, template rebuilds in Astro/Next.js, CMS setup, redirect mapping, DNS cutover
  • Hardest part: Extracting content from page builder shortcodes. If your content is littered with [vc_row] or Elementor JSON blobs, budget extra time for content cleanup.

Medium Site (50-200 Pages, Multiple Content Types)

  • Timeline: 6-10 weeks
  • Cost: $15,000-$35,000 (agency) / 120-250 hours (in-house)
  • Key tasks: Everything above, plus content modeling in the headless CMS, custom component development, form migrations, third-party integration rewiring (analytics, email marketing, CRM)
  • Hardest part: Rebuilding custom ACF field groups and relationships in a new content model. This is where most timeline estimates blow up.

Large Site (200+ Pages, E-commerce, Custom Functionality)

  • Timeline: 12-20 weeks
  • Cost: $40,000-$80,000+ (agency) / 400-800+ hours (in-house)
  • Key tasks: Full content audit, phased migration strategy, data migration scripts, e-commerce platform migration, user account migration, SEO preservation (redirects, sitemap, structured data)
  • Hardest part: Not breaking SEO. Large sites have accumulated years of backlinks, indexed pages, and search authority. One botched redirect map can tank your organic traffic for months.

These numbers might seem high, but compare them to the total cost of ownership of staying on WordPress for another 3 years: managed hosting ($100-$300/mo × 36 = $3,600-$10,800), premium plugin licenses ($500-$2,000/year × 3 = $1,500-$6,000), security incident response ($2,000-$10,000 per incident), and developer time spent on maintenance instead of features.

If you want to talk specifics for your project, our pricing page lays out how we approach this, and you can always reach out directly.

The 3 Mistakes That Kill WordPress Migrations

I've seen these kill migrations dead. Not "cause delays" — kill them. As in, the team gives up and goes back to WordPress, having wasted months and tens of thousands of dollars.

Mistake 1: Migrating Content Without Restructuring It

The biggest mistake is treating migration as a copy-paste job. You export your WordPress posts and pages, import them into a new CMS, and rebuild the same templates. This gives you the same messy content architecture in a shinier box.

The whole point of migrating is to restructure. WordPress encourages a flat content model: posts, pages, and custom post types with ACF fields bolted on. A headless CMS lets you define proper content models with typed fields, references, and validation.

Spend the time to audit your content before you write a single line of code. What content types do you actually need? What fields matter? What pages can be consolidated or deleted? I've seen 200-page WordPress sites reduced to 60 pages of well-structured content during migration — with zero loss of value.

Mistake 2: Ignoring the Redirect Map

WordPress URLs follow a specific pattern (/2024/03/post-title/, /category/uncategorized/, etc.). Your new site will have different URL patterns. Every old URL needs to redirect to its new equivalent, or you lose the SEO value those pages have built up.

This is tedious, unglamorous work. It's also the single most important technical task in the entire migration. Use a crawling tool like Screaming Frog to export every indexed URL, map each one to its new destination, and implement 301 redirects.

// next.config.js — example redirect mapping
const nextConfig = {
  async redirects() {
    return [
      {
        source: '/2024/03/old-post-slug/',
        destination: '/blog/new-post-slug',
        permanent: true,
      },
      {
        source: '/category/:slug',
        destination: '/topics/:slug',
        permanent: true,
      },
      // ... potentially hundreds of these
    ];
  },
};

For large sites, you'll want to generate these programmatically from your content export rather than mapping them by hand.

Mistake 3: Not Giving Editors a CMS Before Launch

Developers love migrations. Content editors hate them. You're taking away the tool they know (WordPress) and handing them something unfamiliar. If you don't involve your editors early — training them on the new CMS, getting their feedback on the content authoring workflow, making sure they can actually publish without developer help — they'll revolt.

I've seen a migration get cancelled two weeks before launch because the marketing team said "we can't work with this." The dev team had built a beautiful Astro site with Sanity Studio, but nobody had shown the editors how Sanity worked until the week of launch.

Bring your content team in during week 2, not week 10. Let them create test content in the new CMS. Listen to their complaints. Adjust the studio configuration. This is what makes or breaks adoption.

FAQ

How do I know it's time to leave WordPress?

Use the five-question framework above. If you answer "yes" to three or more of the questions — more than 20 plugins, hosting over $100/month, security incidents, failing Core Web Vitals, or your team can't ship fast enough — it's time. The framework isn't about hating WordPress. It's about honestly assessing whether the platform is helping you or holding you back. Two or fewer? WordPress is probably still fine for your needs, and you should focus on optimizing what you have.

What's the cheapest WordPress alternative?

Astro with a free-tier headless CMS (Sanity's free plan supports 3 users, Contentful's free plan supports 5 users) deployed on Netlify or Vercel's free tier. Total cost: $0/month. Seriously. For a marketing site or blog, this stack is production-ready and performs better than a $100/month managed WordPress setup. The catch is you need a developer comfortable with Astro and the CMS of choice — but if you're reading this article, that's probably you.

How long does it take to migrate off WordPress?

For a typical small site (under 50 pages), expect 3-5 weeks. Medium sites with 50-200 pages and multiple content types run 6-10 weeks. Large sites with e-commerce or complex custom functionality can take 12-20 weeks. The biggest variable isn't code — it's content. If your content is clean and well-structured, migration goes fast. If it's trapped in page builder shortcodes and deeply nested ACF field groups, budget extra time for extraction and restructuring.

Will I lose SEO if I migrate from WordPress?

You can, but you won't if you do it right. The critical step is implementing a complete 301 redirect map from every old URL to its new equivalent. You also need to preserve your meta titles, descriptions, and structured data (schema markup). Crawl your existing site with Screaming Frog before migration, export all indexed URLs, and verify every redirect works after launch. Most well-executed migrations see a temporary 2-4 week fluctuation in rankings, followed by improvement thanks to better Core Web Vitals.

Can I use WordPress as a headless CMS instead of fully migrating?

Yes, and this is a valid intermediate step. WordPress's REST API (or WPGraphQL) lets you use WordPress as a content backend while building a modern frontend in Next.js or Astro. This approach lets your editors keep using the WordPress admin they know while your dev team builds a faster frontend. The downsides: you still maintain a WordPress installation (with all its security and update overhead), and the REST API can be slow without caching. I'd recommend this as a stepping stone, not a destination.

What happens to my WordPress plugins when I migrate?

They go away — and that's the point. Most plugins exist to fill gaps in WordPress (SEO, caching, forms, image optimization, security). In a modern stack, these are handled by the framework or build tools. Next.js has built-in image optimization. Astro ships zero JS by default. Contact forms can use services like Formspree or Resend. Analytics move to Plausible or Vercel Analytics. You'll need to audit your plugin list and map each one to its replacement in the new stack.

Should I migrate all at once or in phases?

For sites under 100 pages, migrate all at once. The coordination overhead of running two systems simultaneously isn't worth it. For large sites (200+ pages), consider a phased approach: migrate the marketing pages and blog first, keep complex sections (e-commerce, user portals) on WordPress temporarily, and use reverse proxy rules to serve both from the same domain. This reduces risk but increases architectural complexity.

Do I need an agency to migrate off WordPress, or can I do it myself?

Depends on the site. A developer comfortable with Next.js or Astro can migrate a simple blog in a few weekends. But for sites with complex content models, e-commerce, custom functionality, or high SEO stakes, working with a team that's done this before saves real time and money. We've done dozens of these migrations — the patterns are predictable, and the pitfalls are well-known. Check out our capabilities or get in touch if you want to talk through your specific situation.