FREEFirst project with us? Your landing page design is on the house.See the offer
Booking for Q4'26

Webflow to Astro migration, code you own.

We build Webflow sites every week, and we still move some of them to Astro. When you want more speed, full code ownership, or a content setup your developers control, we rebuild your site in Astro and keep every URL and ranking in place.

  • Webflow CMS exported and moved to Sanity or Markdown
  • Every Webflow URL kept or redirected with a real 301
  • Forms and interactions rebuilt without heavy scripts
★★★★★5.0Trusted by ClanX, Petavue, Tata and more

Plan my Astro move

Tell us a little. We reply within one working day with a price and timeline.

🔒 No spam. No sales calls unless you ask for one.

Got it. Thanks!

We will reply within one working day.

A Webflow to Astro migration rebuilds your Webflow site as an Astro codebase, moves your CMS content into Sanity or Markdown files, and redirects any changed URL with a 301. You get a very fast static site, full ownership of the code, and hosting on a platform like Vercel or Cloudflare Pages.

Why move off Webflow

When the site
becomes a product.

Webflow is a great fit for most marketing sites. We are a Webflow Premium Partner and we recommend it often. But some teams reach a point where they want the site in their own repo, reviewed like the rest of their code, deployed by their own pipeline.

Astro fits that well. It ships HTML first and adds JavaScript only where a component needs it. Content can live in Sanity for editors or in Markdown for developers. The move is mostly about keeping what already works: URLs, metadata and rankings.

orbit.dev · Webflow hostingorbit.dev · your repo, your hostWebflowLive on Astro
OrbitStart freenav_component
v4 is outShip APIs your team can trust.

Typed contracts, mock servers and checks in every pull request.

Start freenpm i @orbit/cli
hero_wrap
SprinkleWhiskGingerShortbreadsection_logos
Contracts

One source for every API.

Mocks

Build before the backend.

Checks

Catch breaks in review.

feature_grid
OrbitDocsBlogStatus Made in Webflow
OrbitStart freeNav.astro
v4 is outShip APIs your team can trust.

Typed contracts, mock servers and checks in every pull request.

Start freenpm i @orbit/cli
Hero.astro
SprinkleWhiskGingerShortbreadLogos.astro
Contracts

One source for every API.

Mocks

Build before the backend.

Checks

Catch breaks in review.

Features.astro
OrbitDocsBlogStatus0 KB JSFooter.astro
Rebuilding as Astro components
301 map / 205 URLs
/blog-posts/launch-notes→/blog/launch-notes...301
/case-studies/clanx→/work/clanx...301
/contact-us→/contact...301
/team-members/abdul→/about...301
/blog-categories/news→/blog...301
Search ConsoleClicks · 90 days
Clicks holding steadyLaunch day
astro buildpreview
src/pages142 pages
sitemap-index.xmlwritten
vercel.json205 rules
imagesoptimised
buildcomplete

Example site. The loop shows how we move a page: rebuild, redirect, then watch Search Console.

JavaScript by default

Astro pages ship no JavaScript unless a component asks for it, so pages stay light.

Code you own

Your site lives in Git. Any developer can read it, review it and deploy it.

Typical move

Most marketing sites move in 3 to 5 weeks, plus the Search Console watch.

Redirects as code

Your redirect map,
in the repo.

In Astro, redirects live in config, next to the code. Dynamic routes mean one line can move a whole Webflow collection path to a new one.

One detail matters a lot. A plain static Astro build writes redirects as small HTML pages, not true 301s. So we also write the rules at the host level, for example in Vercel or Cloudflare Pages config, so search engines get a real 301 status.

