Webflow to Astro migration

Move from Webflow to Astro when your team wants to own the code

Webflow is the right tool for many teams. If you want your own codebase, content in Sanity and changes shipped through an AI workflow, we move your site and keep every URL that ranks today.

  • 50+ B2B SaaS teams trust us
  • 5.0 out of 5 stars
  • 5.0 out of 5 stars
  • 5.0 out of 5 stars
Timeline
6–10 weeksFor a typical SaaS marketing site.
SEO risk
LowWe rebuild your Webflow URLs one to one.
Content
Carried overCMS collections, locales, images, metadata
Design and features
RebuiltComponents, interactions, forms, site search
Price
Fixed priceSet once we have checked every URL.

Why teams switch

When teams move from Webflow to Astro

01

You want to own the code

The site lives in your Git repository, with version history and a review for every change. You can switch hosting providers later without a rebuild.

02

You want AI agents on the site

Claude or Codex work directly in the codebase. Your team describes a change, checks the preview and approves it. That is how our AI-native Websites work.

03

Your content needs to travel

In Sanity, use cases, integrations and customer stories are structured data. Your product app or help center can pull the same entries through the API.

04

You keep hitting plan limits

CMS items, locales, or custom code that only runs through embeds. We check which limit actually applies to you against your specific plan.

Webflow vs. Astro

What changes in your team's day to day

CriterionWebflowAstro
Building pagesVisually in the Designer, no code.Content in Sanity, new pages through the AI workflow with preview and approval.
CodeHosted by Webflow. The export leaves out CMS content.Lives in your repository, with full version history.
Content modelCMS Collections with reference and multi-reference fields.Sanity schemas or Markdown, available to other systems through an API.
Hosting and redirectsIncluded in the plan, 301 redirects in Site settings.A host of your choice, redirects in the project or hosting config.
New featuresNative features, Marketplace apps and custom code embeds.Any code or integration, built by your development partner.

Webflow

  • Visually in the Designer, no code.
  • Hosted by Webflow. The export leaves out CMS content.
  • CMS Collections with reference and multi-reference fields.
  • Included in the plan, 301 redirects in Site settings.
  • Native features, Marketplace apps and custom code embeds.

Astro

  • Content in Sanity, new pages through the AI workflow with preview and approval.
  • Lives in your repository, with full version history.
  • Sanity schemas or Markdown, available to other systems through an API.
  • A host of your choice, redirects in the project or hosting config.
  • Any code or integration, built by your development partner.

What moves

What comes over from Webflow

Content and URLs move over directly. Anything that depends on Webflow's own JavaScript is rebuilt in Astro or replaced.

  • Migrated
  • Partly
  • Rebuilt
  • Replaced
  • CMS Collections

    Migrated

    A script reads every item through the Data API and writes it to Sanity field by field. Rich text becomes structured rich text.

  • Reference fields

    Partly

    References and multi-references become Sanity references. A script reconnects them by ID, so nobody relinks entries by hand.

  • Locales

    Migrated

    We read localized items per locale and link the versions in Sanity. Astro's i18n routing serves the language paths.

  • SEO data

    Migrated

    Titles, meta descriptions and Open Graph images per page. Webflow exports your existing 301 redirects as a CSV.

  • Design and components

    Rebuilt

    Classes, variables and Webflow components become Astro components. The code export is a reference, not the starting point.

  • Interactions

    Rebuilt

    Webflow Interactions run on Webflow's own JavaScript. We rebuild the animations in CSS, or with targeted JavaScript where needed.

  • Forms

    Replaced

    Form processing stays with Webflow. We send every form straight to HubSpot or your CRM and test each submission.

  • Site search and Ecommerce

    Replaced

    Both only work on Webflow itself. Search moves to an external service. If you run a store, we first check whether the move makes sense.

For your marketing

What keeps running for your marketing

Rankings are only one part. We also protect everything your team uses to measure leads and pipeline.

Tracking and attribution

GA4, the tag manager, UTM parameters and conversion events keep running from day one. In Astro tracking scripts load only after consent and do not slow the page. Before launch we compare every event on staging with the old site.

Forms and CRM

