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

Framer to Astro migration, yours to keep.

Framer is a lovely place to start a site. When you want the code in your own repo, your own hosting and more control over what each page loads, we rebuild your Framer site in Astro and keep every URL and ranking in place.

  • Framer CMS collections moved to Sanity or Markdown
  • Every Framer URL kept or sent to its new home with a real 301
  • Framer effects rebuilt in light CSS and small 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 Framer to Astro migration rebuilds your Framer site as an Astro codebase, moves Framer CMS content into Sanity or Markdown, and sets a 301 redirect for any URL that changes. You end up with a fast static site in your own Git repo, hosted where you choose, such as Vercel or Cloudflare Pages.

Why teams leave Framer

Great to start.
Hard to own.

Framer gets a good looking site live fast, and we build Framer sites for clients who want exactly that. The site lives inside Framer, though. Hosting, the CMS and the code that runs each page all stay on their platform.

Teams with developers often want more: the site in their own repo, reviewed in pull requests, content their engineers can query, and full say over the scripts each page loads. Astro gives you that. The move is mostly about keeping what already works: URLs, metadata, design and rankings.

Starting price

Framer to Astro moves start at $3,000. You get a fixed quote after a 20 minute call.

Code you own

The site lives in your Git repo. Any developer can read it, review it and deploy it.

Typical move

Most Framer marketing sites move in 3 to 5 weeks, then we watch Search Console.

How the new site is built

Components,
not canvas layers.

In Framer, a page is a stack of frames and components on a canvas. In Astro, each section becomes a small, reusable component in your repo, fed by content from Sanity or Markdown.

That means a new landing page is a set of sections your team already has, not a fresh copy of an old page. Pages ship plain HTML first and load JavaScript only where a component needs it.

What changes

What stays behind
in Framer.

Some things only work while the site is hosted on Framer. We plan a replacement for each one before we build.

Framer forms

Rebuilt to post to a form service, your CRM or a small function, and tested end to end.

Effects and motion

Appear, scroll and hover effects rebuilt in CSS and small scripts, with reduced motion respected.

Editing on the canvas

Replaced by Sanity Studio, so editors still change copy and images without code.

Framer hosting

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

Redirects and sitemap

Framer redirects exported and set at the new host, sitemap generated by Astro.

Images and files

Downloaded from Framer, resized and served from your own project.

Pre-launch checklist

What we check before
the domain moves.

Run on the preview deploy, then again on production.

  • Every Framer URL from the sitemap, a crawl and Search Console has a match or a 301.
  • Existing Framer redirects are carried over, so old links do not break twice.
  • Redirect status is a real 301 at the host, not an HTML refresh.
  • Titles, metas and social images match the Framer site, page by page and per CMS item.
  • CMS items have the same slugs, dates, authors and images as before.
  • Motion feels the same and switches off for people who ask for reduced motion.
  • Forms post to the new endpoint and land in the right inbox or CRM.
  • Analytics and consent fire on every page type.
  • Speed key pages pass Lighthouse on mobile with no layout shift.

What moves

Your site,
moved layer by layer.

Moving from Framer 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 Framer 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.

Review before launch

Check the preview
on every screen.

You get a preview link early in the build and keep it to the end. Every pull request gets its own preview too, so you can see a change before it ships.

Leave comments right on the page. Nothing goes live until you have signed off on desktop, tablet and mobile and the launch checklist is green.

staging.fieldandclay.comStaging
Field & ClayShop
STONEWAREMade slowly. Used daily.
1Field & Clay teamCan the photo be bigger?Resolved
DesktopSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
2Field & Clay teamMenu feels crampedResolved
TabletSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
3Field & Clay teamButton text too smallResolved
MobileSigned off
Waiting for sign-off on 3 screensAll screens signed off. Checklist green.Switch domain

Framer vs Astro

Before and after
the move.

Framer suits many teams. This is what changes for yours.

FeatureAstro + SanityFramer
Who owns the codeYou, in your Git repoLives in your Framer project
HostingVercel, Cloudflare Pages and othersFramer hosting
JavaScript per pageOnly what a component needsFramer runtime on every page
Editing contentSanity Studio or MarkdownFramer CMS and canvas
Editing layoutDevelopers, or Sanity sectionsDesigners, on the canvas
Code review and previewsPull requests and preview deploysStaging inside Framer
Best forTeams with developers who want controlSmall teams who want to design and publish in one place