astro.config.mjsvercel.json
1{2  "redirects": [3    { "source": "/blog-posts/:slug", "destination": "/blog/:slug", "permanent": true },4    { "source": "/case-studies/:slug", "destination": "/work/:slug", "permanent": true },5    { "source": "/contact-us", "destination": "/contact", "permanent": true }6  ]7}
Redirects at the host3 rules cover 205 URLs
Deploymain
git pusha3f9c21 · move blog collection
Buildastro build · 142 pages
Previeworbit-git-move.vercel.app
Productionorbit.dev · global CDN
$ curl -I orbit.dev/blog-posts/launch-notes
HTTP/2 301
location: /blog/launch-notes
JavaScript per pagebefore any of your own scripts
Webflowwebflow.js and jQuery
Astro0 KB by default

Webflow vs Astro

Before and after
the move.

Neither is better for everyone. This is what changes for your team.

FeatureAstro + SanityWebflow
Who owns the codeYou, in your Git repoLives in your Webflow project
JavaScript shippedNone by defaultWebflow runtime on every page
Editing contentSanity Studio or MarkdownWebflow Editor, visual
Editing layoutDevelopers, or Sanity sectionsDesigners, visually
HostingVercel, Cloudflare Pages and othersWebflow hosting
Code review and previewsPull requests and preview deploysStaging domain
Best forTeams with developers who want controlTeams who want visual editing

What changes

What does not come
with you from Webflow.

Some Webflow features are tied to Webflow hosting. We plan a replacement for each one before we build.

Webflow forms

Stop working off Webflow hosting. We rebuild them with a form service, your CRM or Cal.com.

Interactions

Rebuilt in CSS and small scripts, with reduced motion respected.

The Editor

Replaced by Sanity Studio, so editors still change content without code.

Hosting and SSL

Moved to Vercel or Cloudflare Pages, with SSL and a global CDN.

Sitemap and redirects

Generated by Astro and set at the host, tested before launch.

Asset CDN

Images and files moved off Webflow so nothing depends on the old project.

Pre-launch checklist

Ten checks before
we flip the domain.

Run on the preview deploy, then on production.

  • Every Webflow URL from the sitemap, a crawl and Search Console has a match or a 301.
  • Redirect status is a real 301 at the host, not an HTML refresh.
  • Trailing slashes behave the same way they did on Webflow, so URLs do not split.
  • Titles, metas and Open Graph match the Webflow site, page by page and per CMS item.
  • Canonicals and schema are generated from content, not typed by hand.
  • Images are moved off the Webflow CDN, resized and served in modern formats.
  • Forms post to the new endpoint and land in the right inbox or CRM.
  • Analytics and consent fire on every page type.
  • Sitemap and robots.txt are generated and list only live, canonical URLs.
  • Speed key pages pass Lighthouse on mobile with no layout shift.

What moves

Your site,
moved layer by layer.

Moving from Webflow to Astro is more than copying pages. These are the seven layers we move, in the order we move them.

  1. 01
    Audit

    Every URL, page, form and script on your Webflow site, listed in one sheet before anything moves.

  2. 02
    Content

    Pages, posts and collections moved into Astro, field by field, so nothing is retyped by hand.

  3. 03
    Design and build

    Pages rebuilt in Astro as reusable components, matching the look you have or a new design.

  4. 04
    Redirects

    Every old URL gets a 301 to its new address, so old links and search results still land on the right page.

  5. 05
    SEO carried over

    Titles, descriptions, schema and image alt text move with each page.

  6. 06
    Forms and tracking

    Forms, analytics and connected tools set up again and tested before launch.

  7. 07
    Launch and watch

    DNS switched and the sitemap submitted, then we watch Search Console for errors.

What you get

Everything a Webflow
to Astro move needs.

No add-on surprises. These come with every project.

01

URL inventory

Every page, CMS item and asset URL, with traffic.

02

Astro build

Components and layouts that match your current design.

03

CMS move

Collections exported to CSV, then imported into Sanity or Markdown.

04

301 redirects

Set in Astro and at the host, so status codes are real.

05

SEO parity

Titles, metas, canonicals, Open Graph and JSON-LD schema.

