What is a Webflow to Astro migration?
A Webflow to Astro migration means rebuilding your Webflow site in Astro, moving CMS content into a headless CMS like Sanity or into Markdown, and hosting the result yourself on a platform like Vercel or Cloudflare Pages. Any URL that changes gets a 301 redirect, so search rankings carry over.
Webflow does not convert to Astro automatically. Its exported code is useful as a reference, but we rebuild layouts as Astro components so the code is clean, reusable and easy for your team to maintain.
Should you move at all?
Honest answer: most marketing teams are happy on Webflow, and we build Webflow sites for them. A move to Astro makes sense when one or more of these is true:
- You have developers and want the site in your own repo, with code review
- You need features that are hard to do inside Webflow, like heavy custom logic or tight app integration
- You want full control over performance and the JavaScript each page ships
- You want to choose your own hosting
If none of these apply, staying on Webflow is usually the better choice. Read Webflow vs Astro for the full comparison.
Inventory: URLs, CMS items and assets
We list every URL the Webflow site serves: static pages, every CMS item page, collection list pages, and any pages set up with redirects already. We merge the sitemap, a crawl, Search Console and analytics, just like any migration.
Webflow-specific things we check:
- Existing 301 rules in your Webflow settings. They must come across too, or old links break twice
- CMS collection paths like
/blog-posts/that you may want to rename - Images and files hosted on Webflow's asset CDN
- Custom code in site settings and page settings, like tracking or schema
Moving the CMS to Sanity or Markdown
Webflow lets you export each CMS collection as a CSV. We map every field to a Sanity schema or to Markdown front matter: title, slug, date, author, summary, image, rich text and references between collections.
Rich text needs care. We convert it to Portable Text for Sanity or to clean Markdown, and keep headings, links, lists and embeds intact. Images referenced in posts are downloaded and re-hosted, so nothing still points at Webflow.
Editors get Sanity Studio, with live preview. Developers get typed content in the repo. See Astro + Sanity for how we set this up.
Redirects and true 301s
Astro has a redirects option in its config, including dynamic routes. But in a plain static build, Astro writes redirects as HTML pages with a meta refresh, which is not a real 301. Search engines usually follow these, but a true 301 is the safer signal.
So we set redirects at the host as well. On Vercel that is project config, on Cloudflare Pages a redirects file. We also match trailing slash behaviour to what Webflow did, so /about and /about/ do not become two URLs.
Every rule is tested on the preview deploy and again on production right after launch.
SEO parity, forms and interactions
We generate titles, meta descriptions, canonicals, Open Graph tags and JSON-LD schema from content, so every page has them and nothing depends on someone remembering. Values are carried over from Webflow first, then improved only with your sign-off.
Webflow forms only work on Webflow hosting, so each form is rebuilt to post to a form service, your CRM or a small serverless function. Webflow interactions are rebuilt in CSS and small scripts that respect reduced motion. Most sites end up with far less JavaScript than before.
Launch day and the DNS switch
- We lower DNS TTL a day ahead.
- The production build goes up on Vercel or Cloudflare Pages with your domain attached.
- On a call with you, we change the DNS records from Webflow's values to the new host's values. Email records are not touched.
- Once SSL is live, we test redirects, forms, analytics and the sitemap.
- We submit the new sitemap in Google Search Console.
- Your Webflow site plan stays active for a few weeks as a fallback, then you can cancel it.
After launch: monitoring and what can go wrong
For at least two weeks we check Search Console daily: new 404s, pages dropping out of the index, and clicks on your top URLs. Then weekly, until our 30 days of support end.
- Meta refresh instead of 301. Prevented by setting rules at the host.
- Trailing slash splits. Prevented by matching Webflow's behaviour in config.
- Dead forms. Every form tested live on day one.
- Images still on Webflow. All assets moved before launch.
- Old Webflow redirects lost. Exported and carried into the new rules.






