Webflow was right for the first year. You've outgrown it.
Next.js rebuild with a marketing-friendly CMS (Sanity, Contentful) that handles what Webflow cannot — dynamic states, item caps, real interactions.
Who this is for
Marketing lead or technical founder hitting Webflow's limits — CMS item cap exceeded, Collection Pages can't handle the dynamic features you need, designer can't ship the complex states product demands.
The pain today
- Webflow CMS item cap (10k on CMS plan, 20k on Business) about to hit
- Complex filtering, search, or dynamic UI that Webflow can't express
- Third-party embeds slowing the site, no way to deduplicate
- Designer-developer handoff breaking because Webflow isn't a real code export
- Webflow bills approaching $500+/month and rising with traffic
The outcome you get
- Next.js 16 rebuild preserving URL structure and SEO equity
- Headless CMS (Sanity, Contentful) with editor UX as friendly as Webflow
- Real dynamic features — search, filters, personalization — without plugin gymnastics
- Better Core Web Vitals than Webflow's template output typically allows
- Predictable infra cost — Vercel + CMS, no per-CMS-item or per-visitor pricing
Where Webflow stops scaling
Webflow is genuinely great for 0–12 months of a company. Designer-friendly, fast to ship, decent CMS for simple content. Where it breaks: CMS item cap (sites with product catalogs or article archives hit the ceiling), complex dynamic UI (multi-level filters, personalized content, real-time states), performance on content-heavy pages (Webflow's output bundles more than it needs), and cost at scale (enterprise plan jumps, plus add-ons for memberships and logic). Teams typically notice around year two when either item cap, performance, or cost crosses the 'we need to migrate' threshold. Migrating sooner is easier; migrating after hitting the item cap means firefighting, not planning.
Next.js + headless CMS as the upgrade path
The upgrade is a Next.js frontend plus a headless CMS (Sanity, Contentful, or Strapi depending on team fit). Next.js gives you actual components, real dynamic rendering, edge caching, and a much tighter bundle than Webflow's runtime. The CMS gives editors a familiar structured-content experience. Sanity in particular has a live preview and real-time editing feel comparable to Webflow for marketing teams. The migration preserves URLs, content structure, and design direction — it's not a rebrand, it's a re-platform. The team keeps shipping; the ceiling disappears.
Keeping the editing UX marketing-team-friendly
The worry I hear: 'If we leave Webflow, editors have to learn code.' Not true with the right CMS. Sanity Studio has block-based editing, preview URLs, image editing, and a real-time editor feel. Contentful is more structured (closer to Notion's database feel) and scales better for enterprise. Both handle images, links, and content reorganization without developer intervention. The setup I deliver includes schemas tuned to your actual content types (not generic 'Page' with a free-form rich text field), so editors land in a workflow that feels obvious. A 30-minute handover call plus a one-page CMS guide is usually all that's needed.
Case study: Imohub 120k+ items
Imohub is a Brazilian real estate portal with 120k+ active property records. Webflow's CMS would have been impossible — their item cap is 20k on the highest plan, and search + filtering at that scale isn't something Webflow can express. I built it on Next.js + Laravel + MongoDB + Meilisearch + AWS. Query response under 0.5 seconds. 70% infrastructure cost reduction compared to the legacy stack. Top 3 Google rankings. The same architecture — Next.js frontend, headless data, dedicated search layer — applies to Webflow migrations for content-heavy sites (article archives, directories, product catalogs) where Webflow would have capped out.
Migration path and pricing
Webflow-to-Next.js migrations fit the Websites Redesign tier at $4,000–$10,000 depending on page count, CMS complexity, and dynamic features. Standard marketing site (15–25 pages, blog CMS, forms): around $5,000. Content-heavy site (100+ CMS items, search, filters): around $10,000. Timeline: 3–5 weeks for marketing sites, 6–8 for content-heavy. I preserve URLs where possible, ship 301 redirects where not, verify schema and sitemap in Search Console, and stay engaged for 4 weeks post-launch monitoring ranking. 14-day money-back, 1-year bug warranty, Work Made for Hire. Your Webflow plan gets cancelled only after the new site has been stable for 30 days.
When to stay on Webflow
I'll talk teams out of this project when Webflow is still the right tool. Under 1,000 CMS items, under 50 pages, simple marketing needs, a designer comfortable shipping in Webflow Designer — stay. The rebuild pays for itself only when you're hitting actual limits (item cap, dynamic features, performance, cost). Shortcut: if your last 3 design requests involved 'is there a plugin that can do X' — probably time. If your team still ships features in Webflow without friction, not yet. The 14-day money-back exists partly so I can back out if the first two weeks make it clear Webflow was actually the right tool. Better to save you the migration than bill for the wrong answer.
Recent proof
A comparable engagement, delivered and documented.
Rebuilt a real estate portal at a fraction of the cost
Rebuilt Imóveis SC's real estate portal as ImoHub — a faster, more scalable successor — handling 120k+ properties with sub-second search and drastically reduced AWS costs.
Frequently asked questions
The questions prospects ask before they book.
- Will editors lose the visual editing experience?
- No — Sanity Studio has live preview, inline editing, and a feel comparable to Webflow's Editor mode for content work. You lose the ability to change layout from the editor (that's a feature, not a bug — layout changes happen in code), but content edits, image swaps, and reorganization stay visual.
- How do we migrate existing Webflow CMS content?
- Webflow's CMS exports to CSV. I write a one-time migration script that maps Webflow CMS fields to the new CMS schema and imports everything — including rich text, images, and relations. Large catalogs (10k+ items) run as a batch job. Manual cleanup is minimal.
- What about Webflow's SEO tools?
- Next.js with a headless CMS gives you more SEO control than Webflow — custom schema per content type, sitemap scoped by locale, canonical tags per page, meta tag inheritance. I verify everything in Search Console before DNS flip, so the migration preserves ranking, not just URLs.
- Can I still use Webflow's design system (Client-First, etc)?
- Design direction carries over. The CSS architecture moves from Webflow's class system to Tailwind CSS, which plays nicely with modern Next.js. The visual result is identical or better; the underlying implementation is cleaner and more maintainable.
- What about Webflow Ecommerce?
- Webflow Ecommerce is weaker than Shopify for stores above ~$100k/year. If you're on Webflow Ecommerce, migration typically moves to Shopify for the storefront and Next.js for marketing content, bridged through Shopify's Storefront API. That's scoped as a separate engagement involving the Shopify customization service.
Ready to start?
Tell me what you need in 60 seconds. Tailored proposal in your inbox within 6 hours.