Presto to Databricks

fa source inspect presto
fa source plan presto --variant presto

Presto often exposes many independent backing systems. Airlift inventories catalogs, schemas, tables, views, queries, connectors, custom functions, session properties, access controls, schedulers, and consumers. Each catalog receives its own disposition: Lakehouse Federation, governed registration, Delta materialization, source-specific ingestion, SQL conversion, or a human lane.

Movement remains owned by the adapter for each backing source. Airlift records the artifact, source boundary, target snapshot, restart state, and validation runs that join those routes into one migration wave. Independent scenarios test dialect semantics, connector-specific types, federated joins, functions, access, business results, and performance.

After certification, switch queries and consumers through a frozen, approved wave with checkpoint/apply-once/verify/rollback evidence. Modernization can progressively replace federation with governed Delta products without changing the baseline certificate.

The pack is cataloged pending representative live-catalog evidence.

Complete developer command sequence

Generate this exact recipe from the installed CLI so the guide and executable surface stay in sync:

fa source recipe presto
fa source recipe presto --variant presto --json > .airlift/presto-recipe.json

The App is engagement-aware. Presto appears under Active sources only after the source estate is added to an active engagement. The menu is derived from governed engagement scope; installing Airlift does not expose unrelated source pages.

Every remote mutation below requires --host, --org, authenticated workspace identity, and a stable --idempotency-key. JSON request files contain identifiers, artifact references, and opaque credential references—never passwords, tokens, or connection strings. Run fa <resource> <operation> --help for the current schema and exit semantics.

0. Inspect the source contract

fa source inspect presto --json > .airlift/presto-profile.json
fa source plan presto --variant presto --json > .airlift/presto-capability-plan.json

Expected artifacts:

• .airlift/presto-profile.json
• .airlift/presto-capability-plan.json

Open Engagements → active engagement in the App. This stage is visible at /engagements after replacing the placeholder ID with the governed engagement ID.

1. Create governed scope and connection references

fa engagement create --file engagement.json --idempotency-key migration-create-v1
fa estate register --file presto-estate.json --idempotency-key presto-estate-v1
fa connection register --file presto-connection.json --idempotency-key presto-connection-v1
fa engagement update --file presto-scope.json --idempotency-key presto-scope-v1
fa engagement preflight <engagement-id>

Expected artifacts:

• Governed engagement
• Source estate
• Opaque connection binding

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id> after replacing the placeholder ID with the governed engagement ID.

2. Assess and accept inventory

fa assessment start --file presto-assessment-start.json --idempotency-key presto-assessment-start-v1
fa assessment status <assessment-id> --json
fa assessment record --file presto-assessment-record.json --idempotency-key presto-assessment-record-v1
fa assessment accept --file presto-assessment-accept.json --idempotency-key presto-assessment-accept-v1
fa inventory list --estate-id <estate-id> --json

Expected artifacts:

• Assessment report reference
• Normalized inventory
• Dependency graph

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/sources/presto after replacing the placeholder ID with the governed engagement ID.

3. Implement the admitted source adapter

No source-specific executable compiler exists in this release. Continue with assessment, governed work, and an admitted adapter; Airlift does not invent executable output.

Expected artifacts:

• Capability plan and adapter requirements only

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/artifacts after replacing the placeholder ID with the governed engagement ID.

This source is cataloged or assessable but has no source-specific executable compiler in the installed Airlift generation.

4. Convert, move, and remediate

fa plan generate --file presto-migration-plan.json --idempotency-key presto-plan-v1
fa conversion batch create --file presto-batch.json --idempotency-key presto-batch-v1
fa conversion batch start --file conversion-batch-start.json --idempotency-key conversion-start-v1
fa residue list --engagement-id <engagement-id>
fa transfer plan --file presto-transfer.json --idempotency-key presto-transfer-v1
fa transfer run <transfer-id> --idempotency-key transfer-run-v1
fa transfer reconcile <transfer-id> --idempotency-key transfer-reconcile-v1

Expected artifacts:

• Target artifacts
• Residue cases
• Transfer checkpoints
• Reconciliation evidence

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

5. Validate independently and inspect discrepancies

fa validation run --file presto-validation.json --idempotency-key presto-validation-v1
fa validation status <validation-execution-id> --json
fa discrepancy list --engagement-id <engagement-id>
fa artifact list --engagement-id <engagement-id>

Expected artifacts:

• Provider run references
• Readiness evidence
• Discrepancies

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

6. Certify, cut over, and export evidence

fa certificate list --object-id <object-id>
fa cutover status <wave-id> --json
fa evidence list --engagement-id <engagement-id>
fa evidence export --file presto-evidence-export.json --idempotency-key presto-evidence-export-v1

Expected artifacts:

• Migration certificates
• Cutover evidence
• Content-digested evidence export

Open Engagements → active engagement in the App. This stage is visible at /assurance after replacing the placeholder ID with the governed engagement ID.

Runway executes releases; Experiments owns validation verdicts; Airlift owns migration readiness and cutover policy.

What developers see in the App

The contextual source workspace shows the accepted estate and the factory stages for this engagement. Artifacts displays immutable references, content digests, media types, and provider lineage. Runs displays assessment, conversion, transfer, validation, and deployment executions without treating a provider's success as an Airlift verdict.

View full size

These are automated captures from public synthetic engagements. The source workspace is specific to Presto; no unrelated source is presented as its migration journey. For sources without an evidence-backed journey, the image demonstrates setup, navigation, and developer entry points only—not a live connection, converted output, or certified migration. No client data, credentials, workspace hostnames, or internal deployment identifiers are embedded in the images.