From Framer to Astro: when the site outgrows the tool.
Moving from Framer to Astro pays off once the content archive grows, content belongs in version control or server-side logic arrives. This page covers the process and what happens to your animations.
A rebuild, no import
Astro documents migration guides for several frameworks. Framer is absent from that list, so the design gets rebuilt.
Motion is curated
Every animation enters an inventory: keep, simplify or drop. We make no promise of pixel-identical reproduction.
Measured, not claimed
Core Web Vitals before and after the move, using your own field data from your own project.
Our own products, live in the browser.
Screenshots from Mini Marvin, our own progressive web app running in the browser.
Swipe baby names instead of scrolling
Mini Marvin is our progressive web app for finding baby names: swipe through 10,000+ first names right in the browser, no app store needed.
Framer to Astro in four points.
Framer is a good tool
- For a design-led site with a manageable amount of content, maintained without a developer.
- The question is whether your site still fits that.
The move pays off
- When content volume grows, content belongs in version control, server-side logic arrives or several markets need localisation.
The path is a rebuild
- No import turns a Framer project into a maintainable Astro repository.
- Content and URL structure come across.
Afterwards
- Your content sits in content collections with a Zod schema or in a headless CMS, and can be edited by chat.
Is the move worth it for you?
Send us the URL of your Framer site and three sentences on the trigger: content volume, planned integrations, who maintains the site.
Move to Astro or stay on Framer.
We build with Astro and with Webflow. If your situation mostly sits on the right, we advise against the move.
Move to Astro when …
- The content archive grows. Categories, author profiles and years of posts outgrow a CMS designed for lean marketing sites.
- Content belongs in version control. With history, review before publishing and a one-command rollback.
- Server-side work arrives. Form logic, prices from another system, gated areas, personalised fragments.
- You need control over the markup. Structured data, image pipeline, script order and a performance budget someone enforces.
Stay on Framer when …
- The site is young and changes fundamentally every few weeks. At that stage design speed beats architecture.
- Motion is part of the brand. When movement carries the effect, the tool built for it earns its keep.
- Nobody on the team develops. A repository without people to maintain it is a new dependency.
- What you actually want is a redesign. A new look rarely needs a new stack.
How a move from Framer to Astro runs.
Five phases, each with a result you can check.
Inventory and decision
Pages, templates, CMS collections, forms, languages and a separate inventory of every animation.
Measure before the move
Lighthouse, Core Web Vitals from your field data, indexed URLs, positions and conversion numbers.
Define the content model
Which content becomes collections, which fields each schema needs, who maintains them.
Rebuild in Astro
Layouts, components, design tokens, image pipeline, routes. Motion returns along the inventory list.
Launch and re-measure
Redirects live, sitemap submitted, then indexing and positions watched for several weeks.
Frequently asked questions about moving from Framer to Astro.
Can you export a Framer project to Astro?
Never in a way that leaves a maintainable project behind. Astro documents migration guides for a range of frameworks; Framer is absent from that list. The design gets rebuilt as a component and token system, while content, metadata and URL structure come across.
Will our animations survive the move?
The load-bearing ones do, reimplemented. Astro handles page transitions with built-in view transitions, hover and state movement runs in CSS, and demanding effects become islands with their own load timing. We make no promise of pixel-identical reproduction.
Will we lose our rankings when we move from Framer to Astro?
Not when the move is planned. We pull every indexed URL beforehand, build a complete 301 list from it, keep titles and headings of the load-bearing pages stable, and watch indexing and positions for several weeks after go-live.
What does a Framer to Astro migration cost?
The range comes from the number of distinct page templates, the volume of content plus the CMS decision, and how much motion is meant to be rebuilt. After the first call you get an estimate with its assumptions, see Astro development cost.
How long does a Framer to Astro migration take?
A compact site of around ten pages: 3 to 5 weeks from a signed-off inventory. A grown site with an archive, a headless CMS and two languages: 6 to 10 weeks. Then 8 to 12 weeks of monitoring.
Can we still maintain content without a developer afterwards?
Yes. Through a headless CMS with edit forms, through Markdown in the repository, or by chat. We work AI-assisted and run a WhatsApp AI agent in daily business. Structural changes stay development work.
More from the Astro cluster.
Fundamentals, cost and running the site after the move:
Outgrown your Framer site? Let us talk.
Tell us briefly where it pinches: content volume, integrations, cost or performance. You get an assessment of effort and benefit.
Request a Framer to Astro migration.
The URL of the existing site, a rough page count and what prompted the change. Three sentences are enough for a first assessment.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.
Related reading.
Webflow to Astro
The other route design-led teams compare, with the same ifs and ands.
Learn moreAstro Migration
Every migration route at a glance: WordPress, Webflow, Framer and Next.js.
Learn moreEdit Your Website by Chat
What maintaining content looks like when nobody wants to open a CMS.
Learn moreIT Project Management
When the website move is one part of a larger programme.
Learn more