The Framer migration checklist: what to list before you leave
Benjamin Libor7 min read
Before you move a website from Framer to custom code, list everything the site is made of: every page and its URL, every CMS collection and field, every form and where it sends data, every script and integration, the languages, and who edits what today. That inventory is the difference between a migration that takes the time you planned and one that keeps finding surprises after launch. It also gives whoever rebuilds the site, a developer, a studio or an AI tool, a complete brief.
In short
- Framer has no built-in export of a published site to code, so a move is a rebuild, and a rebuild is only as complete as its inventory.
- List pages, CMS collections, components, forms, scripts, integrations, languages, domains and people before anything is built.
- Mark each item keep, change or drop; a migration is the cheapest moment to remove what nobody uses.
- Record what search engines and AI answers rely on today, so you can protect it.
- Decide who owns the repository, the hosting account and the domain before launch, not after.
Why make an inventory at all?
A Framer site hides a lot of decisions inside the editor: a form that posts to a CRM, a script added two years ago for a campaign, a collection used by one page nobody links to. None of these show up when you look at the site, and all of them have to be rebuilt, replaced or dropped on purpose.
The inventory also makes the work estimable. "Rebuild the website" can mean three weeks or three months. "Rebuild 24 pages, 4 collections with 180 items, 3 forms and 2 languages" is something a studio can price and an AI tool can work through, page by page.
Do it in a shared spreadsheet with one tab per section below. Each row gets three columns at the end: keep, change or drop, an owner, and a note.
Pages and URLs
Start with the addresses, because everything else hangs off them.
- Every static page, with its URL, title and the template or layout it uses.
- Pages that exist but aren't in the navigation: landing pages, thank-you pages, legal pages, old campaign pages.
- Every redirect already set up in Framer.
- The 404 page and any password-protected pages.
Your domain's /sitemap.xml lists most published pages; Search Console's pages report finds the ones that get traffic but slipped out of the sitemap. This list becomes the redirect plan later, which is covered in how to leave Framer without losing SEO.
CMS collections and fields
For each collection, record:
- the name and the URL pattern of its item pages
- every field, its type (text, formatted text, image, link, date, option, reference) and whether it's translated
- the number of items, and how many are drafts
- where the collection is shown: its own pages, lists on other pages, or both
- references to other collections
Then export each collection as CSV from Framer. Keep the slug column: it's what keeps the item URLs the same on the new site. References between collections and formatted text with embedded images need the most care when they're turned into content files, so flag those rows.
Components and design system
A rebuild is a chance to tidy the design, but it starts from what exists.
- Design tokens: colours, type styles, spacing and breakpoints as they're set up in Framer.
- Components: buttons, cards, navigation, footer, section layouts. Note the ones used once and the ones used everywhere.
- Interactions: animations, scroll effects, hover states. Mark which ones matter; most sites need fewer than they have.
- Code components: any custom React components written for the Framer site. These often carry logic worth keeping.
- Fonts and their licences: a font licensed for use in Framer isn't automatically licensed for self-hosting.
This tab becomes the brief for the design system on the new site, which is what keeps an AI tool's pages on brand.
Forms, scripts and integrations
This is where most surprises live.
| Item | What to record |
|---|---|
| Forms | Fields, where submissions go (email, CRM, Zapier), spam protection, consent text |
| Analytics | Which tool, which events and conversions are tracked |
| Cookie banner | Tool, categories, which scripts wait for consent |
| Tag managers and pixels | Every tag, who added it, whether it's still used |
| Chat and scheduling widgets | Tool, which pages, who answers |
| Embeds | Videos, maps, social posts, third-party widgets |
| Search, gated content, sign-ins | How they work today and who uses them |
For each script, ask who still uses it. Scripts that nobody can name an owner for are the easiest wins: dropping them makes the new site faster.
Languages and domains
- Every language, its URL pattern (
/de/…, a subdomain, a separate domain) and how complete the translations are. - Which pages and collections are translated and which aren't.
- The primary domain, any secondary domains that redirect to it, and subdomains that point elsewhere.
- Where DNS is managed and who can log in.
Search and AI visibility
Record what the site earns today, so the move can protect it.
- The pages with the most search clicks, and the queries behind them, from Search Console.
- The pages that bring sign-ups, demo requests or other conversions, from analytics.
- The pages AI answers cite when buyers ask about your category. Ask ChatGPT, Perplexity and Google's AI Mode the questions your buyers ask and note your cited pages, or use the prompts you already track. Why some pages get cited and others don't is in how ChatGPT decides which pages to cite.
- Structured data that exists today, and where it's missing.
People, accounts and ownership
A code site belongs to whoever holds the accounts. Settle this on paper before launch.
- The repository: a GitHub organisation owned by the company, with at least two people who can administer it.
- Hosting: the hosting account (Cloudflare, for example) under the company, not a freelancer's personal account.
- The domain and DNS: same rule.
- Editors: who edits content today, who publishes, and who approves. On the new site these become roles: who may edit content, who may change SEO settings, who may publish.
- Design changes: who asks for them and who approves them, now that they're prompts to an AI tool rather than drags on a canvas.
Turning the list into a plan
With the inventory done, the plan almost writes itself.
- Drop everything marked drop, and tell its owner.
- Group what's left into the design system, page templates, content and integrations.
- Set up the repository, hosting and CMS first, so every page built after that has a preview link.
- Rebuild templates before pages, and pages before content, so content lands in finished templates.
- Move each CMS collection with its slugs, then check a sample of items against the old site.
- Rebuild forms and integrations, and test each with a real submission.
- Build the redirect file from the URL list, then launch.
The order of the build itself, and the checks on launch day, are in our Framer to custom code migration guide.
Questions people ask
What do I need to export from Framer before migrating?
Export each CMS collection as CSV, keep a copy of the sitemap, and save the list of redirects and the SEO settings for each page. Download the images and files you uploaded, and note any custom code. Framer doesn't export the site itself as a code project, so the pages are rebuilt from this material and the live site.
How long does a Framer migration take?
It depends on the inventory: the number of pages, collections, languages and integrations. With an AI tool doing most of the building, a typical marketing site takes weeks, not months. The inventory turns that guess into a real estimate.
Can I keep my Framer animations?
Most of them. Framer's interactions use its Motion library, which works in any React app, so effects that matter can be rebuilt as interactive parts of a code site. Many teams keep only a few and let the rest go, which also makes pages lighter.
Who should own the code after the move?
The company. Put the repository, the hosting account and the domain under company accounts with at least two administrators. The studio or freelancer who builds the site can be a member, not the owner.
Written by Benjamin Libor, founder, echo.
Something wrong or out of date? Write to hello@echo-aeo.com and we'll fix it.