Webflow to Astro
Move off Webflow, onto code you own
When every change waits on a developer and the plan keeps climbing, I move the site to code your team owns. As a Webflow Professional Partner, I start with how your team actually runs the site, then decide Next.js or Astro in the audit.
Fixed price from $5,000 typically 4–6 weeks 30 days of hypercare code in your name
The NewBase Stack
Astro, Sanity and Cloudflare.
What moves
What actually migrates.
| What you have | What happens | Why |
|---|---|---|
| Pages | Rebuild Made again in the new codebase. The old version is a reference, not an import. | Webflow exports the rendered HTML, CSS, JavaScript and assets. That is source material rather than an Astro component architecture, so it informs the rebuild instead of becoming it. |
| CMS content | Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. | Collection data comes out separately from the code export, gets transformed, and lands in Astro content files or whichever headless CMS the new site reads from. |
| Interactions | Rebuild Made again in the new codebase. The old version is a reference, not an import. | They become CSS, written JavaScript or a motion library, and each one gets justified rather than carried across. |
| Forms and platform features | Rebuild Made again in the new codebase. The old version is a reference, not an import. | Form handling, search, localization, memberships and ecommerce are things the platform was doing. None of them are in an export, so each needs a destination chosen for it. |
| URLs | Reconfigure The same thing, set up again. Nothing is recreated, but it has to be pointed at the new site by hand. | Every public path stays unless there is a deliberate reason to change it, and the few that do change get a direct rule. |
Mapping
Nothing here is a file move.
- Webflow Collection A content model Fields, types and which of them are actually required, decided rather than inherited from whatever the Collection accumulated.
- Collection item A content entry In Content Collections, or in a headless CMS, depending on who publishes and how often.
- Collection template A route and components One template becomes a route that renders many entries, built from components the rest of the site shares.
- Item slug A route parameter The existing URL is the input, not the output.
- Multi-reference field A typed relationship References become real relationships the build can check, which is where most Webflow CMS structures gain rather than lose.
Hard parts
Where this migration gets complicated.
- 01
Interactive behavior becomes deliberate code
Astro can render most of a page without shipping component JavaScript to the browser, which is the reason to come here and cuts both ways. Everything configured in Webflow's Interactions panel gets reconsidered and then written by hand, and each one has to earn its island rather than be dropped onto the page.
- 02
The editor has to be rebuilt, not just replaced
Marketing could publish without a developer. After the move they can only publish what the new CMS was set up to let them publish, and every one of those fields is a build decision somebody makes.
Process
How the migration works.
-
Audit
Pages, collections, interactions and forms, written down while the site is still serving them.
-
Rebuild
Pages become components, Collections become a content model, and interactions get written rather than configured.
-
Migrate
Content and assets across, addresses and metadata preserved or remapped, forms and analytics verified before the switch.
-
Hand over
The repository, the migration map and documentation written for somebody who was not here.
Included
What is included.
-
Design rebuild
Rebuilt as components, not approximated.
-
Responsive development
Desktop, tablet and mobile, built and checked.
-
CMS architecture
Collections and fields mapped before build.
-
Content migration
Migrated and checked against the source.
-
Asset migration
Collected, compressed and rehosted.
-
Forms and integrations
Tested through to the final record.
-
URL coverage
Every known public address preserved or deliberately redirected.
-
Metadata and canonicals
Preserved wherever possible.
-
Search footprint preservation
URLs inventoried before and checked after.
-
Pre-launch QA
Forms, templates and old URLs verified.
-
Post-launch support
30 days of indexing and traffic checks included.
After those 30 days, Continuous development is the optional way to keep shipping: $2,500 a month, one request at a time, pause or cancel any month.
Search visibility can move during a migration. The goal is to preserve what search engines already understand, and to catch what changed quickly after launch.
And it is yours at the end. The repository sits in your organization rather than mine, the handoff documentation is written for somebody who was not here, and nothing about the project requires me: another developer or your own team can operate it.
Editing
Leaving Webflow does not have to mean handing every edit to a developer.
-
01
Content Collections, in the repository
For a team that publishes rarely and is happy in a pull request. The content is files beside the code, typed and checked at build time, with no service to pay for and nothing to keep running. It stops suiting you the day somebody outside engineering needs to publish without help.
-
02
Sanity
For a team that publishes regularly, or where the person writing is not the person deploying. Editors get a real interface, the model is explicit, and the site reads it at build time. It is another system to configure and pay for, and the modeling is the part that decides whether editors can work on their own.
-
03
No CMS at all
For a site whose pages change a few times a year. Everything lives in components, changes go through the same review as any other change, and there is no editorial layer to maintain. Honest for a small site, and the wrong answer the moment a blog is added.
Content Collections against a headless CMS, and how the choice is made.
Proof
A migration is not finished when the new site looks right.
-
01 Codebase
A codebase your team owns
Components, routes and styles rebuilt deliberately, not cleaned up from exported markup.
Verified by Repository and component structure
-
02 Site
Everything accounted for
Collections, content, metadata and existing addresses checked against the source.
Verified by Source inventory and migration checks
-
03 Systems
Handoffs that actually arrive
Forms, analytics and CRM checked at their destination rather than at the button.
Verified by Submissions, events and records
The migration is complete when these pass, not when the homepage looks right.
The figures above show the report's shape. Yours are counted from your own site.
Maintenance
Built for people and agents to work on.
The important part is not that an agent can write code. It is that the project is structured well enough for its changes to be understood, reviewed and reversed.
-
Marketing
Editor or AI assistant CMS Preview Publish
On the headless CMS answer above. Choose content collections instead and this lane runs through the repository and the review with the developers, which is exactly why that decision comes before the rebuild rather than after it.
-
Developers
Branch Components and routes Review Deploy
The same workflow as any other repository, which is what makes a second developer able to pick it up.
-
Coding agents
Project instructions Branch Review Deploy
Coding agents use the same repository and review process as developers. Instructions explain the patterns; tests and a human review check the changes before release.
Integrations
Changing the frontend doesn't mean changing your stack.
-
HubSpot
Forms that land in the CRM as records, confirmed by the server rather than by the browser.
CRM
-
Sanity
A content model the marketing team edits and the build renders, with a defined preview and publishing path.
CMS
-
Google Analytics
Traffic and conversions measured against the routes the site actually has.
Analytics
-
Stripe
Checkout handled by Stripe, with the webhook as the record that decides what happened.
Payments
-
Mailchimp
Signups that reach the audience exactly once, whatever the visitor clicks.
Email
-
Zapier
Site events handed to the automations the team has already built.
Automation
Other guides
Coming from somewhere else?
Let me plan your next step.
I can scope a migration. Send a brief and I will reply by email with next steps.