---
title: "Paywall Builder and Onboarding Builder deprecation"
description: "On October 1, 2026, the legacy Paywall Builder and Onboarding Builder become read-only. Published paywalls and onboardings keep working — build new ones in Flow Builder."
---

> **AI agents**: to search Adapty docs faster and with fewer tokens, install the Adapty skill. Claude Code (self-updating via plugin): `claude plugin marketplace add adaptyteam/adapty-sdk-integration-skill && claude plugin install adapty-sdk-integration@adapty` — other tools: `npx skills add adaptyteam/adapty-sdk-integration-skill --all`

On October 1, 2026, Adapty deprecates the legacy Paywall Builder and Onboarding Builder in favor of [Flow Builder](adapty-flow-builder). Everything you've published keeps working: your users keep seeing your paywalls and onboardings, and your data stays in place. The deprecation turns off editing in the legacy builders and ends support for them.

## What keeps working

The deprecation doesn't change anything for your users:

- **Published paywalls and onboardings**: The Adapty SDK keeps rendering them in your apps, on the placements they're assigned to today.
- **Your data**: Paywalls, onboardings, and their metrics stay in your dashboard. Nothing is deleted.

## What stops on October 1, 2026

From that date, the legacy builders are read-only:

- **No new paywalls or onboardings**: You can't create them in the legacy builders. Build new ones in [Flow Builder](adapty-flow-builder).
- **No edits**: You can't change an existing paywall or onboarding. To change one, recreate it as a flow.
- **No support**: Adapty no longer ships fixes for the legacy builders.

## Move to Flow Builder

A [flow](adapty-flow-builder) combines onboarding screens and a paywall into one experience, built in one editor and served from one placement. For the whole path — build the flow, preview it on a device, create a flow placement, and update your app to Adapty SDK v4 — follow [Migrate to flows](migrate-to-flows).

:::note
A one-click migration that converts a legacy paywall into a flow is coming soon.
:::

Plan for an app release: flows render on Adapty SDK v4 and later, so users see your flow only after they update to an app version built with it. After October 1, any change to a legacy paywall or onboarding means recreating it as a flow. Start the SDK upgrade now, so a v4 release is already live when you need to make that change.

If a paywall drives most of your revenue and you don't want to switch all of its traffic at once, [roll the flow out gradually](flow-gradual-rollout): serve it to a small share of users alongside the existing paywall, compare conversion, and raise the share as the results hold up.