# TechFabric Airlift

> A governed migration factory for moving warehouse and ETL estates to Databricks.

Role: Migration accelerator
Databricks surfaces: Lakebridge, Unity Catalog, Databricks Asset Bundles, Databricks Apps, Temporal
Status: Console, worker, CLI, and declarative Databricks Asset Bundle deployment are implemented. Twenty-seven source platforms have executable playbooks, including Snowflake, Azure Synapse, Amazon Redshift, Oracle, Teradata, SQL Server, BigQuery, Netezza and SAP. The first two weeks of an Airlift engagement are sold on their own as the Migration Readiness Sprint.
Documentation: https://airlift.techfabric.com
Canonical: https://www.techfabric.com/accelerators/airlift

---

## 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 changes for you

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.

## Questions

### Which source warehouses can Airlift migrate?

Twenty-seven, each with an executable playbook. Snowflake, Azure Synapse and Teradata have their own pages at /databricks/from-snowflake, /databricks/from-synapse and /databricks/from-teradata. Redshift, Oracle, SQL Server, BigQuery, Netezza and SAP are covered too. Tell us your source and we will confirm what the playbook does 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.