We just shipped migration skills that help you try out
@ZenML_io from 11 different ML/data platforms.
Airflow, Argo, AzureML, Dagster, Databricks, Flyte, Kedro, Metaflow, Prefect, SageMaker, Vertex AI.
You could just paste your pipeline code into your coding agent and ask it to convert. But these skills have something extra baked in:
→ Hand-curated (ok ok, mostly!) concept maps for each platform showing what maps 1:1, what's approximate, and what needs genuine redesign
→ Knowledge of ZenML best practices and common migration pitfalls
→ A conservative approach: the skill flags what it's unsure about rather than making something up
Each platform has its own migration story. Dagster's asset-first world needs different thinking than Airflow's scheduler-first model. Prefect's dynamic runtime doesn't translate the same way as Kedro's Data Catalog.
For cloud platforms (AzureML, SageMaker, Vertex AI), the skills support "keep the backend" paths too: switch to ZenML authoring while keeping your existing cloud execution.
They work with
@AnthropicAI Claude Code,
@cursor_ai,
@OpenAI Codex, or any coding agent that supports custom instructions / agent skills. Open-source and free to install.
We've tested them, but 11 platforms is a lot of ground to cover. If you give one a try and have feedback on what worked, what was off, or what's missing, we'd love to hear it. Issues and PRs very welcome.
#MLOps #AgenticCoding #MachineLearning #OpenSource
ALT A table outlines migration pathways from various ML/data platforms to ZenML, detailing translation and special notes for each.