Webflow User Accounts Sunset: Recovery After January 29, 2026

What happened on January 29, 2026

Webflow's official sunset article says User Accounts functionality became unavailable, its dedicated APIs and webhooks stopped, and no new or existing site could add it. This is a completed product change, not a forecast.

What was affected on unmigrated sites

• ✓
  Access to User Accounts and its data was lost because Webflow did not migrate it into the CMS.
• ✓
  User Accounts pages were converted to regular static pages.
• ✓
  Content gates were removed.
• ✓
  Members could no longer log in on published sites.
• ✓
  Integrations and workflows using the dedicated APIs or webhooks stopped working.

Note that User Accounts was not the only deprecation in this cycle. Webflow Logic, its native automation tool, was sunset on June 27, 2025, which broke lead routing, form notifications, CRM sync and content workflows built on it. If your site used both, you may be looking at two separate gaps rather than one, and they need separate inventories. We covered the wider pattern in why teams are leaving Webflow in 2026.

"Sites that missed the deadline are usually running all three failure modes at once, not one in isolation.

The three failure modes, in practice

Sites that did not migrate before the deadline are usually running all three of these at once rather than one in isolation. Recognising which you have determines what you can still recover.

One: login stopped working

Existing members can no longer sign in. Depending on how the site was built, the login route may error, redirect nowhere useful, or return a 404. Members who bookmarked the login URL get the same result, and password resets through the old flow produce nothing. This is the failure customers notice first and the one that generates support volume.

Two: member records were not carried over

Webflow did not migrate User Accounts records into the CMS. If nobody exported the member CSV before the sunset, that list no longer exists inside Webflow. Some businesses reconstruct it from Stripe customer records, an email platform sync, or a CRM that received data through webhooks before the cut-off. Whether that is possible for you is an evidence question, not a general one. Check each of those systems before assuming either recovery or total loss. This is the practical edge of the question we set out in do you actually own your website.

Three: gated pages became public

Pages previously restricted to members were converted to regular static pages. Paid content became openly readable, and any layout driven by logged-in member state either broke visually or rendered placeholder values. Worth auditing deliberately: this is the failure mode with the clearest commercial and, depending on what was gated, potentially contractual consequences.

Check subscription and customer harm separately

Webflow says paid subscriptions for Webflow Ecommerce customers remained available in Stripe and subscribers would continue to be charged. Do not assume every affected business uses that configuration or that chargebacks occurred. Check which subscriptions are still active and what each one entitles the customer to. Then check access, cancellations, refunds, support cases and customer communications in the actual systems rather than in the site's documentation.

• ✓
  List active Stripe products, prices, subscriptions and customer status.
• ✓
  Map each paid state to the access or entitlement the customer should receive.
• ✓
  Identify customers charged without working access and apply the business's legal and support process.
• ✓
  Write down what you tell customers about cancelling, refunds and the move itself.

Replacement option one: a Webflow ecosystem provider

Webflow recommended Outseta and Memberstack and pointed customers to its broader app ecosystem and certified partners. A managed provider can reduce custom identity engineering. Evaluate the current feature set, pricing, data processing, migration, Webflow integration, billing, portability, support and exit path. The historical transition discount is not a permanent price.

Replacement option two: another managed identity system

A dedicated identity or membership provider can support login, sessions, password reset, social sign-in, multifactor authentication and organization features. The website still needs authorization, entitlements, content gating, billing reconciliation, webhooks, consent, monitoring and support. Confirm which responsibilities belong to the vendor and which belong to the implementation team.

Replacement option three: custom application code

Custom does not mean building cryptography or authentication primitives from scratch. A typical implementation uses a maintained identity provider or library and customizes the application's authorization and business workflows. It creates more control and more responsibility. Require threat modeling, secure sessions, account recovery, rate limits, logging, privacy controls, dependency updates and incident ownership.

In practice that resolves to one of two shapes, and the question separating them is who stores the passwords. A hosted identity service, such as Clerk or Auth0, runs the user store, the sign-in screens and the recovery flows, and your application integrates against it; the trade is a per-user bill and another vendor roadmap to watch. A self-hosted library, such as Auth.js, keeps the user table in your own database, which removes the per-user cost and the external dependency and moves session security, account recovery and abuse handling onto your team. Neither is the safe default. Decide it from whether you want the user table inside your application or outside it, then check the exit path before you build against either. Our custom engineering service covers how that work is scoped and handed over.

Is a managed replacement a fix or a deferral?

