Move estates to Databricks with governed proof. Connect, inventory, scope, build, move and go live, with certificates an auditor can verify.

Move your estate to Databricks, with proof

TechFabric Airlift runs your migration as one governed job instead of a spreadsheet of hand-offs. A migration team connects a source estate, inventories it, scopes the work, builds the Databricks target, moves the data, proves parity, and goes live — and Airlift records every decision, artifact, and piece of evidence on one policy-enforced ledger so the speed never costs you the audit.

Connect → Inventory → Scope → Build → Move → Prove → Go-live
              ↘ Fixes (residue / discrepancies) ↗

Speed comes from doing each stage once against a shared, typed inventory. Safety comes from the proof behind it: nothing reaches Go-live without independent validation evidence and a migration certificate that is system-minted and Ed25519-signed, derived from recorded evidence — never authored by the caller. What the certificate does and does not claim is spelled out in the trust appendix.

Who uses which surface

You are	Your home	What you do there
a migrator	the Airlift Databricks App	run each stage, work the Fixes queue, watch progress and blockers
a migration lead or approver	the Airlift Databricks App	freeze scope, approve waves, accept for the business, decide go-live
an auditor or sponsor	the App trust view	read certificates, evidence, and the audit export — read-mostly
automation or CI	the `fa` CLI and versioned remote API	record diagnostics and evidence under the admitted automation role — never approve, waive, certify, or cut over

Every surface invokes the same governed actions; the App, CLI, and API never take different mutation paths.

Start in the App

Follow the App walkthrough — annotated, public synthetic screenshots of one migration from engagement setup through cutover, each paired with the exact next developer action.

What Airlift implements under each stage

Stage	What your project calls or implements	What Airlift records/enforces
Connect / Inventory	source metadata/export adapter or Lakebridge Profiler/Analyzer	run identity, inventory/dependency digests, tool version
Build	Lakebridge, entity mapper, pipeline implementation, or stream bootstrap	method, immutable artifacts, residue disposition
Move	source-specific snapshot/incremental driver	watermarks, restart checkpoints, lag, counts, reconciliation
Prove	Lakebridge Reconcile, Experiments testkit, or admitted external runner	provider run, immutable evidence, readiness observation
Go-live	client-certified checkpoint/apply-once/verify/compensate effector	approvals, separation of duties, freeze digest, rehearsal, operational evidence, durable outcome, rollback, hypercare
the certificate itself	no caller implementation	profile-derived, system-minted and Ed25519-signed envelope — see parity certificates

Supported source profiles

Airlift ships profiles for warehouses and databases, SAP and SaaS applications, ETL platforms, mainframe data, federated query engines, and event streams. Every profile publishes evidence-derived support alongside separate non-evidentiary implementation routing. An empty tenant registry is always cataloged, regardless of shipped implementation paths. Run fa source inspect <source> to see the exact boundary, then open source systems for developer routes.

The governed programming model

Every meaningful state change is an airlift.* Platform action. Console handlers, workers, and agents invoke the same authenticated runtime. Event handlers return pending domain events; projections build the inventory, funnel, readiness matrix, wave board, certificate ledger, and audit trail. Agents may propose or record conversion work but cannot approve, waive, certify, or cut over.

Read architecture for package boundaries and action catalog for the exact mutation contract.

Automation and CLI

Install the CLI when you need scripted source plans, diagnostics, or evidence admission:

npm install --global @fabricorg/airlift-cli

fa sources
fa source inspect dynamics_365
fa source plan dynamics_365 \
  --variant dynamics_365_finance_operations \
  --json > dynamics-finance-plan.json

The generated plan covers inventory, code conversion, data movement, orchestration, security, validation, performance, consumers, cutover, and post-parity modernization. It names the applicable specialist adapter boundary, the Airlift actions your integration must invoke, project outputs, and exit criteria.

Use the same registry in application code:

import {
  AIRLIFT_ACTION_IDS,
  createSourceMigrationPlan,
  resolveSourceSystemProfile,
} from '@fabricorg/airlift';

const source = resolveSourceSystemProfile('d365');
const plan = createSourceMigrationPlan(source.id, {
  variant: 'dynamics_365_finance_operations',
});

console.log(source.workloadSurfaces);
console.log(plan.steps.map((step) => step.airliftActions));
console.log(AIRLIFT_ACTION_IDS.assessmentRecord);

Continue with the source developer workflow for the complete assessment-to-cutover integration.

Documentation map

App walkthrough — the primary path through one migration.
Quickstart — build, test, run, and inspect a plan.
CLI command reference — every implemented command.
Cutover commands — frozen scope through hypercare and source disposition.
Source systems — executable source-specific routes and known gaps.
Migration lifecycle — how adapters and actions compose by phase.
Parity certificates — the certificate honesty model.
Operations — identity, evidence, recovery, and scale.
Integrations — Platform, Harness, Experiments, Runway, Radar, Tower.
Reference — actions, events, profiles, configuration, and errors.

Use production readiness to verify the installation, source profile, evidence providers, and cutover effector before operating on production data.

TechFabric Airlift developer documentation