Migration factory
Fabric Airlift
A governed migration factory for moving warehouse and ETL estates to Databricks.
A warehouse migration your risk function will actually sign off. Scope, evidence, certificates, and a reversible cutover are part of the process, so the migration stops being a long weekend with a rollback plan nobody has tested.
3 common questions, answered below ↓- Role in the family
- Migration factory
- Databricks surfaces
- LakebridgeUnity CatalogDatabricks Asset BundlesDatabricks AppsTemporal
- Status
- Console, worker, CLI, and declarative Databricks Asset Bundle deployment are implemented. Source profiles cover multiple warehouse origins.
- Documentation
- airlift.fabric.pro
The problem
Conversion is the easy part of a migration. The hard part is proving what was in scope, which tool version produced which artifact, what evidence says it is correct, and how to reverse a cutover at two in the morning when it is not.
How it works
Airlift composes Databricks Lakebridge for profiling, analysis, SQL conversion, and reconciliation, then wraps it in a policy-enforced lifecycle: discovery and scope acceptance, independent validation, signed migration certificates, approved waves, and reversible cutover. Every artifact carries the tool version that produced it and the evidence that cleared it.
What it does
Evidence, not assertions
Each converted artifact is bound to immutable evidence proving it is ready to promote.
Signed migration certificates
A wave cuts over only when its certificate is issued. The certificate is the gate, not a status field.
Reversible cutover
Checkpoint, apply, verify, with a defined path back out of an external change.
Wave planning
Scope is accepted explicitly and cut over in approved waves.
A warehouse migration your risk function will actually sign off. Scope, evidence, certificates, and a reversible cutover are part of the process, so the migration stops being a long weekend with a rollback plan nobody has tested.
FAQ
Fabric Airlift, answered
Which source warehouses can Airlift migrate?
It composes Databricks Lakebridge for profiling, analysis, SQL conversion and reconciliation, and adds source-specific transfer profiles on top. Synapse is one of the implemented routes; tell us your source and we will confirm what is covered today.
What makes a migration reversible?
Cutover runs as checkpoint, apply, verify, with a defined path back out of an external change. A wave only cuts over once its certificate is issued, so the gate is the evidence itself.
Can our risk function audit the migration?
That is the design goal. Every converted artifact is bound to immutable evidence and carries the tool version that produced it, so what was in scope, what proved it correct and who approved the wave are all answerable after the fact.