Framer to Next.js Migration Service, Backed by 3,411 Tracked Switches

Our packages price by page count: up to 100 pages $1,500–2,500, up to 1,000 pages $2,500–4,000, and $4,000–6,000 above that. Framer sites get a fixed quote after a short scoping call, because the effects and code components on a Framer site vary more than its page count does. You pay 50% to start and 50% when the site is live.

About one week for a small site (up to 100 pages), two to three weeks for a medium one (up to 1,000) and four to five weeks for a large one. Pages are counted from your sitemap, CMS items included. Heavy effects, localized pages or custom code components can add time; the timeline is fixed in the quote.

Rankings hold when URLs, content, titles and internal links survive the move. We keep URLs wherever Next.js allows, carry over the redirects you set up in Framer, 301 every URL that changes, carry over metadata and structured data, and check every old URL against the new site before launch. If search traffic drops after launch, we find and fix the cause at no extra cost.

Not by itself. In HTTP Archive's September 2026 report, 70.8% of Framer sites pass Core Web Vitals on mobile against 35.7% of Next.js sites, because Framer's hosting optimises pages for you and many Next.js sites are heavy apps. We keep pages static where we can, render components on the server and test every template on mobile before launch.

Not into a finished site. Framer has no built-in code export; marketplace plugins and converter services export the published site as files or chosen components as React code. What you get is Framer's generated output rather than components your team would write, and it doesn't move your CMS, redirects or forms into a working app. The calculator on this page is free: it counts your pages and CMS items from your sitemap.

Do it yourself if a React developer is on staff and the site is small with few effects: a rebuild costs only their time. Hire a team when nobody will look after React code, the site has hundreds of CMS items or heavy animation, or search traffic is too valuable to risk on a first attempt. Developer capacity decides it, not company size.

They are rebuilt in code. Appear effects, scroll animations, hover states and component variants are set up in Framer's editor, so we list every one before the build and recreate it with Motion, the open-source library that began as Framer Motion, or GSAP for longer timelines. Each one is checked against the live Framer site.

Framer's help centre says CMS content leaves through plugins as CSV or JSON. We export every collection that way and import it by script, so item count adds little to the cost. You choose where the content lives afterwards: Markdown files in the repository or a headless CMS.

Yes. Keep the marketing pages on Framer and put the Next.js app on a subdomain, or route a path to it through a proxy; Framer documents serving a site behind a reverse proxy. TechnologyChecker.io's crawl finds 3,946 domains running both. See the hybrid path above.

When designers own the site, publish without engineers and the site is a marketing site the builder handles without workarounds. Rebuilding that in Next.js is usually the wrong call. Sites move the other way too: TechnologyChecker.io's crawl counts 491 domains that went from Next.js to Framer since May 28, 2026, against 3,411 from Framer to Next.js.

Choose Astro for a content site with little interactivity: it ships less JavaScript by default. Choose Webflow if designers should keep a visual builder. Choose Next.js if engineering owns the site, the product already runs on React, or you want AI coding agents to make changes. Among domains that left Framer since May 28, 2026, TechnologyChecker.io's crawl finds 3,411 on Next.js, 1,041 on Astro, 421 on WordPress and 173 on Webflow.

Yes. Because the site is code in your repository, a coding agent such as Claude Code, Codex or Cursor can make any change you describe, from a new landing page to a redirect rule or a CMS field. It builds the site to check its work and opens a pull request with a preview link; you approve it before it goes live, and any change can be rolled back. We hand the repository over set up for this, with an AGENTS.md instructions file and documented components. Framer also has an MCP server, but an agent there works through the tools Framer exposes.

Mostly small software companies. TechnologyChecker.io matched 2,200 of the switching domains to a company: 1,607 have 1 to 10 employees and 470 have 11 to 50, and the largest industries are Software Development (413) and Technology, Information and Internet (296). The United States leads with 588.

TechnologyChecker's own engineers, not an automatic converter. People plan the build, write and review the code and check every page; AI coding agents take the repetitive work, which is why it's faster and cheaper than a traditional rebuild. We run the detection crawl behind the switching numbers on this page, and we deliver migrations ourselves rather than passing them to a partner.

From TechnologyChecker.io's own detection crawl of 29.9M live business domains, run every month. A domain counts as Framer when its pages load Framer's scripts or set Framer's JavaScript globals, and as switched when every Framer signal is gone from the hosts we track and it runs Next.js. Counts are domains, not companies, and each figure carries the date it was measured.

It reads your robots.txt and the sitemap Framer publishes, treats each top-level page as its own design, and treats any folder holding three or more pages (such as /blog/...) as one CMS collection. It loads a sample of pages to judge how heavy each design is. Pages missing from your sitemap aren't counted; we confirm the count on the scoping call.

Not with a built-in button. Framer's help centre says it offers no HTML export for self-hosting, because pre-rendering, image resizing and server-side rendering run on its own hosting. Marketplace plugins can export the published site as files or chosen components as React code, and CMS collections leave as CSV or JSON through plugins. None of these gives you a codebase to maintain, which is why a rebuild moves content by script and recreates components and effects in code.

For sites that engineers own, yes. TechnologyChecker.io's crawl finds Next.js on 731,970 live domains in August 2026, and it is the most common destination for sites leaving Framer: 3,411 domains since May 28, 2026. It is not faster by default: in HTTP Archive's September 2026 data, 35.7% of Next.js sites pass Core Web Vitals on mobile against 70.8% of Framer sites, so a migration has to be built and tested for speed.

For a content site with little interactivity, Astro is the main alternative: it ships far less JavaScript by default. Among sites that left Framer since May 28, 2026, TechnologyChecker.io's crawl finds 1,041 now on Astro against 3,411 on Next.js. Choose Next.js when the site shares a domain or code with a React app, or needs logged-in features.

It depends on who runs the site. For a designer-owned marketing site, Framer and Webflow are the closest choices. When engineers take it over, most sites that leave Framer go to code: since May 28, 2026, TechnologyChecker.io's crawl finds 3,411 former Framer domains on Next.js, 1,041 on Astro, 421 on WordPress and 173 on Webflow.

For a design-led marketing site that designers publish themselves, usually yes: G2 reviewers rate it 4.5 out of 5 from 156 reviews, with ease of use the most-mentioned strength (39 mentions) and high pricing a smaller complaint (9 mentions). The sums change when you add editors, locales and several sites, or when your product already runs on Next.js and the website could share its code.

Cancel the paid plans first. In workspace settings, open the Billing tab, click the three-dot menu next to each site and cancel its plan; editor seats end once the last site plan is cancelled, and plan benefits stay active until the end of the billing period. Then delete the account under Account settings, Profile. Do it after the new site is live, the redirects are checked and your CMS content is exported, so you can still roll back.