Next.js to Framer: migration check
Yes for the marketing site; keep the app in Next.js and move the pages that change weekly.
What maps where
TodayIn FramerFit
- MDX or headless CMS contentFramer CMS collectionsNative
- Contact and signup formsFramer FormsNative
- next/image optimizationFramer's built-in image handlingNative
- i18n routingLocalization (Pro plan)Native
- React componentsCode componentsCode component
- Framer Motion animationsEffects and code componentsCode component
- API routesExternal services or keep a small APIExternal
- Auth and dashboardsKeep in Next.js; link outExternal
Where it gets tricky
- Framer wants the whole domain. There is no supported way to run it under a subpath behind your existing app; the working pattern is www on Framer with the app on a subdomain.
- Marketing pages import the app's shared components and design tokens. The move recreates those in Framer, and someone has to own keeping the two in sync afterwards.
- Redirects, sitemaps, and OG images currently live in code (next.config, route handlers). Each needs a home in Framer's settings before the old repo stops deploying.
Questions that come up
Why would a developer team move a Next.js site to Framer?
So shipping a landing page stops requiring a deploy. If the site is marketing-only, everything moves and non-developers edit safely. If there is a product behind login, the app stays in Next.js and only the pages that change weekly move.
What happens to our React components?
The reusable ones translate well. Framer code components are React, so brand-critical pieces port with light edits; layout components usually dissolve into Framer's own layout tools instead.
Do we keep our URLs and SEO setup?
Yes. Paths stay identical, 301 redirects cover anything restructured, and metadata moves into Framer's SEO settings. next/image and i18n routing both have direct equivalents, so nothing user-visible regresses.
From the design gallery
See all
