Move from Webflow to Astro and keep every URL that ranks.
I rebuild your Webflow site in Astro to match the one you have, move your CMS collections into Sanity, rebuild the interactions that matter, and hand your team a repository they own. Your traffic stays where it is.
Why teams leave Webflow.
Every page loads jQuery and the interaction engine.
Webflow ships jQuery and its own webflow.js on every page, whether that page animates or not. On a phone, that weight is the gap between green and red Core Web Vitals.
Only one person dares touch the styles.
A few years of combo classes and one-off overrides later, changing a button means checking forty pages. The designer who built it becomes the only safe pair of hands.
The CMS plan sets your content strategy.
Collection and item caps tied to your plan mean a growing blog, a docs section, or a set of comparison pages hits a pricing tier before it runs out of ideas.
How a Webflow move runs.
-
Export, then inventory
Webflow’s code export leaves the CMS behind, so I pull every collection out through the API, then crawl the live site so nothing that only exists in production gets left behind.
-
Combo classes, untangled
Your classes, combo classes, and swatches become a small set of design tokens and components. Same pixels, but a button now changes in one place.
-
Interactions rebuilt, not embedded
Webflow Interactions become CSS and small scripts that load only on the pages that use them, instead of one engine on every page.
-
URL parity, checked line by line
Collection URLs keep their paths, the 301s you already set in Webflow move to the new host, and I diff the two sitemaps before the DNS switch.
What you own afterwards.
A Git repository with the full history, a build that runs on your own hosting, your content in Sanity where your team edits it, the redirect map, and the speed reports before and after. No Webflow plan to renew, and no part of the site needs me around to keep it running.
Webflow to Astro, answered.
Most marketing sites take 3 to 4 weeks. Sites with several CMS collections and a team that publishes every week take 5 to 6. You get the timeline in the quote, before anything starts.
You can, but you get a snapshot, not a site. The export leaves your CMS content out, keeps jQuery and webflow.js on every page, and hands you generated files nobody wants to maintain. I rebuild instead, so the code is something your team can actually work in.
I export every collection, including rich text, images, references, and SEO fields, and move it into Sanity. Every item keeps its slug, so its URL does not change.
Yes. Most Webflow interactions become plain CSS transitions or a few lines of script. Heavier scroll timelines get GSAP, loaded only on the pages that use it.
Not when the redirect map holds. Every URL that earns traffic keeps its path, the 301s you set in Webflow move across, meta tags and schema come with the content, and I watch Search Console through the first month.
Webflow forms only work on Webflow hosting, so I reconnect each one to your CRM, email tool, or a form service, and test every submission before launch so no lead gets lost.
Not for long. Sanity replaces it with an editor built around your content: fields for exactly what each page needs, a live preview, and no way to nudge a layout out of place by accident.
For most marketing sites, close to nothing. A static Astro site runs on the free or entry tiers of Vercel, Netlify, or Cloudflare. Sanity has a free plan that covers many marketing teams, and if yours needs a paid one, I list it in the quote. Keep your Webflow plan until the new site is live, then cancel it.
Send me your Webflow URL.
I reply within a day with what the move involves, which package it lands in, and where Webflow is actually costing you.
Plan the move