Both, depending on what membership is worth to you. A managed provider fixes the outage now and moves the deprecation decision from Webflow's roadmap onto that provider's roadmap; it does not remove the decision. Webflow User Accounts was itself positioned as the durable answer when Webflow launched memberships. It ran roughly four years, and the mechanism that ended it, a vendor deciding a feature no longer fits its strategy, applies equally to whichever provider you move to next. If you are weighing the platform itself rather than just the membership layer, our Webflow versus custom website comparison and the breakdown of what Webflow costs over time both set out the trade-offs.

That is not an argument against managed providers. It is an argument for matching the decision to what membership actually is in your business:

• ✓
  If membership is a feature on your site, a managed provider is usually the right call. It is faster, cheaper to start, and the vendor carries the security and maintenance burden. Accept that you are renting, price it accordingly, and keep your data exportable.
• ✓
  If membership is the business, moving from one vendor's roadmap to another vendor's roadmap relocates the risk rather than removing it. Owning the authentication and entitlement layer means the only party who can deprecate it is you.
• ✓
  Either way, the second migration is harder than the first. By then you have member expectations, payment history and integrations to carry across, so the exit path matters more than the entry discount.

Build a like-for-like requirement matrix

What happened to the pages themselves, and how to redirect them

The redirect question follows immediately, because /log-inand /sign-up were real URLs that people had bookmarked and that other sites had linked. The same Webflow article documents 301 redirects under Site settings, Publishing, 301 redirects, and it carries one trap worth knowing before you sit down to do it: you must put a percent symbol before the hyphen when entering the old path, or the redirect errors and is not added. That single character is why a batch of these silently fails to save.

Recovery playbook for an affected site

1. Freeze destructive changes and capture the current site and account state.
2. Inventory broken login, gated routes, API calls, webhooks and customer journeys.
3. Collect lawful exports and records from prior CSV files, CRM, email, Stripe, backups and integrations.
4. Reconcile identities with subscriptions and entitlements without guessing matches.
5. Choose a target only after documenting requirements, data roles and operating ownership.
6. Design customer communication, support, refund and account-recovery procedures.
7. Build and test identity, authorization, billing, data and error states in a non-production environment.
8. Map or redirect former sign-up, login and account URLs and verify search behavior. See what happens to your rankings when you migrate for the checks that matter here.
9. Cut over with monitoring, rollback criteria and named incident owners.
10. Retain evidence, delete unnecessary data and close obsolete credentials and integrations.

There is no standard recovery duration. Scope yours from data availability, user count, billing, workflows, security, review and the selected provider, then commit to dates once those are known. For how we phase a build once scope is settled, see how long a custom website takes to build.

How much does replacement cost?

Price the identity and business system, not only the sign-in screen. Include discovery, data recovery, migration, UI, authorization, billing, consent, security, testing, customer communication, cutover, provider fees and ongoing support. PandaCodeGen's planning tiers start at $1,500 Starter, $3,500 Growth and $5,000 to $10,000 Scale, but membership and billing complexity can require custom scope. The full tier detail sits on the pricing page, and our Webflow migration cost breakdown works through what changes the scope on a Webflow move specifically.

PandaCodeGen terms that must be written into the project

• ✓
  30 percent at onboarding and 70 percent on delivery under the signed agreement.
• ✓
  Refund for failure to deliver the signed scope, not a post-start change of preference.
• ✓
  15 business days of launch defect support on Starter and 30 on Growth or Scale.
• ✓
  Custom-deliverable transfer after full payment; client content remains the client's.
• ✓
  Reusable PandaCodeGen tools and pre-existing code remain PandaCodeGen property; third-party licenses apply.

The broader lesson

The sunsets did not stop with User Accounts. Webflow's feature sunsets page lists the legacy Editor and legacy Editor whitelabeling as unavailable from August 4, 2026, with migration to client and limited seats beginning May 4, 2026 and migrated users assigned the Content editor role. That is a third dated removal on the same page as Logic and User Accounts, and it is worth checking whether it touches how your clients edit content.

Any managed feature or provider can change. Custom systems also change through libraries, infrastructure and maintainers. The durable control is an exit plan: documented accounts, exportable data, standard protocols, dependency ownership, current runbooks and a tested recovery path. That is the principle behind our Webflow migration service, and you can see how it plays out on live builds in our client work.

Frequently asked questions

Primary sources

• Webflow User Accounts sunset
• Webflow deprecation announcement
• Webflow import and export user accounts
• Webflow feature sunsets and deprecations
• Webflow Logic sunset
• Webflow code export limitations