Part of Migration to Astro
Webflow reprices agency and freelancer workspaces and legacy sites on or after 16 November 2026. We rebuild what its export skips: the CMS, the forms and the redirects.
What does moving from Webflow to Astro involve?
Rebuilding the three things Webflow’s code export leaves out: working CMS pages, a form backend and your 301 redirects. Webflow’s generated classes and scripts give way to plain components, and every URL is kept. Our own 15-page Webflow site moved in one working week, with 33 redirects.
Who it is for
Included
Timeline
Under 24 hours
The CMS collections, the 301 list, the forms and the custom code, priced in a fixed quote.
Then
Paths such as /blog/your-post stay, and you decide which draft and archived items come along.
To the estimate’s date
Components a developer can read, in place of generated classes such as div-block-12.
Launch day
Old 301s point straight at the final address, forms are tested live, and only then is the Webflow plan cancelled.
Price
Results
“…their ability to accurately estimate the timeline and effort required for each feature.”
Questions
No. Annual billing locks current pricing for a year, so you can move without a rush.
You would keep the generated classes and scripts, with no working CMS pages or forms. On our own site the export shipped 214 KB of webflow.js plus 89 KB of jQuery.
Files in the repository, or a headless CMS that the estimate names with its running cost.
Often, yes, when your marketing team runs the site and builds pages visually every week. For established companies we build or rebuild the site in Webflow instead of moving it.
Thirty minutes with a builder, not a salesperson, to work out whether we are the right team for it. If we are not, we will say so.