By Mehdi HassanShould you migrate Webflow to Astro or Next.js?
Migrate Webflow to Astro when the site is mostly content and you want the lightest possible pages; migrate to Next.js when the site has app-like features or shares code with a React product. Both produce fast, crawlable HTML. The difference is what each is designed around: Astro around content, Next.js around applications.
We build production sites in Next.js, and our fixed-price packages are Next.js builds, so weigh that when reading our view. Astro is still the right answer for some sites, and this guide says when. For the broader move off Webflow, our Webflow to Next.js migration guide covers the steps both frameworks share, and Webflow vs Next.js helps if you're unsure about leaving at all.
What makes Astro a good fit for content sites?
Astro is a good fit for content sites because it renders pages to static HTML and sends no JavaScript to the browser unless a component needs it. Interactive pieces, such as a pricing toggle or a search box, become islands that load on their own, while the rest of the page stays plain HTML.
- Content collections. Markdown and MDX files with a typed schema, so every post has the fields it needs and build errors catch missing ones.
- Bring your own components. Islands can be written in React, Vue, Svelte or plain Astro components.
- Static or server output. Build everything at deploy time, or add a server adapter for pages that need to be dynamic.
- Any headless CMS. Pull content from Sanity, Payload, Contentful or others at build time instead of files.
The research we draw on includes a public example of scale: zenml.io moved 2,224 pages to Astro, using AI coding agents for much of the rebuild. Large content sites are exactly where Astro's static-first model pays off.
Astro vs Next.js: how do they compare after Webflow?
Astro wins for pure content and simplicity, and Next.js wins for interactivity, product integration and a larger ecosystem. Here's how they compare for a team leaving Webflow.
Factor | Astro | Next.js |
|---|---|---|
Default JavaScript sent | None unless you add islands | React runtime on every page |
Best for | Blogs, docs, resource libraries | Marketing sites with product features |
Content in the repo | Content collections, Markdown, MDX | Possible, but less built in |
Headless CMS support | Good, mostly at build time | Excellent, including live preview flows |
Auth and app features | Possible with adapters, less common | First-class |
Visual editing for marketers | Depends on CMS, more setup | Mature with Sanity and Payload |
Hiring and ecosystem | Smaller | Very large |
The editing row decides many projects. If marketers publish weekly and expect click-to-edit preview, Next.js with Sanity or Payload is the more mature path today. If the writers are comfortable with Markdown or a simple CMS form, Astro is hard to beat.
What does a Webflow to Astro migration involve?
A Webflow to Astro migration involves rebuilding the design as Astro components, moving CMS content into collections or a headless CMS, recreating forms and other platform features, and keeping every URL working. Nothing transfers automatically, because Webflow has no Astro export.
Webflow's code export can help as a reference for markup and styles, but it isn't a starting codebase; we explain why in exporting Webflow code. CMS content comes out as CSV or through the Webflow API. Two details catch teams out: rich text arrives as HTML that has to be converted to Markdown or your CMS's format, and every image URL points to Webflow's CDN, so images must be downloaded and re-hosted before you close the Webflow site.
What does a sample Webflow to Astro migration plan look like?
A sample plan runs in seven phases. Duration depends on page count and how much content lives in the CMS, so treat it as an order of work, not a schedule.
Benchmark
Record organic traffic, top pages, indexed URLs, Core Web Vitals and backlinks. See our guide to benchmarking before a migration.
Inventory URLs
Crawl the site and list every URL, including CMS items, with its target URL on the new site.
Choose where content lives
Markdown collections for developer-written content, a headless CMS for anything marketing edits.
Build layouts and components
Rebuild templates in Astro, adding islands only for parts that need JavaScript.
Migrate content
Script the export, convert rich text, re-host images and validate every entry against the collection schema.
Replace platform features
Forms to your CRM, site search, analytics and any localization routing.
Redirect, test and launch
Add redirects for changed URLs, check meta and sitemaps, then switch DNS and watch Search Console.
Hypothetical example: a resource-heavy content site
For example, suppose a developer-tools company has a Webflow site with 20 marketing pages and around 600 articles, guides and glossary entries in the CMS. Writers are engineers who already work in Git.
Astro fits well: articles move into MDX content collections, code samples render at build time with syntax highlighting, and the only islands are search and a newsletter form. Marketing pages, edited by the one marketer, pull from a small headless CMS. If the same company also wanted a logged-in dashboard on the marketing domain, we'd lean back toward Next.js.
How do you protect SEO in a Webflow to Astro move?
Protect SEO by keeping URLs identical wherever possible, redirecting the rest one to one, and carrying over titles, descriptions, canonicals and structured data. Astro's file-based routing makes matching Webflow paths straightforward, including collection paths such as /blog/post-slug.
- Generate a sitemap with Astro's sitemap integration and submit it in Search Console on launch day.
- Set redirects at the host, such as Cloudflare or Vercel, or in Astro's redirects config.
- Keep hreflang and locale URLs intact on multilingual sites; see migration SEO for multilingual sites.
- Preserve internal links and your topic structure, so pillar pages still link to their clusters, as covered in topic clusters and pillar pages.
If the content plan includes thousands of templated pages, compare approaches in programmatic SEO with Next.js too. Both frameworks handle large static builds, and the choice comes down to how those pages are edited and updated.
Which should you choose after Webflow?
Choose by what the site does and who edits it. Content-first sites edited by technical writers suit Astro; marketing sites run by non-technical teams, or sites tied to a product, suit Next.js.