We replace Webflow forms with custom forms connected straight to your CRM. Fields, hidden fields for the lead source and the handover to HubSpot, Salesforce or Pipedrive stay the same. We check test leads right in the CRM.

Demo booking

Demo and contact pages, calendars like HubSpot Meetings, Calendly or Chili Piper and your chat stay in place. Old demo URLs from ads, emails and sales decks redirect straight to the new page.

Visibility in AI search

Structured data, clear headings and an up-to-date sitemap are in place from launch. That helps Google and AI search like ChatGPT or Perplexity find your pages again quickly.

Content mapping

How Collections become Sanity documents

In WebflowIn Astro
CMS CollectionSanity document typewith required fields and validation per field
Reference and multi-reference fieldsSanity referencesauthors, categories and integrations stay linked
Rich text fieldsStructured rich textembedded images and links come along
Collection template pagesDynamic Astro routessame path, for example /blog/post-slug
Static pagesAstro pages built from componentsyour team edits copy and images in Sanity
Localized contentLanguage versions in Sanityserved through Astro's i18n config

Process

How we migrate
your Webflow site

An example project: 8 weeks to launch. Afterwards we monitor rankings and redirects for four more weeks.

Migration from Webflow, example project

path digitalYour team

Your team

Access, sign-offs

SEO

URLs, redirects, tests

Build

Pages, content in Astro

Point at a step to see what happens there.

  1. Week 1 · Your team

    Kickoff

  2. Week 1 · SEO

    Audit and URL inventory

  3. Weeks 1–2 · SEO

    Sanity schema and redirect plan

  4. Weeks 2–5 · Build

    Components in Astro

  5. Week 2 · Your team

    Redirect plan sign-off

  6. Weeks 4–6 · Build

    Content migration via API

  7. Weeks 6–8 · SEO

    SEO parity, QA and onboarding

  8. Week 8 · Your team

    Launch

  9. After launch · SEO

    Launch and monitoring

Pre-launch checklist

What we check before launch

Stage 1 of 4

Before the build

Stage 2 of 4

During the build

Stage 3 of 4

Before launch

Stage 4 of 4

After launch

Honestly

When you should stay on Webflow

  • Your marketing team builds pages visually every week

    If campaign landing pages come out of the Designer and that works well, Webflow is the right tool. Moving would take exactly that away from your team.

  • Nobody should own code or deployments

    Astro needs a development partner for new features and updates. On Webflow, the platform handles hosting and maintenance.

  • The problem is the build, not the platform

    Messy classes, missing components, a CMS nobody understands. As a Webflow Enterprise Partner, we can often fix that faster by rebuilding in Webflow.

  • It is mostly about hosting or governance

    Webflow Enterprise has its own options for larger teams, such as custom hosting. We look at those before we recommend switching platforms.

Frequently asked questions about migrating from Webflow to Astro

What B2B SaaS teams want to know before moving from Webflow to Astro.

Can I just export my Webflow site as code?

The code, yes, on Workspace plans. The export includes HTML, CSS, JavaScript and images, but no CMS content, no form processing and only the primary locale. To get a site your team can maintain, we rebuild the components in Astro.

How does the CMS content get out of Webflow?

Per Collection as a CSV, or through the Webflow Data API. We usually use the API, because it lets us read every Collection and locale in one run and reconnect references by their IDs.

Can my marketing team still build pages after the migration?

Your team edits copy, images and CMS entries in Sanity. New pages from existing blocks come through the AI workflow: describe it, check the preview, approve. New blocks and features are built by a developer.

Will our URLs stay the same?

Usually, yes. Astro can mirror the paths of your Collection pages and locales. Where an address changes, it gets a 301 redirect, served as a real redirect by the host or adapter.

What happens to our Webflow Interactions?

They depend on Webflow's own JavaScript and do not carry over. We rebuild the animations that matter for the page, mostly in CSS. Effects that add nothing we drop, after checking with you.

Does Webflow keep running until launch?

Yes. Your site stays online and unchanged until the domain switches. Content published in the meantime moves over before launch. You cancel the Webflow plan only once Astro runs stable.

Plan your migration
from Webflow to Astro

Show us your Webflow site. We will tell you whether Astro or Webflow fits your team better and what a move would involve.