Migration
Framer to custom code
Framer exports no code, so pages and components are rebuilt. CMS content leaves through a plugin as CSV or JSON, and permanent redirects protect the traffic.
Trusted by teams from pre-seed to the S&P 100
What moves, and what gets rebuilt
Each part of the site, what it becomes, and whether it comes across, needs converting or is rebuilt.
FramerCollections with their fields and single or multi references, edited inside Framer
CMS contentNeeds convertingcustom codeCSV or JSON from an export plugin, loaded into a headless CMS or into files in the code
FramerPages, breakpoints and styles laid out on the Framer canvas
Pages and designRebuiltcustom codeRoutes and React components written by hand, with the live Framer site as the reference
FramerCanvas components with variants, and any React code components written in Framer
ComponentsRebuiltcustom codeComponents in the repository; code components are copied and adapted, the rest written again
FramerEffects, transitions and scroll animations set in Framer’s panels
AnimationsRebuiltcustom codeCSS or an animation library, written in code and checked against a recording of the old site
FramerFramer form blocks, some posting each submission to a webhook as JSON
FormsRebuiltcustom codeForms that post to a Server Action or a form service, sending to the same destinations
FramerPage and CMS paths, plus redirects kept in Site Settings, Hosting
URLs and redirectsNeeds convertingcustom codeThe same paths as routes, and a permanent redirect in next.config for each one that changes
FramerTitles and descriptions per page, with the sitemap and canonical tags filled in by Framer
Search settingsNeeds convertingcustom codeMetadata on each route, a sitemap.ts, a robots.ts and canonical tags, all written in code
FramerYour domain, registered wherever it is and connected to Framer’s hosting
DomainComes acrosscustom codeThe same domain, pointed at the new host on launch day
Moving from Framer to custom code, step by step
What Framer lets out, where the CMS content goes, what replaces its animations, forms and hosting, the redirects, the checks, and who should stay.
Why teams move from Framer to custom code
On this page, custom code is a site your developers write and maintain in a framework such as Next.js or Nuxt. Its source sits in your own repository, and you pick where it is hosted.
Most teams make this move when the launch site has turned into part of the product. The product team wants the marketing pages to use its components, its sign-in or its live pricing. Or the site needs logic Framer has nowhere to hold: a calculator that calls your API, pages generated from product data, content that depends on who is signed in.
The other reason is ownership. Framer’s help centre says that if you need to export source code, Framer may not be the right solution. An engineering team that reviews every change in pull requests usually wants the website in the same workflow as everything else it ships.
Some reasons do not stand up. Framer renders every page to HTML on its servers before serving it, so crawlers already get the full text, and a rewrite will not fix indexing by itself. A slow page is more often a heavy video or an oversized image, which can be fixed in Framer. And if designers and marketers are the ones changing the site every week, code takes their tool away unless a CMS is planned for them from the first day.
What Framer lets out, and in what form
Many people searching for this move hope for a button that converts the project to React. We did not find one in Framer’s help centre or developer documentation. Framer’s article on exporting says it does not provide a way to export published sites as HTML files or static bundles, because a published site relies on Framer’s backend services. A second article, written about porting your data, says every site is published as HTML, CSS, JavaScript and assets that you can download and host anywhere. It does not say how. Either way, a published page is built output, and developers cannot pick it up and carry on working in it the way they would with source code.
Framer’s marketplace lists third-party plugins that offer to export selected components as React files. Framer’s help does not document them and we have not tested their output. A generated file can help a developer see how a tricky layout was put together. Plan the build as though no page or component comes across.
Code components are the exception. If someone wrote React code components inside Framer, using its code editor, that code is yours. Copy each one into the repository. They were written to run on Framer’s canvas, so expect changes before they work in the new site.
The CMS content is the part that leaves in bulk. Framer says it exports through plugins, as CSV or JSON, and it has no export button of its own. Run one export for each Collection and keep the files. Collect the brand files separately: the logo, the favicon, original images at full size and any fonts, with their licences checked for use on a self-hosted site.
Where Framer’s CMS content goes
Framer’s CMS holds Collections, each with its own fields, and items can point to other items through single or multi references. Next.js has no CMS, so first decide where the content will live. There are three usual homes:
- Files in the repository, such as Markdown or TypeScript, changed by developers. It suits content that changes once a month or less.
- A headless CMS, which gives editors a web interface and gives the site an API to read from. Choose it before you export, because its field types decide the conversion.
- Your product’s database, for content the product already holds, such as integrations, templates or plan features.
Then map each Collection field by field:
- Each Collection becomes a content type in the CMS, or a folder of files, with one route template such as app/blog/[slug]/page.tsx.
- Plain text, numbers, dates, links and toggles map one to one.
- Formatted text needs a decision. Open the export and see what the plugin wrote for it, then convert it to the CMS’s rich text or to Markdown. Check headings, links and inline images on five items before you run the rest.
- Images come out as addresses. Download every file, store it with the new site and rewrite the addresses, so nothing still loads from Framer once the plan is cancelled.
- References become references in the CMS, or IDs in your files. Load the Collection being pointed to first, such as Authors before Posts.
- Slugs are copied exactly, because they become the URLs.
What replaces Framer’s animations, forms and hosting
Framer bundles several jobs into the one tool. On a coded site each one is chosen and built:
- Animations. Effects, transitions and scroll animations stay behind with the canvas. Screen-record each one on the live Framer site before anything else, because the recording is the only specification you will have. Rebuild them in CSS where you can and with an animation library where they need sequencing, and turn them off for visitors who ask for reduced motion.
- Forms. A Framer form can post each submission to a webhook as JSON, signed with a Framer-Signature header. In Next.js a form posts to a Server Action, which runs on the server, receives the form data and sends it on. Point it at the same CRM or inbox, validate every field on the server and add spam protection.
- Localisation. Framer’s is an add-on bought per locale. Next.js puts the locale in the path through an app/[lang] folder and leaves translation to you, in dictionary files or a library. Check whether your export plugin carries each locale’s text or only the default, and read each locale’s addresses from the sitemap so they can be kept.
- Hosting. Framer runs the site on AWS behind a global network, renews certificates and keeps a version for every publish. On Vercel, which hosts this site, a certificate is issued when you add the domain and a bad release can be rolled back, while the application, its data and the source code are yours to look after. Next.js can also run on your own Node.js server or in a Docker container.
- Editing. In Framer, someone with content permission changes text, images and CMS items on the live page. In code, editing is whatever your developers build. This site is custom code, Nuxt on Vercel with its content in the code and no CMS, so a developer makes every change. A marketing team needs a CMS in place before launch.
- Upgrades. Frameworks publish end dates. Next.js 15 gets security releases until 31 January 2027, and Nuxt 3 stopped getting them on 31 July 2026. Name the person who plans the upgrades.
The order of work
We work through the move in this order. It holds whether we run it or your own developers do:
- Inventory. Take every address from Framer’s sitemap at /sitemap.xml on your domain, add the redirects already set in Site Settings, Hosting, and mark the pages that bring in visits or links in analytics and Search Console.
- Redirect map. In a spreadsheet, write the new path beside each old one. Keep paths the same wherever you can, so most rows need nothing.
- Content model. Choose where the content lives, define its types and fields, and load a test export of ten items from each Collection.
- Rebuild. Write the shared layout, header and footer first, then each page type and its components, from the Framer design and the animation recordings, on a preview deployment.
- Content. Export every Collection, load them in reference order, move the images and paste in the copy from the static pages.
- Checks. Set metadata, the canonical base, the sitemap and robots.txt, then test forms, internal links and indexability on the preview.
- Launch. Add the redirects to next.config, point the domain at the new host, request every row of the map on the live site and submit the new sitemap in Search Console.
- Watch. Read Search Console’s not found report and the traffic to the old top pages for weeks, add redirects for anything the map missed, and keep the Framer project until you are sure, as the record of how every page looked.
Keeping URLs, redirects and search
A coded site can answer at any path, so you can usually keep every Framer address. Build /about at /about and each CMS page in the same folder with the same slug, such as /blog/post-name, and those rows of the map need no redirect. Change an address only when there is a reason, such as merging two thin pages.
Where a path does change, add it to redirects in next.config. With permanent set to true, Next.js answers with a 308, which its documentation says tells clients and search engines to cache the redirect forever. If an older client needs a 301, a statusCode property can take the place of permanent. A source of /old-blog/:slug covers one level of a folder and /old-blog/:slug* covers everything under it, and query strings are passed through. Next.js checks redirects before it looks for a page, so an old rule left in the file overrides a page you have since built at that path. Vercel caps the config file at 1,024 redirects. Past that it offers bulk redirects on its paid plans.
Copy Framer’s own redirects into the map as well. They live in Site Settings, Hosting, and they stop applying once the domain points somewhere else.
Framer generated the sitemap and took the canonical tags from the connected domain. In Next.js each is written: a sitemap.ts listing every route, with language alternates if the site is localised, a robots.ts, and alternates.canonical in each route’s metadata, with metadataBase set in the root layout. Carry the titles and descriptions across from Framer’s page settings and CMS fields, and any JSON-LD from Framer’s custom code into a script tag in the page. Framer also served each page as Markdown to AI agents that asked for it, and that stops unless you build it.
We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links. We also monitor after launch. These steps manage migration risk; they cannot guarantee that rankings will stay unchanged. Expect some movement while Google recrawls the new site.
When this site’s addresses changed, we mapped each old address by hand to the page that replaced it, used permanent redirects and wrote no wildcard rule. Pages with no replacement return a 404 instead of sending people to the homepage.
Checks before the domain moves
Run these on the preview deployment, and the redirect checks again once the domain points at the new host:
- Each content type holds as many items as its Framer export has rows.
- Five items of each type open with their body, images and references intact.
- A search of the built pages for “framer” finds no image, video, font or script still loading from Framer.
- Every page has its own title and description.
- The canonical tag on every page shows the live domain, with https and the right choice of www.
- The sitemap lists every page that should be indexed and none of the old addresses.
- robots.txt allows crawling, and no page still carries a noindex left over from the preview.
- Every row of the redirect map returns a 308 or 301 and lands on the right page in one hop.
- Each form has delivered a test entry to its destination, and the Framer form’s webhook is switched off at launch.
- Each animation matches its recording, and stops when reduced motion is turned on.
- Each locale answers at its old address and links to the others with hreflang tags.
- Analytics and tag scripts are recording visits on the new site.
When to stay on Framer
For plenty of startups Framer is still the right tool. Stay if:
- The site is pages and a blog, and nothing on it needs to share code, logins or data with the product.
- Designers and marketers make the changes every week, and nobody has budgeted for a CMS or the developer time to set it up.
- No developer will be around after launch. A coded site needs one for every change outside the CMS and for each framework upgrade.
- Your engineers are needed on the product. A rebuilt marketing site takes weeks of their time, then some of it every month after.
- The complaint is a slow page or a tired design. Both can be fixed inside Framer for much less than a rebuild.
- You want to own the code in principle, and nothing on the roadmap needs it. Owning it also means paying for its hosting and its upgrades.
- The site has grown a large content operation and no product features. Webflow, which is built around structured content, may suit it better.
What decides the time and the cost
Every page and component is written again, so the number of distinct layouts and components sets most of the time. A home page, a pricing page, a blog template and five landing pages built from shared sections are much quicker than ten pages that each have their own layout and animation.
The content comes next: how many Collections, how clean the formatted text is, how many images there are to move and how many locales. Then the work around the site, such as forms that feed a CRM, the CMS and its editing screens, and anything the site reads from the product.
We price a migration as a website project. Our websites start from $15,000 and most take four to eight weeks. The page system, content work, integrations, publishing requirements and migration complexity set the scope, and we agree it and the price before work starts.
If your own developers do the move, the costs are their time, the host, any CMS and its seats, and the Framer plan kept running until the new site is checked.
Vendor details were checked against the documentation of Framer, Next.js and Vercel on 15 November 2026. Framer’s own articles disagree about exporting a site, and all three change their features, so read their pages before you start.
Moving from Framer?
Short answers, from the guide above.
Not with anything Framer documents. Framer’s help centre says it does not export published sites as HTML or static bundles, and that it may not suit teams who need to export source code. Third-party plugins in its marketplace offer to export components as React files. The pages themselves are rebuilt by hand in Next.js. CMS content does come out, through plugins, as CSV or JSON.
No one can promise where each page settles. We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links. We also monitor after launch. In Next.js that means keeping Framer’s paths where you can, a permanent redirect for each one that changes, and a sitemap and canonical tags written in code. Expect some movement for a few weeks while Google recrawls the new site.
Most of our website builds take four to eight weeks, and we scope a migration as a website project. Every page and component is written again, so the number of distinct layouts and animations decides more than the number of pages. Many CMS Collections, several locales, a CMS set up for editors and forms that feed a CRM each add time.
Through a plugin. Framer documents CMS export as plugins that write CSV or JSON, with no export button of its own. Export each Collection, check how the plugin writes formatted text and images, and download every image so nothing loads from Framer after you cancel. The content then goes into a headless CMS, into files in the code, or into your product’s database.
Whoever your developers set it up for. Next.js has no CMS or editor roles of its own. Connect a headless CMS and marketers edit there, in the fields and screens your developers build. Without one, every change is a code change. Framer’s on-page editing, where content editors change text and images on the live page, has no direct equivalent, so plan the editing before the build.
Where to go next
- Framer vs Custom codeFramer for a fast, polished launch site that designers build and marketers edit. Custom code when the site has to behave like part of the product.
- WordPress to custom codeContent stays in WordPress behind the new site or leaves as XML or JSON. Design and plugins are rebuilt in code, and a redirect map protects search.
- Webflow to custom codePages are written again as components, CMS content leaves as CSV or through Webflow’s API, and a permanent redirect for each changed URL protects search.
Planning this move?
Tell us where it is now and where it is going. We’ll say what we’d keep, what we’d rebuild and how long it takes.
Most teams start with a call, then a sprint or an audit.
The people you’d work with, from the first call to launch