Automatic Migration of Legacy Flows to Conditional Flows
On October 12–13, we will automatically migrate all remaining Legacy Flows in Contracted Projects to Conditional Flows. No action is needed on your side.
As announced in our migration plan, Legacy Flows are being upgraded to Conditional Flows. The self-service window for Contracted Projects has now closed, and we will run the automatic migration on October 12–13, 2026.
What will happen
All Legacy Flows that haven't been migrated yet will be converted to Conditional Flows automatically. The migration keeps your setup intact:
- Schedules and triggers transfer automatically.
- Configuration ID stays the same; only the component ID changes.
- The original Flow is kept as a read-only reference.
- Rollback is available for 30 days after the migration, until November 12, 2026.
What you need to do
Nothing is required. If you prefer to migrate on your own terms, you can still do it before October 12 using the one-click migration described in the Migration Guide.
After the migration, we recommend:
- Checking that your key Flows ran as expected.
- Updating any external integrations or API calls that reference the Legacy Flow component ID (
keboola.orchestrator) to the Conditional Flow component ID (keboola.flow).
What you get with Conditional Flows
- Conditional branching: Route workflows based on task outcomes or variable values.
- Per-task retry: Automatically retry failed tasks with configurable delays.
- Computed variables: Set variables dynamically from task results and pass them between tasks.
- Better error handling: Continue on failure, stop immediately, or route to alternate paths.
Learn more about Conditional Flows.
Getting help
If you have any questions or run into issues after the migration, contact your Account Manager or reach out to support@keboola.com.
Thank you for your understanding and for being a valued part of the Keboola community.