# Migrations to Databricks

> TechFabric builds on Databricks end to end: migrating warehouses and ETL onto the lakehouse, designing Unity Catalog governance, and shipping applications that run inside the workspace. We run our own business on the same stack, so the patterns we recommend are ones we operate ourselves.

For: Data platform leads with a funded initiative
Canonical: https://www.techfabric.com/services/databricks

---

We build on Unity Catalog, Lakeflow, Databricks Apps, AI Gateway, and Genie, and we run our own business on the same stack. Migration off legacy warehouses, governed pipelines, and applications that live inside the workspace.

## What it includes

- Inventory and exclusions agreed before a wave plan, so scope is defensible
- Warehouse and ETL conversion wrapped in signed certificates and a reversible cutover
- Operational databases onto Lakebase, not only the analytics estate
- Twenty-seven source platforms with executable playbooks behind TechFabric Airlift

## Questions

### Can you migrate our existing warehouse to Databricks?

Yes. The first two weeks are the Migration Readiness Sprint at /databricks/migration-readiness. TechFabric Airlift at /accelerators/airlift composes Databricks Lakebridge, then wraps conversion in signed certificates and a reversible cutover. If you already know the source, start at /databricks/from-snowflake, /databricks/from-synapse or /databricks/from-teradata.

### What does Unity Catalog governance actually involve?

Deciding who can see what, proving it, and keeping lineage intact as data moves. In practice that means catalogue and schema design, grants that match how your teams actually work, and making sure the applications and agents you build inherit those permissions instead of routing around them.

### Do you build Databricks Apps, or just pipelines?

Both. Applications that run in-workspace under their own service principal are a large part of what we do, using Databricks Apps, Unity AI Gateway, Model Serving and Genie. That is the difference between a lakehouse and a system people actually use.

### We already have a Databricks team. Where do you fit?

Usually on the initiative that keeps slipping because your team is fully committed elsewhere. We take ownership of that piece without pulling anyone off the current roadmap, and we work in your workspace so nothing has to be handed back later.

### Which Databricks surfaces do you work with?

Unity Catalog, Lakeflow, Delta, Databricks SQL, Databricks Apps, Model Serving, AI Gateway, Genie, Lakebase and Asset Bundles. Our accelerators are built on those same surfaces.