Published output hides the component system
Rendered HTML, CSS, JavaScript, and assets show the finished page. The reusable React components, design tokens, breakpoint rules, and editing guidance still need to be created for the new website.
Export Framer site designs into an owned Next.js website your team can update with Claude Code, Codex, or Cursor. Use the published site and CMS data as migration inputs, keep the visual details and key URLs, then launch from the Agentic Website Template with search and release checks already connected.
A Framer website combines the canvas with managed rendering, image optimization, font delivery, CMS Collections, forms, localization, redirects, and hosting. Moving to an editable Next.js website means giving each part a clear home in the new repository.
Use the templateRendered HTML, CSS, JavaScript, and assets show the finished page. The reusable React components, design tokens, breakpoint rules, and editing guidance still need to be created for the new website.
Plugins can move Collection data into CSV or JSON. The new site also needs fields, references, slugs, rich text, images, filters, localized routes, and a publishing workflow.
Forms, webhooks, redirects, custom fonts, analytics, code components, and Motion effects all need to be mapped, rebuilt, reconnected, and tested before the domain moves.
Use the Agentic Website Template as the new foundation. Your AI coding agent can study the published site, recreate its design in clean Next.js components, move the content, and connect the services your marketing team needs after launch.
See the three ways to use the templateKeep the Framer design
The site-clone workflow uses the live website as its visual reference. It captures detailed layouts, component states, responsive behavior, hover interactions, scroll effects, and page transitions for review.
Own the editing workflow
Brand voice, design rules, goals, examples, reusable components, and agent instructions live beside the code. Claude Code, Codex, or Cursor can use that context for the next page request.
Move CMS content
Map exported fields and items into a content model that supports dynamic routes, rich text, images, references, metadata, and internal links. The included blog provides a working publishing pattern.
Keep pages visible
The Next.js build renders important copy and links in HTML. Clear routes, metadata, canonical URLs, structured data, sitemaps, and direct redirects help search engines and AI systems understand the new site.
Reconnect and test
Reconnect form delivery, analytics, custom scripts, font files, and integrations. Then test routes, redirects, mobile layouts, motion, crawl access, and production settings before moving the domain.
Start with the published website and exported content. Let your coding agent build one complete page in the Agentic Website Template, review the result, and use the approved system for the rest of the site.
Start with the Agentic Website TemplateList every public URL and locale. Export CMS data, redirects, and available assets, then record important hover, scroll, and page transition effects.
Ask your coding agent to read README.md and AGENTS.md, then use the site-clone skill with the published Framer URL. Review the page at desktop, tablet, and mobile sizes.
Build the remaining routes and Collections, reconnect forms and analytics, add local font files, and recreate the interactions that matter to the experience.
Test every important URL, localized path, redirect, form, tracking event, animation, and search file in preview. Deploy the approved build and monitor the launch.
Layouts, responsive behavior, typography, interactions, and important Motion effects follow the Framer site your visitors already know.
Pages, CMS content, forms, scripts, fonts, redirects, localization, and search settings live in an owned Next.js project.
Your team can brief an AI coding agent, review a working change, and launch new pages with the same brand and release rules.
Straight answers for teams turning a published Framer website into an editable Next.js repository.
Framer's current HTML export guide says standalone HTML export for self-hosting is unavailable because published sites use managed rendering, image, font, caching, and delivery services. CMS plugins can export content as CSV or JSON. Use the live site and portable data as inputs for the Next.js migration.
Yes. Record each appear effect, hover or tap state, scroll transform, layout animation, marquee, and page transition. Recreate the important movement with React and Motion, then test reduced motion and mobile behavior.
Export the Collection fields and items, then rebuild their routes and publishing flow. Reconnect each form destination or webhook. Map every locale, translated path, language setting, and hreflang relationship before launch.
Any platform move can change search performance. Keep useful URLs, use direct permanent redirects for changed paths, preserve page meaning and metadata, render important content in HTML, update internal links, and monitor the new site after launch.