Gemin
Start a project

Webflow to Astro

Migrate from Webflow to Astro

I am a Webflow Professional Partner, so the honest answer matters: most marketing sites should stay on Webflow. Astro makes sense when the site is mostly static, the team is comfortable with a build workflow and performance or code ownership matters more than visual editing.

Start a project

A migration like this usually takes 2–4 weeks

Why people move

What changes when you move from Webflow to Astro.

What is being compared Webflow Astro
Structural changes Webflow Visual editing, inside the site Astro Code, a review and a deploy Content editing is the separate question, and the answer depends on whether the Astro site reads Markdown, a Git workflow or a headless CMS. Structure is the part Webflow wins outright, and it is the thing you are giving up. Be sure.
JavaScript shipped Webflow Webflow's runtime, plus whatever the site adds Astro Little by default, with each island added on purpose The reason to pick Astro over the alternatives, and the reason every interaction becomes a deliberate decision rather than a panel setting.
Content model Webflow Structured collections, inside Webflow's CMS Astro Markdown, content collections, or a CMS the project connects to
Ownership Webflow The platform, the hosting and the publishing, all managed for you Astro Your team owns the codebase, the dependencies, the build and the deploy

Once you have decided

What actually migrates.

What you have What happens Why
Pages Rebuild Made again in Astro. The old version is a reference rather than something that can be imported. Webflow exports the rendered HTML, CSS, JavaScript and assets. That is source material rather than an Astro component architecture, so it informs the rebuild instead of becoming it.
CMS content Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Collection data comes out separately from the code export, gets transformed, and lands in Astro content files or whichever headless CMS the new site reads from.
Interactions Rebuild Made again in Astro. The old version is a reference rather than something that can be imported. They become CSS, written JavaScript or a motion library, and each one gets justified rather than carried across.
Forms and platform features Rebuild Made again in Astro. The old version is a reference rather than something that can be imported. Form handling, search, localization, memberships and ecommerce are things the platform was doing. None of them are in an export, so each needs a destination chosen for it.
URLs Reconfigure The same thing, set up again. Nothing is recreated, but it has to be pointed at the new site by hand. Every public path stays unless there is a deliberate reason to change it, and the few that do change get a direct rule.

Before you budget it

Where this migration gets complicated.

  1. 01

    Interactive behavior becomes deliberate code

    Astro can render most of a page without shipping component JavaScript to the browser, which is the reason to come here and cuts both ways. Everything configured in Webflow's Interactions panel gets reconsidered and then written by hand, and each one has to earn its island rather than be dropped onto the page.

  2. 02

    The editor has to be rebuilt, not just replaced

    Marketing could publish without a developer. After the move they can only publish what the new CMS was set up to let them publish, and every one of those fields is a build decision somebody makes.

How it runs

How the migration works.

  1. 01

    Plan

    Pages, collections, interactions, forms and everything the platform was quietly doing, written down while the site is still on it, and where the content lives next: Markdown, Astro content collections, or a CMS somebody picked on purpose.

  2. 02

    Build

    Pages become components and the interactions become code that somebody now maintains.

  3. 03

    Migrate

    Content and assets moved across, and URLs, metadata and structured data carried over unchanged. The map exists to prove that they were.

  4. 04

    Launch

    Forms arriving, every route rendering, tracking intact, then the deploy. Typically 2–4 weeks, then a week of watching what the old addresses return.

What you are buying

What is included.

  • Design rebuild

    Rebuilt as components, not approximated.

  • Responsive development

    Desktop, tablet and mobile, built and checked.

  • CMS architecture

    Collections and fields mapped before build.

  • Content migration

    Migrated and checked against the source.

  • Asset migration

    Collected, compressed and rehosted.

  • Forms and integrations

    Tested through to the final record.

  • URL parity

    Every public address the same on both sides.

  • Metadata and canonicals

    Preserved wherever possible.

  • Search footprint preservation

    URLs inventoried before and checked after.

  • Pre-launch QA

    Forms, templates and old URLs verified.

  • Post-launch support

    One week of indexing and traffic checks included.

Search visibility can move during a migration. The goal is to preserve what search engines already understand, and to catch what changed quickly after launch.

Other migrations

Coming from somewhere else?

Reach out and see if we are a good fit.

Start a project

Currently booking two to four weeks out.