Flows → Conditional Flows: migration plan & timeline
Following the Orchestrations UI deprecation announced earlier this year, we are now taking the next step: all existing Flows will be migrated to Conditional Flows — Keboola's modern workflow engine with branching, retry and variables.
What's changing
Conditional Flows will become the only workflow system in Keboola. Legacy Flows will be migrated in three batches:
| Batch | Date | What happens |
|---|---|---|
| Batch 1 — Simple Flows | July 1, 2026 | Migration button available for eligible Flows. Try it out, preview the result, and migrate at your own pace. Automatic migration on August 1, 2026 for any remaining Flows in this batch. |
| Batch 2 — Standard Flows | October 1, 2026 | Second wave of Flows eligible for migration. Same process: self-serve first, then automatic. |
| Batch 3 — Complex Flows | March 1, 2027 | Final batch including Flows with advanced configurations. Manual guidance provided where needed. |
After each migration, both versions will be visible in your project - the new Conditional Flow will be active, and the original Flow will remain accessible but disabled (read-only), so you can compare and verify.
Why
Conditional Flows offer significant improvements over legacy Flows:
- Conditional branching — route your workflow based on task outcomes, variable values, or custom conditions
- Per-task retry & delay — automatically retry failed tasks with configurable strategies
- Computed variables — set variables dynamically from task results - more improvements coming soon
Maintaining two parallel systems also increases operational overhead and slows down feature development. Unifying on Conditional Flows lets us ship improvements faster.
What you need to do
Before July 1, 2026: Nothing. We'll identify which of your Flows are eligible for Batch 1 and notify you.
Starting July 1, 2026: You'll see a "Migrate to Conditional Flow" button on eligible Flow pages. Click it to preview the migration result and confirm. If you don't migrate manually, eligible Flows in Batch 1 will be migrated automatically on August 1, 2026.
After migration: Review your new Conditional Flow. The original Flow remains visible (disabled) for comparison. Schedules, triggers, and notifications are updated automatically.
Rollback
If anything looks wrong after migration, you'll be able to roll back to the original Flow. Details on the rollback window will be shared before Batch 1 goes live.
Questions or concerns?
Reach out to your Account Manager or contact support. We'll share a detailed migration guide and FAQ before the July 1 launch.
This is the first in a series of updates. We'll post progress updates as each batch approaches.