Migrate to Astro: content moves, the front end is rebuilt.
When you migrate to Astro, content, URLs and search signals move across while the presentation layer is built new. We migrate from WordPress, Webflow, Framer and Next.js, with a redirect map and measurement.
Front end rebuilt
Content, URLs and search signals move across. Layout, components and navigation are built new.
One-to-one redirect map
Every old URL gets one target, including pagination, archives and campaign URLs with query strings.
Measured before and after
We record Core Web Vitals and visibility as a baseline, then again the same way.
An Astro website in production.
Built by us, maintained by the client.
Client project · website
HappyLipo
Content platform on lipedema: knowledge articles, nutrition, care and downloads. Built by us, first in Webflow. On Astro with Sanity as the editing system since September 2026, maintained by the client.
Migrating to Astro in four points.
What moves
- Content, URLs and metadata.
- Layout, components and navigation are built new.
The path depends on the source
- WordPress and Next.js have official migration guides.
- For Webflow and Framer the path starts with an export.
What carries the rankings across
- A complete redirect map
- Unchanged titles and descriptions
- Canonicals and hreflang
- Sitemap and IndexNow submission
- Then Search Console monitoring after launch
When we advise against it
- When your site is fast enough and your team is happy with it.
- If your marketing builds the pages itself, stay on Webflow.
Five paths to Astro, and what follows.
The process is similar everywhere. The source decides the effort.
WordPress to Astro
The most common case. Content comes out via API or export, and an official migration guide exists.
DetailsWebflow to Astro
No official guide. The path runs through a CMS export and a front-end rebuild.
DetailsFramer to Astro
Usually smaller sites with high design ambition. Content from the collections, layout rebuilt.
DetailsNext.js to Astro
Technically the smoothest path: same language, same component thinking, official migration guide.
DetailsWordPress as headless CMS
The back end stays, only delivery changes. Your editors keep working in wp-admin.
DetailsEdit your website by chat
What becomes possible after the migration: change text or add a post as a chat message.
DetailsIs the move worth it for you?
Send us the URL and two sentences about what slows you down. You get an assessment of effort, risk and benefit.
How a migration to Astro runs.
The first two steps decide how the rest goes.
Content inventory
Every URL from sitemap, server logs, analytics and Search Console. Outcome: keep, merge, retire.
URL map and redirect plan
Every indexed URL gets exactly one target, including pagination, archives and feed addresses.
Consolidate templates
Grown one-off pages become a handful of page types with typed fields in a Zod schema.
Rebuild the front end
Layout, components and image pipeline are built new. Interactive parts become single islands.
Launch and follow-up
Preview environment, page-by-page check against the redirect map, then eight to twelve weeks of monitoring.
Frequently asked questions about migrating to Astro.
Will we lose our Google rankings when we migrate to Astro?
Not when the migration is planned. We build a complete redirect map and carry titles, descriptions, canonicals and hreflang across unchanged. Beforehand we mark the paragraphs that carry positions, and after the switch we watch Search Console for several weeks.
How long does a migration to Astro take?
From inventory sign-off to switching day: 3 to 5 weeks for a focused marketing site, 6 to 10 for a company site with a blog and CMS, from 12 for multilingual sites or system integrations. A headless move sits at 4 to 8 weeks.
What does a migration to Astro cost?
Template consolidation, the volume and state of your content, the integrations and the size of the redirect plan set the range. The front-end rebuild is the expensive part, the content move rarely is. See Astro development cost.
Is there a tool that automatically converts WordPress to Astro?
No. There are exporters to Markdown, and Astro publishes official migration guides, among them WordPress and Next.js. Those cover content and project structure. The presentation layer gets rebuilt in every case.
Can we keep our CMS and still move to Astro?
Yes. Astro is CMS-agnostic and stays the presentation layer. With WordPress that path is headless operation, or the content moves into a headless CMS or into the repository as content collections. For logged-in applications we recommend custom software.
Can we run the migration ourselves with AI?
For a prototype and the content export, yes. The demanding parts stay: redirect map, content model, retirement list and the monitoring afterwards. We work AI-assisted ourselves, for example with our WhatsApp AI agent, and put every change through review and build.
Read on in the Astro cluster.
The individual migration paths, plus comparisons, cost and fundamentals:
We assess before we quote.
Describe your starting point in three sentences: platform, page count and what slows you down. You get an assessment, usually within 24 hours.
Request a migration to Astro.
Briefly describe what your site runs on today and what bothers you. We come back with a first assessment.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.
Related services.
Webflow Agency
When your team prefers building pages visually. We work in Webflow as much as in Astro.
Learn moreSEO Audit
Measure before you decide. Sometimes the problem sits in the structure and the content.
Learn moreIT Project Management
When someone has to hold deadlines, interfaces and approvals of a larger programme together.
Learn more