Webflow to Astro migration
A Webflow to Astro migration is a rebuild, not an export: Webflow's code export leaves Collection lists empty and leaves form processing, site search and localised content behind. We export every collection to CSV, rehost your assets, rebuild templates as Astro routes and keep item URLs identical so rankings carry over.
- Crawl and collection export
- Schema and import
- Astro build
- Redirect testing and launch
Trusted by B2B and premium service brands in 17+ countries.
Why teams move
Why teams move from Webflow to Astro
Content that has to be modelled freely
Webflow sets item and collection limits by plan, and its schema lives inside one site.Teams with large or shared content often want a headless CMS where they define the model and query it from any channel.
The code export is not an exit
Webflow exports HTML, CSS and JavaScript, but Collection lists come out empty and form processing, site search and localized content stay behind.Rebuilding in Astro is the only way to leave with a working CMS-driven site.
A front end the developers control
An Astro project sits in Git with pull requests, previews and automated checks, and sends JavaScript only for the parts that need it.For product teams, that keeps the marketing site inside their normal engineering process.
What moves
What carries over, and what needs work
Carries over
- CMS items, exported per collection to CSV with rich text as HTML
- Images and files, downloaded from their Webflow-hosted addresses before the old site is switched off
- Collection and item slugs, so /collection/item URLs can stay exactly as they are
- Per-page and per-template SEO titles and descriptions
- Your existing 301 rules, translated into the new host's redirect file
Needs work in Astro
Collection lists and templatesCollection lists, filters and template pages are Webflow features.
They are rebuilt as Astro routes and components that read from the new CMS at build time.
Webflow InteractionsExported interactions keep working only with Webflow's own script files.
We rebuild the motion that matters in CSS or small scripts, so the new site does not carry Webflow's runtime.
Forms and site searchWebflow processes form submissions and runs site search on its own hosting, and neither works outside it.
Forms get a new endpoint, and search is added only if visitors actually need it.
- Localized contentWebflow Localize content is not in the code export and each CSV export covers one locale, so every locale is exported, mapped and checked on its own.
Content model
How Webflow content maps to Astro
We map every field before anything moves, so content is not retyped by hand and nothing is dropped without a decision.
| In Webflow | In Astro | What we check |
|---|---|---|
| Name | title (string) | Becomes the H1 and default meta title source |
| Slug | slug | Copied exactly, never regenerated from the title |
| Rich text | Portable Text | HTML converted, embeds and custom code blocks reviewed by hand |
| Image, Multi-image | image, array of images | Files downloaded from the Webflow CDN, alt text kept |
| Reference, Multi-reference | reference, array of references | Imported in dependency order so references resolve |
| Option | string with a fixed list | Option values kept so existing filters map one to one |
| Switch | boolean | Used for featured and draft style flags |
| Date/Time | datetime | Time zones checked so dates do not shift by a day |
Redirects and SEO
Protecting rankings during the move
The redirect plan
Collection paths kept as they are
Webflow item pages follow /collection-url/item-slug. An Astro route such as src/pages/blog/[slug] reproduces that shape, so CMS item URLs can stay identical after the move.Existing rules translated, not copied
Webflow 301 rules can use (.*) captures with %1 references. Each rule is rewritten in the new host's syntax and tested one by one, because wildcard and ordering rules differ between hosts.No content left pointing at Webflow
Old pages and rich text link to images on Webflow's CDN. We rewrite those addresses during import so nothing on the new site still depends on the old project.
Risks we watch for
Publishing a raw export
A code export shows empty states where Collection lists should be.Published as is, it would replace real pages with thin ones, so exports are only ever used as a reference for markup.
Locale folders and hreflang
Webflow Localize serves locales from subdirectories such as /en-us and lists them with hreflang.The Astro build either keeps the same folders and hreflang, or redirects each locale URL deliberately.
Template-level metadata
In Webflow, CMS template SEO fields are bound to collection fields.The same bindings are rebuilt in Astro templates so every item keeps its own title and description.
Timeline and fit
How long it takes, and whether it suits you
It fits when
- The site needs a content model shared with an app or other channels
- Your developers want the marketing site in the same repository and pipeline
- You have outgrown your Webflow plan's CMS limits or want to stop planning around them
- Forms, search and integrations need custom handling anyway
We would advise against it when
- Your marketing team builds pages in the Designer every week and wants to keep doing so
- The site is small and Webflow's CMS covers it comfortably
- Nobody will maintain a codebase after launch
- You mainly want a visual refresh, which a redesign in Webflow would cover
How we run it
How we run a Webflow to Astro move
Step 01
Crawl and collection export
We crawl the Webflow site for its URL inventory and baseline, then export each collection to CSV and download every image and file before anything is switched off.
Step 02
Schema and import
We model the collections in the new CMS, rewrite asset links, convert rich text and import items in dependency order so references and slugs arrive intact.
Step 03
Astro build
We rebuild templates and collection pages as Astro routes, recreate the interactions that matter, and connect forms and any search to their new services.
Step 04
Redirect testing and launch
We translate and test every redirect rule, compare old and new pages, point the domain and monitor crawling, indexing and rankings after launch.
Common questions
Webflow to Astro: questions we get asked
Can we use Webflow's code export instead of rebuilding?
For most sites, no. The export leaves Collection lists empty and does not include form processing, site search, password protection or localized content, so a CMS-driven site does not work from it.
What happens to our images in Webflow?
They are downloaded first. CSV exports reference images by their Webflow-hosted URLs, which stop working if the source site is deleted, so we pull every file and rehost it before switching off the old project.
Can the site stay live on Webflow during the rebuild?
Yes. Webflow keeps serving the site until the switchover. Just before launch we export again, or freeze content briefly, so edits made during the build are not lost.
Next step
Want it moved for you? We plan the move around what already ranks.
We inventory every Webflow URL, map each one to its new address in Astro, move the content with its metadata, then switch over and watch indexing.
- Every URL inventoriedA full URL list with a ranking and traffic baseline.
- Every old URL mappedA 301 redirect map so link equity carries over.
- Watched after launchSitemap submitted, then indexing and rankings monitored.
Planning a move from Webflow?
Tell us about your current site and what needs to move, and we will come back to you with the next steps.