Migrating Control-M, AutoSys, Automic, and Tidal to Apache Airflow
October 8, 2026 | 11am ET / 4pm BST
Whether it’s Control-M, AutoSys, Automic, Tidal, or some combination: nobody wants to be attached to their legacy scheduler. The world's oldest banks and frontier labs are among the 85,000+ organizations running on Airflow… So why hasn't your team moved yet?
Because migrating a legacy scheduler at scale can be terrifying. With thousands of job definitions and years of undocumented dependencies, you’re one bad step from breaking production.
Hear from Waj Khan, Director of Data Platforms at Ontario Teachers' Pension Plan, on how the team migrated off UC4 / Automic onto Airflow: how he made the internal case, ran the cutover without disrupting production, and consolidated batch, analytics, and machine learning onto one orchestration layer.
You’ll learn how to:
- Make the internal case: why this is standardizing on where the industry's already headed, not a random migration project
- De-risk the cutover with a parallel-run, wave-based approach, so your legacy scheduler stays live until every workload is validated
- Automatically convert Control-M, AutoSys, Automic and Tidal job definitions into production-ready Airflow Dags with a data engineering agent
Save Your Spot Today
By proceeding you agree to our Privacy Policy, our Website Terms and to receive emails from Astronomer.
