The short answer
Change one thing per phase, and let each phase finish in a state you would be happy to stay in. A site that moves from Webflow to Astro and Sanity can do this: first a working site in Webflow, then the same site on the new stack, then new ways of making pages. If a later phase never happens, you still have a finished site.
This is different from routing stages. Here, usually only one system is live at a time, and each phase ends with a switch.
The rule: one change per phase
A site move can change four things: the platform, the design, the content and how the team edits pages. Each one that changes makes it harder to find the cause when something goes wrong. So split them.
| Phase | What changes | What must not change | Gate to the next phase |
|---|---|---|---|
| 1. Build | Design and content, on a platform the team can use now | URLs you want to keep | Live and stable, with its URL and SEO list on file |
| 2. Move | Platform and CMS | Design, copy, URLs, on-page SEO | Parity check passed, and the team can publish |
| 3. New workflow | How pages get made | The look, and the URLs of live pages | A real page shipped through the new process |
Decision rule If someone asks to change the design during phase 2, write it down for after the move. Rewrites and redesigns are easier to judge against a stable baseline.
We have run all three phases on one site, in this order.
When to move off Webflow at all
Webflow is often the right place to stay, so a good build there is not a stepping stone by default. We cover the choice in when to move from Webflow to Astro. Have a clear reason in writing, such as wanting the site in a codebase your team controls, and name who will run that codebase after the move.
Phase 2: getting the content out
Plan this first, because it shapes the Sanity schema.
- Code export will not bring your content. Webflow's code export article says CMS content is not included. Collection lists export empty, and Collection pages do not show bound field content. User accounts, Ecommerce and localised content are left out as well.
- Export each Collection. The same article says Collections can be exported as CSV. Do it early to test your scripts, and again at the switch.
- List every field and where it shows. Plain text, rich text, images, references and option fields each need a matching Sanity field.
- Keep slugs as they are. They are what keep your URLs.
- Copy your images. Find every media URL in the content, including inside rich text, and bring those files across, so nothing depends on the old site.
- Copy your SEO fields. Titles, descriptions and social images per item often live in fields or templates that are easy to miss.
Phase 2: getting it into Sanity
Sanity's import docs set out a method that suits a repeatable move:
- Imports use newline-delimited JSON, one document per line, each with a
_type. - Give each document a stable
_id. Sanity recommends this, and it means you can re-import later. Building the ID from the old item's slug or ID works well. - References go in as weak and are strengthened after every document exists, so the order of documents does not matter.
- Assets can come from an HTTPS URL or a local path, using
_sanityAsset. - By default, the import fails if a document already exists.
--replaceoverwrites, and--missingonly adds what is absent. - Imports can trigger webhooks, so consider turning those off first.
- Schema validation rules do not run on API or client changes, so write your own checks for what came in.
So write the move as a script you can run many times, not a one-off. Run it early and often, fix what breaks, and on the last day run it once more to pick up late edits. Our post on structuring Sanity content helps with the schema.
Phase 2: rebuilding the pages in Astro
Same design, so the test is simple: put the old and new page side by side at each breakpoint. Check these, as they do not come across on their own.
- Trailing slashes. Webflow removes them. Astro's configuration reference has a
trailingSlashoption that defaults toignore, and abuild.formatoption that defaults to folders. For prerendered pages, your host decides how slashes behave. So set these on purpose, and test on the real host. - Redirects. Webflow's 301 list has to be recreated. Astro's docs warn that, in static mode with no adapter, its
redirectsoption writes a meta refresh with no status code. For real 301s, use your host's config or a suitable adapter. - Interactions. Plan to rebuild them in CSS and small scripts, with reduced motion respected.
- Forms. Decide where they post in the new setup, and test each one by receiving a real message.
- Schema, sitemap and robots.txt. Webflow generated its sitemap for you, so decide what now creates each of these.
- Editors. Build the Sanity Studio for the people using it, and have them publish a real page before the switch.
The switch: two ways
| Whole-site switch | Section by section | |
|---|---|---|
| How | Move DNS to the new host on one day | A proxy sends paths to Astro or Webflow |
| Best for | Most marketing sites, especially with the same design | Large sites, or a section with its own timeline |
| Follow | The Site Move Playbook | Chapters 2 to 4 and 6 of this guide |
Because design and URLs stay the same in this phase, a whole-site switch is often the simpler route. Freeze publishing in Webflow for the last run of the script, and tell the content team when they can start publishing in Sanity. Keep the Webflow site published on a staging address until you are sure you do not need it, for quick comparisons.
Phase 3: a new way of making pages
Only start this once the new site is settled. A section library works because every part already matches the brand, so the job shrinks to choosing sections and filling them with content.
- Build sections from real pages, and name them by what they do.
- Write down what each section is for, and what content it needs. Both people and AI tools need this.
- Keep a person in the loop, with a staging link to review before anything goes live.
- Keep the URL, title and schema rules as part of the process, so new pages meet them from day one.
See Astro and Sanity and Webflow to Astro for how we run this work.


