NEWAI-native design subscriptions are back
Book a call

Webflow to Astro migration

Webflow to Astro, code you own

For teams that want the site in a repository: faster pages, no seat fees, and a codebase AI agents can edit safely.

Plan your migrationWhat moves, what doesn’t
Typical timeline
Scoped after the URL inventory
Cost
Quoted after the URL inventory
SEO risk
Low to medium: Astro can match every Webflow path
Moves cleanly
CMS collections (CSV or API), copy, images
Must be rebuilt
Pages and components, interactions, forms, site search

In short

Checked against Webflow and Astro docs

A Webflow to Astro migration exports the CMS to CSV and rebuilds the site as Astro components. Webflow’s code export gives static HTML and CSS but leaves CMS lists empty and forms without a backend, so we use it as a reference, not a starting point. Collections become typed content in Astro, pages are rebuilt from a token-based design system, and redirects move to the host as real 301s.

Why teams move

Why teams move from Webflow to Astro

  1. Own the site outright

    No site plan, no Workspace seats, no lock-in to one host. The site is files in a repository you control.

  2. Agents and developers edit it

    A typed codebase with a design system is something coding agents can change through reviewed pull requests, with full history.

  3. Programmatic pages

    Comparisons, integrations, locations and docs generated from data files are simpler in code than as hand-kept CMS collections.

Old vs new

Webflow vs Astro, for this move

WebflowAstro
Who owns itWebflowHosted by Webflow, site plan and seatsAstroA repository you own, hosted anywhere
EditingWebflowVisual Designer and EditorAstroCode and Markdown, or a headless CMS
Page weightWebflowWebflow runtime and interactionsAstroHTML first, JavaScript only where needed
AI agentsWebflowWebflow’s MCP server and AI toolsAstroAny coding agent through pull requests
RedirectsWebflowSite settingsAstroHost redirect file, each line marked 301

Last updated

Astro vs Webflow: the full comparison

What moves, what doesn’t

What comes across from Webflow

  • Content

    Collections export to CSV or through the Data API, rich text as HTML. We convert them to Markdown or typed data files.

  • CMS

    Webflow collections become Astro content collections with a schema checked at build time, or a headless CMS if editors need a UI.

  • SEO

    Titles, descriptions and OG tags become frontmatter; sitemap and structured data are generated. Webflow’s 301s are exported as CSV and moved to the host.

  • Forms

    Webflow form handling doesn’t come with the code, so forms move to a form service, your CRM or a serverless function.

  • Integrations

    Site search, memberships and ecommerce need a decision each; analytics and embeds are added back and loaded lazily.

  • Animations

    Webflow interactions are rebuilt in CSS or a small motion library and only shipped where used.

  • Media

    Exported image URLs point at Webflow’s hosting, so every file is downloaded and served from the new host before Webflow is cancelled.

Moves over
Exported, imported, then checked by hand
Partly
Some of it imports, the rest is redone
Rebuilt
Nothing to import, we rebuild it
Replaced
Swapped for the new platform’s equivalent

Content model

How Webflow content maps to Astro

  1. CMS collection

    Webflow collections with typed fields, references between them and a template page per item.

    On Webflow

    Content collection

    A folder of Markdown or data files with a schema, so a missing or wrong field stops the build.

    On Astro

    What you get src/content/blog/*.md

    Fields become typed frontmatter; references become slugs checked at build time.

  2. Collection template page

    The one page design Webflow fills in for every item, served under the collection’s own path.

    On Webflow

    A dynamic Astro route

    One route file that builds a static page for every entry in the collection when the site builds.

    On Astro

    What you get src/pages/blog/[slug].astro

  3. Static pages and components

    Pages built in the Designer from classes, components and variables, and hosted by Webflow.

    On Webflow

    Pages and components

    .astro pages and components that all read one set of design tokens for colour, type and spacing.

    On Astro

    What you get src/styles/tokens.css

  4. 301 redirects

    Redirect rules saved in Webflow’s site settings, served by Webflow’s hosting and exported as CSV.

    On Webflow

    A host redirect file

    A plain text file deployed with the site, one rule per line with the 301 status written out.

    On Astro

    What you get public/_redirects

Process and timeline

How we move a Webflow site to Astro

  1. Inventory and export

    Before any code

    List every URL, export collections and redirects to CSV, download assets, and keep a code export as a visual reference.

  2. Content model

    Before any code

    Write the collection schemas and route map so every Webflow path has a home.

  3. Design system and pages

    Build

    Tokens and components first, then pages, matched against the live site.

  4. Content conversion

    Build

    Convert CSV to Markdown or data files and validate every item against the schema.

  5. SEO parity and redirects

    Before launch

    Per-page SEO checked; 301s written into the host’s redirect file; forms and search tested.

  6. Switch and watch

    Launch and after

    Move the domain early in the week, submit the sitemap and watch 404s and indexing daily.

SEO safety

The pre-launch checklist for Webflow to Astro

Rankings are lost in three ways: broken URLs, missing on-page signals and crawl problems. 4 stages, from the first crawl to the weeks after launch, close all three. Tick the checks as you go; your progress stays in this browser.

Stage 1 of 4

Before the build

Know every URL and where it goes before anything is designed.

Stage 2 of 4

During the build

Carry every on-page signal across, page by page.

Stage 3 of 4

Before launch

Real redirects and a clean path for crawlers, ready for the switch.

Stage 4 of 4

After launch

Watch what Google sees in the first weeks and fix it fast.

Free migration planner

Plan your Webflow to Astro redirects

Enter your site to list every URL, see which keep their path on Astro and get the 301 redirect map.

What people worry about

What Webflow teams worry about

  1. Our marketers can’t edit code

    They don’t need to. Content can live in a headless CMS with a visual editor, while layouts stay in code.

  2. Can’t we just use Webflow’s code export?

    It leaves CMS lists empty, drops form handling and site search, and covers one locale. It’s a useful reference for the rebuild, not a site to run.

  3. Will images break when Webflow is cancelled?

    Every asset is downloaded and re-served from the new host, and the built site is searched for Webflow URLs before launch.

When not to migrate

When to stay on Webflow

  • Marketers build new page layouts themselves every week in the Designer.

  • Nobody on the team works in code or with coding agents, and you don’t want a headless CMS.

  • You rely on Webflow Ecommerce, memberships or localization.

Not sure which side you’re on?

If one of these is you, staying on Webflow is probably the better call. We’ll say so on the first call.

Book a call

FAQ

Webflow to Astro questions

Adrian

Moving from Webflow to Astro?

Every URL mapped, the CMS rebuilt, SEO kept. We scope it on a 30-minute call.

Plan your migration
Can we start from Webflow’s code export?

Only as a reference. The export (on paid Workspace plans) has the HTML, CSS and interactions, but CMS collection lists show their empty state, forms need a new endpoint and only the primary locale is included.

What about Webflow DevLink?

DevLink exports Webflow components to React, which can run inside Astro. It doesn’t cover CMS collection lists or page-level interactions, so it helps with some components, not the whole site.

Who edits content after the move?

Developers and coding agents in Markdown and data files, or marketers in a headless CMS. We agree this before the build.

How do redirects work?

We export Webflow’s 301s as CSV and write them into the host’s redirect file, so they stay real server-side 301s.

Keep exploring

All migrations

Platform facts checked on . Platforms change their exports and limits; we recheck at the start of every project.

You've reached the end, so now…

Tell us what you’re building.

We’ll help you map the right scope, team, timeline, and next steps.

Book a call