What problem does it solve? Porting Databricks workloads to Microsoft Fabric requires replacing every dbutils call, collapsing Unity Catalog three-level namespaces, and re-platforming jobs, clusters, and MLflow tracking, which is error-prone without an exhaustive mapping reference. ## Core Features & Use Cases - Complete dbutils to notebookutils Mapping: Covers fs operations, secret scope to Key Vault URL conversion, notebook run/exit, widget replacement with parameter-tagged cells, and library install replacement with Fabric Environments. - Catalog and Storage Migration: Reduces Unity Catalog catalog.schema.table namespaces to Lakehouse schema.table structures and converts DBFS paths to OneLake abfss paths. - Workload Re-platforming: Maps Databricks Jobs to Spark Job Definitions, Delta Live Tables to notebooks plus Data Pipelines, Photon to Native Execution Engine, and MLflow tracking to Fabric ML Experiments. - Use Case: A data engineer inherits 50 Databricks notebooks using dbutils.secrets, widgets, and Unity Catalog tables, and needs each one rewritten for Fabric with correct notebookutils calls, parameter cells, and two-level schema references. ## Quick Start Migrate this Databricks notebook to Microsoft Fabric by replacing all dbutils calls with notebookutils and converting Unity Catalog table references to Lakehouse schemas.