WordPress to Astro, or keep WordPress headless.
Moving WordPress to Astro pays off when updates, plugins and page-builder markup cost more upkeep than they return. We check both paths: a full migration, or headless WordPress with Astro as the front end.
Two paths to choose from
Move off WordPress entirely, or keep it as the editorial back end. That decision comes first.
Static by default
Astro ships prerendered HTML. Client-side JavaScript arrives only where you request it.
Measured before and after
We record your Core Web Vitals before and after the move, using your own field data.
Our own products, live in the browser.
Screenshots from Mini Marvin, our own progressive web app running in the browser.
Swipe baby names instead of scrolling
Mini Marvin is our progressive web app for finding baby names: swipe through 10,000+ first names right in the browser, no app store needed.
WordPress to Astro in four points.
The short answer
- The move adds up when your site publishes content at heart while its plugin and update surface has to be maintained like an application.
Path A, full migration
- Content is exported, the content model rebuilt in Astro, WordPress switched off.
- After that there is no back end left to maintain.
Path B, headless WordPress
- Your editors keep the familiar admin and Astro becomes the front end.
- Details under WordPress as a headless CMS.
When we advise against it
- A live WooCommerce shop, deep plugin logic inside the business model, or an editorial team working in the block editor every day.
Is the move worth it in your case?
Send us the URL, an approximate page count and your plugin list. You get an assessment of which path fits.
Full migration or headless WordPress?
Astro is CMS-agnostic and works as the presentation layer. Path B is an equal option.
| Dimension | Path A: full migration | Path B: headless WordPress |
|---|---|---|
| Where the content ends up | In content collections in the repository, validated by a Zod schema. | Still in the WordPress database, fetched via REST API or WPGraphQL. |
| What editors work in | Content files, a connected CMS or the chat route. | The familiar WordPress admin with block editor, media library and roles. |
| WordPress operation afterwards | Gone, along with the database, PHP and the publicly reachable admin. | Stays in place and has to be maintained and secured. |
| What happens to plugins | Every plugin function is replaced or dropped, line by line. | Editorial plugins stay; anything producing front-end output goes inert. |
| Fits when | Editors publish rarely and WordPress mostly generates maintenance work. | A team publishes daily and depends on its workflows. |
How a migration from WordPress to Astro runs.
Five phases, each with a result you can check.
Take stock
Every indexed URL, the page types, the full plugin inventory and the traffic distribution.
Decide path A or B
Who publishes, how often, with which approval stages, and how much the block editor matters.
Content model and export
Posts, pages, categories, authors, media and custom post types get mapped over.
Define the replacements
Forms, newsletter, search, consent and gated areas each get a successor.
Launch and follow-up
Redirects live, sitemap submitted, indexing and field data watched for several weeks.
Frequently asked questions about moving from WordPress to Astro.
Will we lose our rankings when we move from WordPress to Astro?
Not when the move is planned. We pull every indexed URL beforehand, build a complete 301 list from it and test each redirect before go-live. Afterwards we watch indexing and positions for several weeks. To check the estate first, start with an SEO audit.
What happens to our plugins?
Plugin functions get replaced or dropped. Caching and image plugins fall away because Astro ships static HTML and image optimisation is built in. Membership, booking and shop plugins are applications: they stay in WordPress or get rebuilt as custom software.
We run a WooCommerce shop. Can we still move?
Usually we advise against it. Catalogue, cart, checkout, tax and shipping rules and payment providers all interlock, which makes it a shop project with its own risk profile. One middle route is moving only the marketing part. We cover that in e-commerce process consulting.
How long does a WordPress to Astro migration take?
Path A: 3 to 5 weeks for a tidy site up to roughly 30 pages, 6 to 10 weeks in the usual case, from 12 with a page builder and several languages. Path B usually sits at 4 to 8 weeks, followed by 8 to 12 weeks of monitoring.
What does a WordPress to Astro migration cost?
The range comes from the number of distinct page types, the volume of plugin functions to replace and the state of the content. After taking stock you get an estimate with its assumptions, see Astro development cost.
Can our editors still publish on their own afterwards?
Yes. On path A they maintain content in the repository, through a headless CMS or by chat. We work AI-assisted and run a WhatsApp AI agent. On path B almost nothing changes for them.
More from the Astro cluster.
Fundamentals, editing and operation after the move:
WordPress to Astro: assess first, decide second.
Describe your starting point briefly: URL, page count, plugin list, who publishes. You get an assessment of path, effort and cost range.
Request a WordPress migration.
URL, approximate page count, plugin list and who maintains the content: four details are enough for a first assessment.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.
Related reading.
WordPress as a Headless CMS
Path B in detail: editors stay in WordPress, Astro takes over the front end.
Learn moreAstro vs WordPress
Where each system leads, and when the two combine.
Learn moreAstro Development Cost
What makes up the price of an Astro project and what drives the range.
Learn moreAstro Performance Optimization
Measure Core Web Vitals, set budgets, verify again after launch.
Learn moreAstro Migration
Every migration path at a glance: WordPress, Webflow, Framer and Next.js.
Learn moreIT Project Management
When the move is part of a larger programme and someone has to hold the threads.
Learn more