Webflow Migrationto Next.js.
When Webflow is no longer enough (too many pages, several languages, fragile integrations, business logic it can't hold), we rebuild your site in Next.js: code you own, hosted where you choose, with the CMS that suits your team. Your design, content and traffic come with you.
In short
A Webflow to Next.js migration means rebuilding a Webflow site in code with Next.js, a widely used development framework for websites and applications. The design, content and URLs are carried over. What Webflow handled for you (hosting, CMS, forms) is replaced by building blocks chosen for your project. You win twice: the platform's limits go away (volume, languages, integrations, business logic) and you own code that any development team can pick up. Scroll, a Paris-based agency, made this journey for its own site: you benefit from that experience.
Keep, extend or rebuild?
Webflow remains an excellent tool for many marketing sites: we build and maintain them. Before recommending a rebuild, we answer three questions.
Keep Webflow
Showcase site with stable needs, a team that edits the design itself, limits mainly around content or SEO. An optimisation or a redesign within Webflow is enough.
Extend Webflow
The site works, but it needs to connect to a CRM, automate some flows or add a one-off feature. Integrations and automations around Webflow may be enough.
Rebuild in Next.js
The limits are structural: volume, languages, business logic, performance, platform dependency. A code rebuild creates a foundation you own.
When Webflow is no longer enough.
Leaving Webflow makes sense when the platform sets the project's limits instead of your needs. The most common signals:
Recognise several of these signs? The question becomes: what to rebuild, and in what order. That's exactly what our audit sets out.
The cutover checklist.
Changing technology changes how every page is produced and served. We're here to preserve your traffic: the cutover is prepared URL by URL, then monitored after launch.
What we keep, what we rebuild.
A rebuild isn't a code export. Webflow's export gives you HTML and CSS pages, useful as a reference, rarely as a base to build on. We decide page by page, component by component.
- The design that works
- URLs that matter
- High-performing content
- Useful metadata
- Images and media
- Animations that serve the message
- Key forms
- Analytics events
- Editorial autonomy
- Pages as reusable components
- Interactions and animations, in code
- The content model
- Forms and where they send data
- Integrations with your tools
- Languages
- Business logic
- Hosting
- Backups and monitoring
The right approach may be a full rebuild or, for a large site, a step-by-step rebuild.
From Webflow to Next.js.
The point isn't to copy pages, but to replace what the platform did for you with building blocks you control.
| Existing Webflow | Next.js destination |
|---|---|
| Designer pages | Reusable React components |
| Webflow interactions | Coded, lighter animations |
| CMS collections | Collections in the chosen CMS (Payload by default, or Directus) |
| Webflow Localization | Languages handled by the site, one URL per language |
| Webflow forms | Developed forms, sent to your tools |
| Webflow hosting | Hosting of your choice (OVH, Vercel, Scaleway…) |
| Scripts and embeds | Integrations kept, cleaned up or replaced |
| SEO settings | Metadata, sitemap and redirects handled in code |
Why Next.js after Webflow.
Next.js underpins almost all our projects, websites and applications alike. After a rebuild, your site can gain:
See our Next.js agencyA coded site needs hosting, backups and updates: we take care of it, or train your team if it prefers to stay in control.
What about the CMS?
Next.js displays the site; the CMS is where your team edits the content. We choose the one that suits your team with you.
Payload
The CMS installs inside the Next.js site: one project, an admin designed for your content. It's what we use for our own site and for our clients.
Directus
When the same data must feed both a website and an application, or your team needs a real data back-office, Directus is an excellent option.
No CMS
For a site of a few rarely updated pages, content can live in the code: lighter to maintain.
Six steps.
A dedicated team from scoping to delivery, with a dedicated project lead.
Site and limits audit
Pages, collections, interactions, forms, integrations, languages, SEO, performance, and what is really blocking you. Full inventory of URLs and their traffic.
Architecture & CMS choice
Site structure, content model, editing tool, integrations and hosting. What is kept, merged, deleted or redirected: every important URL gets a destination and a 301.
Design decision
What is kept from the existing design, cleaned up into reusable components or redesigned, based on your goals. Webflow animations are recoded, not copied.
Next.js development
Components, pages, forms, languages, business logic, integrations, technical SEO, tests and continuous integration.
Content transfer & 301s
Content retrieved through Webflow's API or by export, cleaned up, imported into the chosen CMS, then redirects put in place.
Launch & operations
Pre-production checks, cutover, then monitoring: 404s, indexing, Search Console, conversion. After that, hosting, backups, updates and monitoring are handled by us or by your team.
Our own exit from Webflow.
Our site used to run on Webflow. We rebuilt it in Next.js, with Payload as the CMS, and it has been live since 12 June 2026. We went through the cutover as a client would: what to carry over, what breaks, what to watch afterwards.
- Nearly 200 articles carried over from Webflow, in French and English
- A 301 redirect plan prepared before launch
- Pitfalls found and fixed : content stored outside the body text, invisible characters, tags served too late
- A site hosted on our own server, with encrypted off-server backups
Before / after.
What the rebuild changes in practice, topic by topic.
| Subject | Before: Webflow | After: Next.js |
|---|---|---|
| Code | At Webflow, exportable as static pages | In your repository, versioned and tested |
| Hosting | At Webflow only | With the host of your choice |
| Languages | Platform add-on | Built into the site, one URL per language |
| Integrations | Scripts and relay services | Built and connected to your tools |
| Business logic | Difficult, often worked around | Built for your needs |
| Performance | Dependent on the platform and scripts | Server rendering, controlled images and scripts |
| Operations | Handled by Webflow, on its terms | Handled by us, or by your team if you prefer |
| Switching providers | Tied to the platform | Any Next.js team can take over |
Our site, in figures.
The site you're browsing, rebuilt after Webflow. Figures as of 27 October 2026.
How long should you plan for?
The audit is what gives a reliable timeline. It depends on factors such as:
- Number of pages and URLs
- Number of CMS collections
- Content volume
- Keeping or redesigning the design and animations
- Multilingual support
- Integrations and business logic
- Choice of CMS
- SEO equity to protect
- Expected hosting and operations
Frequently asked questions
The questions that come up most often during scoping. If yours isn't listed, get in touch!
Is your Webflow site no longer enough?
Let's talk. We audit your site, tell you whether it's better to optimise, extend or rebuild it, and propose a Next.js rebuild plan with the CMS that suits your team and your traffic protected.
75011 Paris