06

Forms rebuilt

A form service or your CRM, tested end to end.

07

Hosting and DNS

Vercel or Cloudflare Pages set up, DNS switched with you.

08

Search Console watch

Daily for two weeks, then weekly through our 30 days.

Our process

How a Webflow to
Astro move runs.

3 to 5 weeks for most marketing sites. Coloured bars are ours, striped bars are yours.

Webflow to Astro · scope to launchYou

Our work

Sites we have
built and moved.

Try us first · Try us first · Try us first ·

Not sure Astro is right? Ask us first.

We send a free URL inventory of your Webflow site and an honest note on whether Astro is worth it for you. If staying on Webflow makes more sense, we will say so.

Get my free URL inventoryFree, no strings

The guide

The Webflow to Astro migration guide

How to leave Webflow hosting without losing rankings, forms or your editors' sanity.

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

  1. We lower DNS TTL a day ahead.
  2. The production build goes up on Vercel or Cloudflare Pages with your domain attached.
  3. 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.
  4. Once SSL is live, we test redirects, forms, analytics and the sitemap.
  5. We submit the new sitemap in Google Search Console.
  6. 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.

Wall of love

Don't take
our word for it.

Hear it from the founders and teams we have built for.

Bailey McElligott, Design Director
Bailey on working with Kookies.
Bailey McElligott · Design Director0:17
Verified review
5.0
★★★★★
"They are very professional and the best at what they do."

Juned Khatri, Chief, BubbleWrap
Web development · Dec 2022 to Jan 2023 · Quality, schedule, cost and willing to refer: 5.0

Read it on Clutch
"Fast, efficient and beautifully designed! Kookies nailed our website with pixel-perfect execution and smooth interactions."
Juned KhatriFounder, ClanX
"They are very professional and the best at what they do. Kookies surpassed expectations with Webflow. Thrilled with the results!"
Juned KhatriChief, BubbleWrap
"Kookies' professionalism, dedication and exceptional design skills exceeded our expectations. Highly recommended for high-quality work and timely delivery."
AA
Ali Al MuttawaCo-founder, Artal Invest
"A thorough job, with high-quality work in a short timeframe. Abdul and his team were prompt, professional and patient with all our inputs. Happy to recommend them."
Sejal SinghiManaging Consultant, Baraka Impact Finance

FAQs

Webflow to Astro
questions.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Usually for code ownership, performance control or custom features. Teams with developers often want the site in Git, with pull requests and preview deploys. If you do not need that, Webflow is often the better choice.

No tool converts it cleanly. Webflow can export code and CMS CSVs, which we use as a reference and as content. The Astro site itself is rebuilt as components.

Your editors use Sanity Studio, a visual content editor with preview. If your team prefers, content can also live in Markdown files in the repo.

No, Webflow forms only work on Webflow hosting. We rebuild them to post to a form service, your CRM or a small function, and test each one before launch.

We set them in Astro and at the host, so search engines get a real 301 status. A plain static Astro build alone writes redirect pages, not true 301s.

A careful migration keeps them. We keep URLs where we can, redirect the rest, carry over all metadata, and check Search Console daily for two weeks.

You get a fixed quote after a 20 minute call. Moves start at $2,000. First-time clients get $500 off projects of $2,000 or more.

For 30 days after launch we make safe changes for free: copy edits, image swaps, colour tweaks and link updates, and we fix anything we built that does not work. New sections, page redesigns and new features are not part of it. We quote those separately, or they are covered by a care plan.

Ready when you are

Let's move you
to Astro.

Start with a free URL inventory. We map every page before anything moves.

★★★★★5.0 on Clutch
Abdul Quadir
Talk to our teamA senior lead runs your call. Abdul, our founder, often joins.

Book a free 20 minute call

Pick a day that works for you.

See open timesOpen calendaror email hello@kookies.io
Book a callGet a quote