Preserve what earns attention
Crawl pages and record Search Console demand, links, metadata, media and conversion paths before deciding what changes.
Webflow to Astro migration, without losing the useful parts
Moving from Webflow to Astro is a rebuild, not a code export. We inventory the current site, protect valuable content and URLs, and create an Astro website your team can keep publishing.
- Page and URL inventory
- Content and CMS mapping
- Astro build and launch QA
A planned move from visual builder to custom frontend
Astro gives the frontend team direct control of page code. The trade-off is that Webflow CMS, forms and interactions need an explicit destination.
Astro
Content first. Interaction where it helps.
Keep the page lightweight, with interactive elements added deliberately.
Rebuild content ownership
Map Webflow collections and page components to Astro templates and a CMS such as Sanity where editors still need control.
Verify the new site
Test redirects, canonicals, forms, analytics, structured data and responsive behaviour before and after cutover.
What the destination can look like
Hilvy runs its own website with Astro pages and Sanity content. That is a live example of our Astro implementation. It is not presented as a completed Webflow-to-Astro client migration.
The approach for your site depends on its current Webflow CMS, interactions, integrations and editorial needs.
HILVYGive people a reasonto choose you.Explore this website
A feel for our work.
A short look at the websites we design and build.
The migration sequence
The work is sequenced so content and search decisions are made before the final domain switch.
-
Inventory
Crawl the Webflow site and capture URLs, templates, CMS fields, assets, scripts, forms and important search queries.
-
Map and build
Agree destination URLs and content types, then build Astro components and test the editing workflow with representative pages.
-
Redirect and launch
Prepare direct redirects for changed URLs, verify page metadata and functionality, then monitor coverage and enquiries after release.
Move only for a clear advantage
Where this helps
Teams whose Webflow site now needs custom frontend control, a different content model or engineering ownership that is difficult to support inside the current setup.
When to take another route
If Webflow still serves your marketing team well, a redesign, CMS clean-up or performance pass may be lower-risk and less expensive than migration. Astro does not automatically solve content or ranking problems.
Questions worth asking before you start
Can you export a Webflow site straight into Astro?
There is no dependable one-click conversion for a production site. We rebuild the layouts and components, map CMS content to a destination model and replace or reconnect forms, interactions and integrations. Some assets and copy can be reused after review.
What happens to Webflow CMS content?
We inventory collections, fields, references, rich text and media, then map them to Astro content or a CMS such as Sanity. A sample migration exposes formatting and relationship issues before the full move.
Will the migration preserve our search rankings?
No agency can promise unchanged rankings. We reduce avoidable risk by identifying valuable pages and queries, retaining useful content and URLs where possible, setting direct redirects where needed and verifying canonicals, metadata, links and sitemap output.
Who updates the website after moving to Astro?
That depends on the content model. Editors can manage structured content in a connected CMS, while design-system or component changes remain development work. We document the boundary and train the team before launch.
Is leaving Webflow the right move?
We can review your current site and show what would need to be rebuilt, retained or redirected before you commit.