WebzstoreExport
Code export
What it holds
A ZIP of HTML, CSS, JavaScript and images, from a paid Workspace plan
Webflow to Astro Migration
Webflow to Astro Migration
We move Webflow sites to Astro by treating the code export and the CMS data as two separate jobs. The export gives you a starting reference for the front end. Your CMS items, forms, search and store come out another way, or must be rebuilt.
01Choose
Choose what you want to change
Do you want Webflow's CMS replaced, kept in another tool, or only the interactive features rebuilt? Tick one part, several, or the whole move.
Where this startsWe want out of Webflow, and I am not sure what the code export includes or what happens to our CMS items and forms.
In plain terms
- Collection
- A Webflow list of items that share the same fields, such as team members.
- CSV file
- A spreadsheet-style file that holds rows of data.
- Headless CMS
- A content system with no public front end, feeding a separate website.
- Redirect map
- A list that sends visitors from each old address to its new one.
- Front end
- The part of the website that visitors see and use.
02Exports
Which Webflow export gives you what?
These are separate files from separate places. We check each one before planning the build.
Export
CMS Collection CSV
What it holds
The items of one Collection, in a spreadsheet-style file
Export
Ecommerce CSV
What it holds
Ecommerce Collections, exported separately
Export
Membership data
What it holds
Any account export you saved before Webflow turned off User Accounts on 29 January 2026, or data held in a third-party membership tool
Export
Form submissions
What it holds
Past entries, exported separately from the code
Export
Localised content
What it holds
Only the primary language is included in the code export
03Left behind
See what the exported code leaves behind
Webflow states its exported code does not include CMS content, Ecommerce products and checkout, site search, form processing, reCAPTCHA or password protection. Collection lists show an empty state, and the export includes empty Collection template pages. Webflow's native User Accounts feature was turned off on 29 January 2026, so we do not plan around a new export from it. Where members matter, we start from any account file you saved earlier or from the third-party membership tool you now use, and decide how logins are handled in the new site.
We do not claim the exported files run unmodified as an Astro project. Webflow itself says manual edits can break some components. So we use the export as a visual reference and rebuild the pages as Astro components (reusable page parts). Our Headless CMS Development service helps compare where the content could live.
04Collections
Give every Collection a new home
A Collection is a Webflow list of items that share fields, such as case notes, team members or products. For each one we decide: keep it in a headless CMS, or move it into files in the project. We then map the fields and import the CSV.
Reference and multi-reference fields (fields that link one item to another) need to be re-created by hand. We list every link first, so none is lost. Where a site has several languages, we check how each language's content is exported.
05Features
Rebuild forms, search and interactions, then test them
Forms do not work on an exported Webflow site. We connect each one to a form service or a small server function, and test where its messages go. Search is rebuilt as a separate feature. Navbars, sliders and tabs rely on JavaScript, so each is rebuilt and tested.
Our test list covers one item from every Collection, an item with many links, a form with a file upload, the search box, each interaction and the mobile menu. Past form submissions are kept in their export file.
06Launch
Agree editing, publishing and old addresses
Astro builds pages in advance by default (static output), and we would use that for a statically generated site. Editors then need to know how a change reaches the live site, so we agree the editing tool, the rebuild trigger and who runs it. If a site is set to render some pages on request instead, the publishing workflow follows that approach, and we agree it before the build. If you want a different system for editing, see Headless CMS Migration.
Old Webflow addresses go in a redirect map (a list sending visitors from each old address to its new one), and we avoid chains of redirects. We test the map and monitor search performance after launch. No result is promised. Website Migration Services explains the wider process.
Questions about moving Webflow to Astro
Can I use the Webflow code export as my Astro site?
Not unmodified. The export is a reference, and the pages are rebuilt as Astro components.
Will my CMS items be exported with the code?
No. Collections are exported separately as CSV files, and links between items are recreated by hand.
Will my forms keep working?
No. Webflow says forms do not work on exported sites, so each form is rebuilt and tested.
Do I need a paid plan to export the code?
Yes. Webflow offers code export on paid Workspace plans, not on Site plans.
Rebuild with the data in order
Send us your Webflow address, the Collections you use and the forms that matter. We will assess what the code export gives us and what we must recreate.
Explore the next step
- Website Migration ServicesExplore website migration services with Webzstore. Plan your content, features and launch, then discuss the project on a free 30-minute call.
- Headless CMS DevelopmentExplore headless cms development with Webzstore. Plan your existing content, features and launch, then discuss the project on a free 30-minute call.
- Headless CMS MigrationExplore headless cms migration with Webzstore. Plan your existing content, features and launch, then discuss the project on a free 30-minute call.