Best Practices for Upgrading to Kestra 2.0

​Kestra 2.0 rebuilds the engine: workers run on any network, the queue backend is your choice, and governance is enforced when flows are saved or executed. Most flows continue to work, but a few constructs require a guided migration. This session covers what to plan for before you upgrade.

​In 30 minutes, we’ll cover:

• ​What’s new in 2.0 and what it means for your deployment

• ​Why your upgrade starts from 1.3, and why the cutover is one-way

• ​Which flow constructs change (ForEach, pluginDefaults, trigger conditions) and which changes fail silently

• ​How kestra-migrate, the migrate-kestra-2 agent skill and kestractl scan, rewrite and validate your flows

• ​Bitovi’s migration package for teams that want help with the move

​Bring your questions. We’ll leave time at the end.