We're sunsetting Tinybird Classic for Free and Developer plan workspaces. If you have an eligible Classic workspace, you need to migrate it to Tinybird Forward by September 15, 2026.
Forward is now the main Tinybird product experience. It is where we are focusing development, and 80% of Tinybird users are already there.
Classic was good at getting a real-time data project running quickly. Forward adds the workflows needed to change and operate the project over time: deployments, automatic schema migrations, local development, Cloud Branches, CI/CD, typed SDKs, Agent Skills, and unified logs.
Migrating before the deadline gives you time to test your project and choose when the change happens. It also qualifies you for an early-migration offer if you complete the move by August 15, 2026.
Who needs to migrate
This change applies to Tinybird Classic workspaces on Free and Developer plans.
It does not apply to Enterprise workspaces. If you received our email but primarily use Tinybird Enterprise, check whether you also have Free or Developer workspaces in another region or created for testing. Only those eligible workspaces need to be migrated or removed.
After September 15, any remaining eligible Classic workspaces will be scheduled for automatic migration. We will do our best to make that process smooth, but migrating yourself gives you more control over timing, validation, and any project-specific changes.
Before you migrate
Migration upgrades your existing workspace in place. Your tables and data stay in the workspace and are available in Forward after migration. Existing Endpoint URLs and supported tokens continue to work.
Forward does change how the project is developed, tested, and deployed. Review these differences before you start:
- Classic branches and Releases are deleted during migration.
- Include files need to be replaced with secrets or generic Pipes, depending on how you use them.
- Classic regression and data quality tests use a different model in Forward. Forward uses fixture tests.
- Resource-scoped tokens using
:sql_filterneed to be replaced with JWTs. - Existing Classic CI/CD scripts need to use the Forward CLI and deployment workflow.
Migration is permanent. After the first Forward deployment, you cannot switch the workspace back to Classic.
The Classic to Forward migration guide documents the compatibility checks and alternatives available in Forward.
How to migrate
The migration guide walks through the preparation and compatibility checks. Once the project is ready, the main migration flow is:
tb --cloud pull
tb migrate-to-forward
tb --cloud pull downloads the project as Forward-compatible datafiles. For connector-backed projects, it also creates connection files and secret references for you to review.
tb migrate-to-forward validates the project, removes Classic branches and Releases, runs a deployment check, creates the Forward project configuration, switches the workspace, and deploys it.
After it finishes:
- Query your main API Endpoints.
- Confirm that ingestion and connectors continue to receive data.
- Run your application against the existing Endpoint URLs and tokens.
- Commit the Forward project files and update CI/CD if you use it.
Follow the migration guide rather than treating these commands as a substitute for the preparation steps, especially if the project uses connectors, include files, Classic branches, custom tests, or CI/CD.
Migrate by August 15 and get a discount
As a thank you for migrating early, we are offering:
- Two months at 50% off your current paid plan.
- One month free if you are on the Free plan and upgrade to a paid plan.
Complete the migration by August 15, 2026, then email support@tinybird.co. We will share the coupon and help you apply it.
What you get in Tinybird Forward
Classic made it fast to start a real-time data project. Forward is built for what comes next: changing schemas, testing safely, reviewing changes in Git, and deploying without rebuilding resources by hand.
Deploy changes instead of rebuilding resources by hand
In Classic, a schema change could mean creating a new Data Source, reconnecting downstream resources, copying data, and coordinating the switch yourself. In Forward, change the project files and deploy:
tb deploy --check
tb deploy
Tinybird analyzes the dependency graph and creates a deployment plan. It handles the backfills and table exchanges required by the change. You can inspect the plan before applying it, and destructive operations require explicit confirmation.
The same deployment model covers Data Sources, Pipes, Materialized Views, API Endpoints, connections, and their dependencies. Read more about deployments and schema changes.
Develop locally or in an isolated Cloud Branch
Run the Tinybird runtime with Docker using Tinybird Local. You can load fixtures, build resources, execute tests, and call local API Endpoints before touching a shared workspace.
Create a Cloud Branch when you need production-like data, connector validation, or a shared environment for pull request review. Changes in the branch do not change production.
Forward branches are different from Classic branches. Classic branches are not migrated.
Put the data project in Git and CI/CD
Forward projects are files. Data Source schemas, SQL Pipes, API Endpoints, connections, tests, and secret references can live beside your application code and go through the same review process.
The Tinybird Local Docker image runs validation and tests in CI without a shared Cloud workspace. When changes need real data or connectors, CI can create an ephemeral Cloud Branch for the pull request. See the Forward CI/CD guide for GitHub Actions and GitLab CI examples.
Choose datafiles, TypeScript, or Python
Datafiles and SQL remain first-class in Forward. The redesigned tb CLI covers local development, Cloud Branches, tests, deployments, logs, connections, and secrets.
You can also define Data Sources, Pipes, Materialized Views, Endpoints, connections, and clients in the language your application already uses:
- The TypeScript SDK provides typed resource definitions, ingestion, and Endpoint clients.
- The Python SDK provides Python-native resource definitions and typed runtime methods.
Both SDK workflows generate the same Tinybird resources and support local builds, branches, deployment checks, and production deployments.
Give your coding agent Tinybird context
Tinybird Agent Skills package our project conventions, SQL guidance, schema design rules, deployment workflows, and testing practices for Amp, Claude Code, Codex, Cursor, and OpenCode.
npx skills add tinybirdco/tinybird-agent-skills
No Tinybird-specific agent required. Your agent works through the same CLI and SDK interfaces as the rest of your team.
Manage connectors and logs as part of the project
Forward supports Kafka, S3, GCS, and DynamoDB connectors. Connection definitions live in the project. Credentials are stored as environment-specific secrets rather than committed to Git.
Unified logs in the UI and CLI cover queries, ingestion, jobs, API Endpoints, and connector activity. See the connector migration guide and monitoring guides.
Migrate before September 15
The required migration deadline for eligible Free and Developer workspaces is September 15, 2026. Migrating now lets you review the generated project files, test the application, update CI/CD, and choose when the change happens.
If you are unsure which workspaces are affected or run into a migration issue, contact support@tinybird.co or ask in the Tinybird Slack community.