What you get

Everything a Framer
to Astro move needs.

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

01

URL inventory

Every page, CMS item and file URL, with its traffic.

02

Astro build

Components and layouts that match your Framer design.

03

CMS move

Framer collections moved into Sanity or Markdown.

04

301 redirects

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

05

SEO carried over

Titles, metas, canonicals, social images and 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 Framer to
Astro move runs.

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

Framer 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 Framer site and an honest note on whether Astro is worth it for you. If staying on Framer makes more sense, we will say so.

Get my free URL inventoryFree, no strings

The guide

The Framer to Astro migration guide

How to leave Framer hosting without losing rankings, forms or the design your team loves.

What is a Framer to Astro migration?

A Framer to Astro migration means rebuilding your Framer site as an Astro project, moving Framer CMS content into Sanity or Markdown, and hosting the result on a platform like Vercel or Cloudflare Pages. Any URL that changes gets a 301 redirect, so search engines and old links follow along.

There is no button that turns a Framer project into clean Astro code. We use the live site as the reference and rebuild each section as a component, so the code is tidy and easy for your team to keep up.

Should you move at all?

Most small teams are happy on Framer, and we build Framer 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 want to choose your own hosting and own the build
  • You need the site to share content or components with your product
  • You want full control over the scripts each page loads

If none of these apply, staying on Framer is usually fine. Read Framer vs Astro for the full comparison.

Inventory: pages, CMS and files

We list every URL the Framer site serves: pages, every CMS item, and any redirects already set in Framer. We merge the sitemap, a crawl, Search Console and analytics, so nothing with traffic gets missed.

Framer things we check on top:

  • Redirects in your Framer site settings, which must come across too
  • Collection paths you may want to rename on the way
  • Images and files hosted by Framer
  • Custom code added in site or page settings, like tracking tags

Moving the Framer CMS

Each Framer collection is exported and mapped field by field: title, slug, date, author, summary, image, rich text and links between collections. Content lands in Sanity for editors or in Markdown for developers.

Rich text gets cleaned on the way, keeping headings, links, lists and embeds. Images in posts are downloaded and re-hosted, so nothing still points at Framer. See Astro + Sanity for how we set up the editor side.

Design and motion

Framer sites are often design led, with appear and scroll effects on most sections. We rebuild the look first, then the motion, using CSS and small scripts instead of a heavy runtime.

Every effect respects reduced motion settings, and the page reads fully before any script runs. If you want a fresh design while you move, we can do that as part of the same project.

Redirects and true 301s

Astro can write redirects in its config, but a plain static build writes them as small HTML pages with a refresh, not a real 301. So we also set every rule at the host, in Vercel or Cloudflare Pages config.

We match trailing slash behaviour to the old site, so /about and /about/ do not split into two URLs. Every rule is tested on the preview deploy and again right after launch.

Launch day and after

  1. We lower DNS TTL a day ahead.
  2. The production build goes up with your domain attached.
  3. On a call with you, we change the DNS records from Framer to the new host. 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. Keep your Framer plan for a few weeks as a fallback, then cancel it.

For two weeks we check Search Console daily for new 404s and dropped pages, then weekly until our 30 days of support end.

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

Framer to Astro
questions.

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

No tool converts a Framer project into clean Astro code. We use the live site and your CMS content as the source and rebuild each section as an Astro component.

Yes. Every collection item moves with its fields, slug, images and rich text into Sanity or Markdown, so URLs and content stay the same.

Close to it. We rebuild Framer effects in CSS and small scripts, and they switch off for visitors who ask for reduced motion.

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

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

Framer to Astro moves start at $3,000. You get a fixed quote after a 20 minute call, and first-time clients get $500 off projects of $2,000 or more.

If your team wants to keep designing and editing visually, Webflow is often the better fit. We run both moves and will tell you which one suits you.

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
off Framer.

Send the form and get a price and timeline within one working day. Or book a quick call with our team.

★★★★★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