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
- We lower DNS TTL a day ahead.
- The production build goes up with your domain attached.
- On a call with you, we change the DNS records from Framer to the new host. Email records are not touched.
- Once SSL is live, we test redirects, forms, analytics and the sitemap.
- We submit the new sitemap in Google Search Console.
- 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.






