Moving off a legacy WordPress theme: rebuild, go headless, or migrate
Your WordPress site has outgrown its theme. Here are the three honest options, what each costs, and how to migrate without losing rankings.
mrkd teamOctober 12, 2026
Most WordPress sites don't fail all at once. They get heavier. A page builder here, a plugin there, a theme from 2019 that nobody wants to update. One day every change takes a developer, and the site takes four seconds to load on a phone.
At that point there are three honest options. None is always right.
Option one: rebuild on WordPress
Keep WordPress. Replace the theme.
A modern WordPress build uses the block editor with a library of custom blocks that match your design system. Styles are locked, editors fill in fields, and the plugin list shrinks to a handful you actually trust. Posts, pages, media, and URLs stay exactly where they are.
Choose this when: your team knows the WordPress admin, you rely on plugins for things like forms, events, or memberships, and the problem is the theme rather than the platform.
What it costs: the least of the three. No content migration, no retraining, and a much lighter site at the end.
Option two: go headless
Keep WordPress as the content backend. Replace the frontend with Next.js.
Content still lives in WordPress, and editors still use the admin they know. A separate frontend fetches content over the REST API or GraphQL and renders the site — fast, modern, and free of theme constraints.
Choose this when: performance or a custom frontend matters more than the plugin ecosystem, or the same content needs to feed an app or multiple sites.
What it costs: more than a rebuild. Many plugins that change the frontend no longer apply, so forms, previews, and SEO tooling need deliberate replacements. You also run two systems instead of one.
Option three: leave WordPress
Move content to a different CMS — usually Storyblok or Builder.io.
Choose this when: the editing experience is the problem. If editors struggle to build pages, need a true visual editor, or you're running several languages and markets, a component-based CMS fits better than retrofitting WordPress.
What it costs: the most. Content has to be modeled, migrated by script, and checked. Editors have a new tool to learn. In exchange you get a cleaner content model and an editor built for composing pages.
How to migrate without losing rankings
Whichever option you choose, the risk everyone worries about is the same: the traffic cliff after launch. It's avoidable.
- Inventory every URL before you start, including the ones you forgot existed. Analytics and Search Console show what actually gets traffic.
- Preserve URLs where you can. The best redirect is no redirect.
- Map every redirect that you can't avoid, one-to-one, and test them before launch, not after.
- Carry metadata across: titles, descriptions, canonical tags, structured data, and image alt text.
- Migrate by script, not by hand. Scripts are repeatable, so you can re-run the import to catch content published during the project.
- Monitor after cut-over: crawl errors, rankings for the pages that matter, and Core Web Vitals.
How we'd decide
Start with who's frustrated. If developers are frustrated, the theme is probably the problem — rebuild on WordPress. If performance or architecture is the problem, go headless. If editors are frustrated, look at a different CMS.
We compare the platforms, and how we migrate between them, on our websites page. Or send us a short brief and we'll tell you which option we'd pick.
Keep reading
All posts- ReadGuide3 min read
What is a composable website? A guide for SaaS marketing teams
Composable is the buzzword on every agency site. What it means in practice, what it costs, and the three signs your SaaS marketing site is ready for it.
- ReadGuide5 min read
Storyblok vs WordPress vs Builder.io: choosing a CMS for your marketing site
The framework we use with SaaS teams to choose between Storyblok, WordPress, and Builder.io — with a comparison table across the four criteria that matter.
- ReadGuide6 min read
Connecting your business systems without replacing them
Your CRM, billing, product, and support tools don't talk to each other. You don't need to rip any of them out. Integration patterns, sync strategies, and when to use iPaaS versus a custom build.
Let's build something
Need a partner like us?
Tell us about your project. We respond within one business day.