Migrate from Terraform¶

If you're using the Terraform Fabric Provider, here's how to migrate to fab-bundle.

Why Migrate?¶

	Terraform	fab-bundle
Language	HCL	YAML
State	Remote (S3, Blob, etc.)	Local or OneLake
Learning curve	High (HCL, providers, modules)	Low (single YAML file)
Drift detection	`terraform plan`	`fab-bundle drift`
Rollback	Manual state manipulation	`fab-bundle rollback`
Fabric-specific	Generic provider	Purpose-built for Fabric
MCP support	No	Yes (12 tools)
Item types	~15	45

Adoption flows¶

fab-bundle ships three complementary commands for bringing existing resources under management. Pick the one that matches your starting point:

Command	Use when	Scope
`fab-bundle import --from-terraform`	You already manage Fabric with Terraform and want to migrate in bulk.	Reads `terraform.tfstate`, extracts all `microsoft_fabric_*` resources, and seeds fab-bundle state.
`fab-bundle generate`	You have a workspace but no declaration yet and want to reverse-engineer a `fabric.yml`.	Scans a live workspace and writes `fabric.yml` plus item content (notebook source, etc.).
`fab-bundle bind`	You wrote the declaration by hand and want to attach it to an existing item without recreating it.	Per-resource; binds one entry in `fabric.yml` to one live item by ID.

Compared to Databricks Asset Bundles

databricks bundle generate exists but is per-resource-type and requires the existing item's ID. databricks bundle deployment bind is the direct analog of fab-bundle bind. DAB has no equivalent of fab-bundle import --from-terraform — migrating from Terraform on Databricks is a manual generate + bind per resource. Bulk tfstate ingestion is unique to fab-bundle.

Step-by-step Migration¶

1. Import existing state¶

fab-bundle import --from-terraform terraform.tfstate --target dev

This reads your Terraform state and creates a fab-bundle state file.

2. Generate fabric.yml¶

fab-bundle generate --workspace "your-workspace-name"

Or manually map your Terraform resources:

Terraform	fabric.yml
`microsoft_fabric_workspace`	`targets.dev.workspace`
`microsoft_fabric_lakehouse`	`resources.lakehouses`
`microsoft_fabric_notebook`	`resources.notebooks`
`microsoft_fabric_warehouse`	`resources.warehouses`
`microsoft_fabric_spark_environment`	`resources.environments`
`microsoft_fabric_data_pipeline`	`resources.pipelines`

3. Validate¶

fab-bundle validate
fab-bundle plan --target dev

4. Deploy¶

fab-bundle deploy --target dev

5. Remove Terraform¶

Once fab-bundle is managing your resources, remove the Terraform config. Keep the Terraform state file as a backup until you're confident.