skills.rest
MGPowerlytics
MGPowerlyticsCOMMUNITY
Explore all skills by this author →
GitHub

airflow-3x-migration

Migrate Airflow 2.x workflows to Airflow 3.x by updating imports and adopting TaskFlow API.

Updated Jan 16, 2026
Search Tags:#automation#migration#airflow#providers#dag#taskflow
One-click install
npx skills add https://github.com/MGPowerlytics/nhlstats --skill airflow-3x-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: airflow-3x-migration
Source: https://github.com/MGPowerlytics/nhlstats/tree/main/.github/skills/airflow-3x-migration
Command: npx skills add https://github.com/MGPowerlytics/nhlstats --skill airflow-3x-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams migrate Apache Airflow 2.x workflows to Airflow 3.x by updating imports, replacing deprecated features, and adopting new paradigms like Asset scheduling and the TaskFlow API.

Core Features & Use Cases

  • Import path changes for operators and sensors to their 3.x provider packages.
  • Replacement of deprecated features with modern alternatives (e.g., SubDagOperator to TaskGroup, and changes to schedule and providers model).
  • Guidance for DAG definition changes, Asset-based scheduling, and new versioning patterns across typical betting workloads.

Quick Start

Review the migration guide, apply the changes to a sample DAG, and validate compatibility using Airflow 3.x tooling and tests.

Frequently Asked Questions about airflow-3x-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Airflow 2.x workflows to 3.x?▼

To migrate Airflow 2.x workflows to 3.x, update operator and sensor imports to their 3.x provider packages, replace deprecated features like SubDagOperator with TaskGroup, and adopt Asset-based scheduling.

What deprecated Airflow features need replacing during a 3.x migration?▼

During an Airflow 3.x migration, deprecated features like the SubDagOperator must be replaced with modern alternatives such as TaskGroup, alongside adopting new versioning patterns and the updated providers model.

Do I need to change import paths for operators when upgrading to Airflow 3.x?▼

Yes, upgrading to Airflow 3.x requires changing import paths for operators and sensors to their respective new 3.x provider packages to ensure compatibility with the updated providers model.

How does Asset-based scheduling work in Airflow 3.x?▼

Asset-based scheduling in Airflow 3.x replaces older scheduling paradigms by allowing DAGs to trigger based on data asset availability, requiring you to update DAG definitions to adopt this new model during migration.

How do I validate Airflow 3.x migration changes for my DAGs?▼

Validate Airflow 3.x migration changes by applying updates to a sample DAG, checking compatibility against the provided migration guides, and testing the DAGs using Airflow 3.x tooling and example references.

Can I use the TaskFlow API for Airflow 2.x to 3.x migration?▼

Yes, adopting the TaskFlow API is a core part of migrating Airflow 2.x workflows to 3.x, enabling modern task definition paradigms alongside Asset-based scheduling and updated provider imports.

Related Skills

Explore More Software Engineering Skills→
astronomerastronomer
419

migrating-airflow-2-to-3

Migrate Airflow 2.x DAGs and code to Airflow 3.x with rule-based fixes.

Official
Advanced
emilneuraz-aiemilneuraz-ai

airflow-dag-patterns

Design production-ready Airflow DAGs with operators, sensors, testing, and deployment.

Community
Advanced
astronomerastronomer
419

cosmos-dbt-core

Convert dbt Core projects into Airflow DAGs or TaskGroups using Astronomer Cosmos.

Official
Advanced
minyeamerminyeamer
3

dag-factory

Convert YAML configuration files into executable Apache Airflow DAG definitions.

Community
Intermediate