Framer to Astro migration: code you own, React included
Framer can't hand you your published site as files to host yourself. We rebuild it in Astro, a fast code base your developers own, with every URL mapped and tracking rebuilt. Astro renders React components, so a team that thinks in React or Next.js has somewhere familiar to work.We rebuild your Framer site in Astro, code your developers own, with every URL mapped. Astro renders React components.
- Full code control
- Every Framer URL mapped
- Hosted where you choose
- Live Framer sitePages, CMS items, forms and redirects read off the published site
crawl - Content files in GitBlog and lists as JSON or Markdown, checked against a schema
content collections - Astro pagesLayouts rebuilt in code, with React components where a page needs them
build - Host and redirectsOld addresses answered with permanent redirects from the host
301
- Forms to CRM or n8n
- GTM and GA4
- Search Console
Teams we've worked with
Six things we plan for
Leaving Framer for code is a rebuild. Most of the risk is in the parts a visual builder did for you without saying so.
There's no export to start from
Framer's own help says published sites can't leave as standalone files, since they rely on Framer's backend. So we read your live pages for every URL, title and form, and rebuild from that.
React and Next.js are the wrong question first
Developers often ask for a framework by name. Astro can render React components for the interactive parts, and the rest ships as plain, fast HTML. If your project needs a full Next.js application, we'll say so on the call.
Redirects that are only a meta refresh
In Astro's static output, redirects become HTML files with a meta refresh tag, and the status code isn't used. Google prefers permanent server-side redirects, so we serve them from the host and test each one.
Forms have nowhere to go
A static page can't take a form post, and Astro Actions only work on pages rendered on demand. We send forms to a small endpoint that checks them and passes them to your CRM or automation.
Images skip Astro's processing
Anything in public/ is served untouched, and remote images are processed only for domains you authorise. We keep images in the project so Astro resizes them and sets their dimensions.
Your team loses the visual canvas
Editing moves to fields and blocks in Keystatic. Anything new in a layout needs a developer first, which we tell you before you commit.
A site your developers own
Your content as files in your repo, your URLs kept, and hosting wherever you choose.
Everything on the Framer site, listed
Pages, CMS items, forms, redirects and tags, taken from the published site and checked against the rebuild.
Your content as files
Astro content collections hold Markdown, MDX or JSON files, checked against a schema, so a missing field fails the build instead of reaching your site.
Pages rebuilt in code
Layouts rebuilt in Astro and compared with the Framer page before anything goes live, with React components where a page has real interaction.
Every old address kept
Slugs matched where we can, and permanent redirects served from the host for the rest. Search Console gets the new sitemap on launch day.
Forms into your systems
Forms post to a small endpoint that checks them and hands them on to your CRM or automation. The site sends no email itself.
Tracking
GTM loads after the page, and GA4, Google Ads and Meta are each checked with a test enquiry.
Images in the project
Astro resizes them and sets width and height, which helps stop layout shift.
Editing in Keystatic
A form for each kind of page and blocks to put in order, saved as commits. A new section type needs a developer.
What we connect the Astro site to
Framer hosted the site and its forms. These are the tools that replace that, and what passes along each wire.
A fast site with an easy editor still needs tracking, good content and a quick follow-up on every enquiry before it brings in customers.
GitHubHolds the code and the content. Every CMS save is a commit.
CloudflareServes the site from a Worker and stores the uploaded images.
n8nGets every form the site sends and follows it up.
WebflowWhat this site moved off. We still build client sites on it when the team wants to edit visually, and WordPress sites move to it or to Astro, whichever suits the site.
Who this is for
For you if
- You need full code control, and Framer can't give you the site as files to host yourself.
- Your developers want to work in code, including React, and keep content in Git.
- You want the developers moving your site to have moved a site into Astro themselves.
Not for you if
- You want to move onto Framer. We move teams off it, not onto it.
- Your team redesigns pages visually every week. A visual builder such as Webflow suits that better.
- You'd rather not look after hosting and the build. We'd tell you that too.
What changes when you move
Framer is a hosted visual builder. Astro is code you own and host where you choose.
| What matters |  Astro and KeystaticOur pick | Framer |
|---|---|---|
| Taking the site with you | Your content is already files in your own repo. | Published sites can't be exported as HTML for self-hosting. |
| Content | Files in your own Git repo, in Markdown, MDX or JSON, with a schema that catches missing fields. | Held in Framer's CMS. |
| Redirects | Permanent redirects from the host, each one tested before launch. | Set under Site Settings, Hosting, Redirects, and covering your own domain only. |
| Forms | Each form posts to your CRM or automation from the new site. | Rebuilt during the move. |
| React | Official integration renders React components. | Not covered by the help pages we checked. |
| Editing | Fields and blocks in Keystatic. A new section type needs a developer. | Visual canvas. |
Sources: Astro and Framer help pages, checked 22 October 2026. We don't quote prices: check their pricing pages.
What happens after you get in touch
Short call
You tell us who'll run the code, what Framer can't do for you now, and which pages bring in enquiries.
Crawl and list
We read the published Framer site and write down every page, CMS item, form, redirect and tag, so nothing hides in the rebuild.
Write the plan
You get the schema, the redirect approach, where it's hosted, who looks after the build and a timeline in writing, before we start.
Build and compare
We build the Astro site and check each page against the Framer one, with redirects tested before launch.
Launch and watch
Permanent redirects are served from the host, the sitemap is sent, and Search Console and your leads are checked daily for two weeks.
Work we can show you
In October 2026 we rebuilt our own site in Astro, and every live URL was checked against the new build before cutover. The same redirects and checks apply to yours.
372
addresses on our old site checked against the new build
113
redirects from old addresses to their new pages
Pacing's own move from Webflow to Astro, live 13 October 2026, not a Framer move.
Questions people ask before booking
Straight answers, so you know what to expect.
Still have a question?
Book a callWhat platforms do you use for website development?
We pick the platform for the site, not the other way round. Webflow suits a site your team edits itself, Astro with Keystatic suits a site that needs custom code (our own site runs on it), and for shops we use Shopify (we've built a custom Webflow storefront on Shopify).
We don't build or maintain WordPress. If you're on it, we'll move you to Webflow or Astro, whichever suits the site.
Should I move my Framer site to Astro?
Yes if you need the published site as files you can host yourself, which Framer doesn't offer. If your team redesigns pages visually every week, a visual builder fits better.
Can we export our site from Framer?
Not as files you can host yourself. Framer says it offers no HTML export, so we rebuild from your live pages.
Can we use React or Next.js?
Astro renders React components through its official integration, so interactive parts can be React and the rest stays plain HTML. If your project needs a full Next.js application, tell us on the call and we'll say whether Astro is the right fit.
Will we lose our Google rankings?
We can't promise that, and nobody honest can. Google says to expect temporary fluctuation during a move. We keep slugs the same where we can, redirect the rest and check Search Console daily for two weeks.
Will the new site have a sitemap?
Yes. @astrojs/sitemap writes the sitemap files at build time, and it needs your site's address in the Astro config. Before launch we read it through for old addresses, then send it in Search Console.
Can our team still edit the site?
Yes. Keystatic gives each kind of page a form, and blocks can be put in order. Each save is a commit, and the site rebuilds. A brand-new kind of section needs a developer.
How long does it take?
A Framer to Astro migration used to take months. Now it can take weeks, or even days. The biggest factor is how quickly your team can review the work and give feedback. You'll see the timeline in the written plan before we start.
Tell us about your Framer site and who'll run the code.
How many pages and CMS items, what Framer can't do for you now, and whether your team works in React.
- You'll talk to Ben or Cam, the people who do the work.
- We'll reply within one working day.
Get a Framer to code plan
Send us your Framer site's address and tell us who'll run the code, and we'll say on the call whether Astro suits.
Full code control · Every Framer URL mapped · Hosted where you choose