By Mehdi HassanWhat replaces Webflow features after moving to Next.js?
Every Webflow feature that isn't a page needs a deliberate replacement in Next.js, because Next.js is a framework, not a platform. Forms, user accounts, ecommerce, site search, Logic workflows and hosting each become a separate tool or a piece of code you own. Most migration guides skip this list, and it's where budgets and timelines go wrong.
This map covers each feature, the usual replacement and what to watch for. It fits into the wider plan in our Webflow to Next.js migration guide.
Webflow feature | Common Next.js replacement | Watch for |
|---|---|---|
Forms | Server action posting to CRM or form service | Spam, notifications, UTM fields |
User accounts and gated content | Clerk, Auth.js, Supabase Auth or Payload auth | Password resets, roles, migrating users |
Ecommerce (small) | Stripe Checkout or Payment Links | Tax, receipts, inventory |
Ecommerce (catalog) | Shopify headless via the Storefront API | Cart, checkout domain, apps |
Site search | Algolia or a static index such as Pagefind | Indexing on publish |
Logic workflows | Server code, Zapier or n8n | Retries and error alerts |
Localization | Next.js i18n routing plus a CMS locale field | hreflang and URL structure |
Hosting and SSL | Vercel or Cloudflare | Preview deploys, caching |
How do you replace Webflow forms in NextJS?
Replace Webflow forms with a form component that posts to a Next.js server action or route handler, which validates the data, checks for spam and sends it on to your CRM. This is more work than Webflow's built-in forms, but it gives you full control over where submissions go and what happens next.
List every form
Record each form, its fields, where submissions go today and who gets notified. Webflow form settings and any Zapier zaps tell you this.
Pick the destination
Post to the CRM you already use, such as HubSpot or Salesforce, or to a form service. Store a copy in your CMS or database as a backup.
Build the server handler
Validate fields on the server with a schema library, reject bad input and return clear errors the form can show.
Add spam protection
Use a honeypot field plus a challenge such as Cloudflare Turnstile, verified on the server, not only in the browser.
Capture attribution
Pass UTM parameters, the page URL and the referrer as hidden fields so marketing keeps its source data.
Send notifications
Email the team and the submitter through a transactional email service, and alert someone if the CRM call fails.
If your forms collect health information, the rules change: you need a vendor that will sign a business associate agreement. We cover that in HIPAA compliant forms on Webflow, Framer and Next.js.
What replaces Webflow memberships and gated content?
Webflow's user accounts and gated content move to an authentication provider in Next.js. Hosted services such as Clerk handle sign-up, login, password resets and social logins for you. Libraries such as Auth.js keep users in your own database. If your CMS is Payload, its built-in auth can manage users and access rules in the same app.
Gating then happens in Next.js middleware or in the page itself: check the session, then show the content or redirect to login. Roles, such as free and paid members, become fields on the user record. The hard part is moving existing members. Passwords can't be exported in a usable form, so plan an email asking members to set a new password, or use magic-link login so nobody needs one.
When gated content doesn't need accounts at all
Many marketing sites use memberships only to gate a report or a webinar recording behind an email address. That doesn't need user accounts. A form that captures the email, adds the lead to the CRM and then emails a link to the resource does the same job with far less to maintain. Keep real authentication for cases where users return repeatedly to protected content, such as a customer portal or a paid course.
What replaces Webflow ecommerce after the move?
Webflow ecommerce is replaced by Stripe for a small number of products and by Shopify for a real catalog. The dividing line is inventory and operations: if you're selling a few plans, tickets or digital products, Stripe Checkout or Payment Links are enough. If you manage stock, variants, shipping and fulfillment, Shopify's back office is worth paying for.
- Stripe Checkout. Product pages live in your CMS, and the buy button opens a Stripe-hosted checkout. Tax and receipts are handled by Stripe settings.
- Shopify headless. Next.js renders product pages from the Shopify Storefront API, and the cart hands off to Shopify's checkout. Compare the options in Shopify Hydrogen vs Next.js.
- Shopify for the store, your site for the brand. Keep the store on Shopify and link to it from the marketing site. It's the simplest setup, and we compare it in Webflow vs Shopify.
Product URLs matter for SEO. Webflow product pages live under /product/, so either keep that path in Next.js or redirect every product URL to its new home.
What replaces Webflow site search, Logic and localization?
Site search, Logic and localization each have a straightforward replacement, but each one is easy to forget in a scope. Check whether your Webflow site uses them before anyone estimates the work.
- Site search. For a small site, a static search index built at deploy time is free and fast. For a large or frequently updated site, a hosted search service indexes content from the CMS on publish.
- Logic. Webflow Logic flows, such as routing a form to different teams, become a few lines in your server action or a workflow in Zapier or n8n. Code is easier to test; a workflow tool is easier for marketing to change.
- Localization. Next.js handles locale routing, and your CMS stores translations per field. Keep locale URLs identical to the old ones, or redirect them and update hreflang tags.
Does replacing these features change the cost of leaving Webflow?
Yes. Each replacement adds build time, and some add a monthly bill, such as an auth provider, a form service or a search index. Webflow's plan bundled them, so a fair cost comparison has to add them back in.
For most marketing sites the extra bills are small, because the only features needed are forms and hosting. Sites with memberships or ecommerce are different, and those features can cost more to rebuild than the pages. Factor them into your numbers using Webflow to Next.js migration cost, and if they tip the balance, read why companies leave Webflow and who shouldn't.
Which features should you replace first?
Replace forms first, because they carry revenue: demo requests and contact forms are usually the most valuable thing on a marketing site. Then hosting and redirects, then search and localization, and finally memberships and ecommerce, which deserve their own scoping.
If memberships or a large store are the reason your site is hard to move, consider separating them: keep the marketing pages in Next.js and run the store or member area as its own app. A cleaner split often costs less than rebuilding everything in one place. For a CMS that can store form submissions and manage users in the same app, see Webflow to Next.js and Payload CMS.
