Framer to Astro migration

Move from Framer to Astro and own the code behind your site

On Framer, the platform decides where your site runs and what it loads. We rebuild it in Astro, move the CMS to Sanity and protect 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
5–8 weeksFor a typical SaaS marketing site.
SEO risk
MediumWe rebuild collection paths and localized URLs exactly.
Content
Carried overCMS collections, page copy, images, metadata
Design and features
RebuiltLayouts, components, effects, forms
Price
Fixed priceSet once we have checked every URL.

Why teams switch

Common reasons to leave Framer

01

Pages load more than they need

A site builder ships scripts for features many pages never use. Astro renders HTML and only loads JavaScript for components that need it. We measure before and after with PageSpeed Insights.

02

The code isn't yours

Pages live on the Framer canvas and custom logic runs as code components inside Framer. With Astro, the whole site sits in your repository, where you can review it, version it and hand it over.

03

Hosting isn't your call

Framer sites run on Framer. An Astro project deploys to Vercel, Netlify, Cloudflare or your own servers, depending on what your IT or privacy requirements say.

04

You want AI agents to do the edits

In an Astro project, every page is code and every piece of content is a Sanity document. That's a format Claude or Codex can work in: they prepare the change, your team approves the preview.

Framer vs. Astro

What changes for your team

CriterionFramerAstro
CodePages on the canvas, custom logic as React code components inside Framer.Your own repository of Astro components, versioned in Git.
HostingIncluded, on Framer's infrastructure.Your choice: Vercel, Netlify, Cloudflare or your own servers.
JavaScript in the browserDecided by the platform.None by default, only where a component needs it.
EditingVisual, on the canvas, built for designers.Content in Sanity, bigger changes through the AI workflow with a preview.
RedirectsIn Site Settings under Hosting, with placeholders.In the Astro config or at your host, documented in code.

Framer

  • Pages on the canvas, custom logic as React code components inside Framer.
  • Included, on Framer's infrastructure.
  • Decided by the platform.
  • Visual, on the canvas, built for designers.
  • In Site Settings under Hosting, with placeholders.

Astro

  • Your own repository of Astro components, versioned in Git.
  • Your choice: Vercel, Netlify, Cloudflare or your own servers.
  • None by default, only where a component needs it.
  • Content in Sanity, bigger changes through the AI workflow with a preview.
  • In the Astro config or at your host, documented in code.

What moves

What comes over from Framer

Content transfers, the canvas becomes code. If a Framer feature has no direct replacement, you'll know at the inventory stage.

  • Migrated
  • Partly
  • Rebuilt
  • Replaced
  • CMS content

    Migrated

    We export each collection as CSV, clean up the fields and import the items as documents in Sanity.

  • Pages and layouts

    Rebuilt

    Canvas layouts become Astro components and page templates. The design can stay as it is; what's underneath is new.

  • Code components

    Partly

    Framer code components are React components. Many keep running in Astro as islands; we adapt the parts tied to Framer.

  • Effects and animations

    Rebuilt

    Scroll and hover effects are rebuilt with CSS or small scripts and only where they help explain something.

  • SEO data

    Migrated

    Page titles, descriptions and Open Graph images from Framer move into dedicated Sanity fields, page by page.

  • Forms

    Rebuilt

    We rebuild Framer forms, connect them straight to HubSpot or your CRM and test every submission.

  • Language versions

    Partly

    Locales and localized paths from Framer Localization are recreated in Sanity and Astro routing, path by path.

  • Marketplace components

    Replaced

    Components and plugins from the Framer Marketplace are replaced with custom components or direct integrations.

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 Framer 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 Framer content maps to Sanity and Astro

In FramerIn Astro
CMS collectionSanity document typewith typed fields and real references
Collection pageDynamic Astro routesame path, same slug as before
Component with variantsAstro component with propsvariants become options your team picks in Sanity
Code componentReact island in Astroloads JavaScript only when the component needs it
CMS imagesSanity assetspulled in from the image URLs during import
LocalesLanguage fields or one document per languagedepending on how much the versions differ

Process

How we migrate
your Framer site

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

Migration from Framer, 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, URL inventory and baseline

  3. Weeks 1–2 · SEO

    Redirect plan and Sanity schema

  4. Weeks 2–4 · Build

    Astro components and templates

  5. Week 2 · Your team

    Redirect plan sign-off

  6. Weeks 4–5 · Build

    Content migration

  7. Weeks 5–7 · SEO

    SEO parity, QA and handover

  8. Week 7 · 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

To be honest

When you should stay on Framer

  • Your design team iterates visually every week

    If designers build pages themselves on the canvas and nobody on the team wants to touch code, Framer is the better tool.

  • Nobody should own new features

    Your team edits content in Sanity on its own. New components and integrations in Astro need a development partner.

  • The problem is the message, not the platform

    If the site is fast enough and simply doesn't convince, rewriting the content will do more than a migration.

  • Translation runs entirely in Framer

    If your team relies on Framer Localization and Auto Translate, we first work out what the translation process should look like in Sanity.

Frequently asked questions about migrating from Framer to Astro

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

Can I take my Framer site's code into Astro?

Not as a project you could maintain. Framer exports CMS content as CSV through a plugin; we rebuild pages and components in Astro. The design can stay exactly as it is.

Does all our CMS content come with us?

Yes. We export every collection, map the fields to a Sanity schema and import items and images. References between collections are kept.

What happens to our code components?

Framer code components are React components and Astro can render React. So we keep many of them and only strip out what's tied to Framer.

Will the site actually get faster?

That depends on your current site. Astro ships HTML without JavaScript by default. We measure your key pages before and after the move with PageSpeed Insights, so you see the result for yourself.

Can my team change pages without a developer?

Your team edits copy, images, blog posts and new pages built from existing blocks in Sanity. Bigger changes go through the AI workflow of our AI-native websites. New features still need a development partner.

What does a Framer to Astro migration cost?

A full relaunch with positioning, copy, design and build typically costs €40,000–60,000 net, less or more depending on scope. A pure migration costs less. We agree the scope in a call, then you get a fixed price.

Plan your migration
from Framer to Astro

Show us your Framer site. We'll tell you which components get rebuilt, what your Sanity model looks like and which URLs need extra care.