What problem does it solve?
Migrating Databricks notebooks, jobs, Unity Catalog structures, and runtime configurations to Microsoft Fabric requires manual rewriting of APIs, path conversions, and workload mappings, which is time-consuming and prone to errors. This Skill eliminates that manual effort by providing exhaustive reference materials and code patterns for accurate, low-effort porting.
Core Features & Use Cases
- Exhaustive dbutils to notebookutils API Mapping: Complete side-by-side reference for replacing all Databricks dbutils calls with Fabric notebookutils equivalents, including file system operations, secrets management, notebook orchestration, and widget migration workarounds.
- Workload Migration Guidance: Step-by-step instructions for converting Unity Catalog three-level namespaces to Fabric Lakehouse two-level schemas, Databricks Jobs to Spark Job Definitions, Delta Live Tables to Fabric Pipelines, and MLflow tracking configurations.
- Before/After Code Patterns: Ready-to-use code snippets for common migration scenarios including DBFS to OneLake path conversion, secret scope to Azure Key Vault integration, and Photon to Native Execution Engine substitution.
- Use Case: Data engineering and analytics teams moving from Databricks to Microsoft Fabric can use this Skill to accelerate migration of existing workloads without rewriting code from scratch.
Quick Start
Use the databricks-migration skill to port your existing Databricks notebooks, jobs, and Unity Catalog structures to Microsoft Fabric with correct API substitutions and namespace mappings.