Implement Netezza migrations with Analyzer, BladeBridge conversion, explicit transfer adapters, Experiments parity, and appliance residue tracking.

Migrate Netezza with Airlift

Netezza is an additional Airlift source profile beyond the seven named M&M program tracks. The profile covers SQL, NZPLSQL, external tables, nzload/nz_migrate, distribution keys, scheduler dependencies, extensions, and downstream BI.

What Airlift adds to a Netezza migration

Stage	Databricks tool or project adapter	Airlift responsibility
discover	Lakebridge Analyzer plus a reviewed appliance/workload extraction	accept inventory, dependencies, exclusions, source version, extraction identity, and report digests
plan	assessment and unload measurements inform target architecture	assign owners and dependency-aware waves; preserve NZPLSQL, extension, utility, and human-work decisions
convert	BladeBridge converts supported Netezza SQL	record attempts, tool generations, artifact digests, warnings, and residue lanes
move data	external-table or utility snapshot plus a source-specific delta strategy	track manifests, watermarks, lag, restart checkpoints, rejected rows, counts, and target snapshots
validate	admitted Experiments schema, row, aggregate, sampled, and business scenarios	admit independent evidence because there is no universal Lakebridge Reconcile connector
certify	Airlift evaluates the active readiness profile	mint a signed certificate identifying artifacts, snapshots, evidence, and policy
cut over	project load, scheduler, application, and BI connection effectors	freeze scope, enforce approvals, checkpoint, apply once, verify, and retain rollback evidence
modernize	Unity Catalog, Lakeflow, Delta, liquid clustering, and Databricks SQL work	keep appliance-specific redesign separate from baseline parity

This preserves the work that an SQL-only report misses: appliance utilities, extensions, physical organization, scheduler calls, data extraction, permissions, and consumers.

Inspect and generate a plan

fa source inspect netezza
fa source plan nz --json > .airlift/netezza-plan.json

Analyze

Lakebridge Analyzer supports Netezza exports. The current upstream matrix does not list a Netezza database profiler, so collect workload and appliance metrics with a reviewed client extraction and retain that artifact separately.

databricks labs lakebridge analyze \
  --source-directory ./source-export \
  --source-tech "Netezza" \
  --report-file ./artifacts/netezza-analysis.xlsx \
  --generate-json true

Inventory NZPLSQL, UDF/UDA extensions, external table formats, load scripts, distribution/organization clauses, scheduler calls, grants, and consumers in addition to standard DDL.

Convert

databricks labs lakebridge transpile \
  --source-dialect netezza \
  --input-source ./source-export/sql \
  --output-folder ./artifacts/converted

BladeBridge is the preferred deterministic path. Route NZPLSQL, extensions, appliance utilities, cross-database references, and physical organization behavior to explicit residue. Airlift preserves these objects and owners in the ledger.

Transfer and validate

Implement snapshot extraction with external tables or approved Netezza utilities, then add a source-specific delta strategy. Return file manifests, restart points, source watermarks, target snapshots, row counts, and rejected-row evidence.

Lakebridge Reconcile does not currently list a Netezza connector. Run schema, row, aggregate, sampled, and business-query scenarios through an admitted Fabric Experiments producer. Record the immutable run and evidence digest before resolving readiness.

Certify and cut over

Assign profiles to SQL, NZPLSQL, utilities, extensions, jobs, and consumers, then admit source-specific validation runs before minting certificates. The project effector may switch loads, schedules, endpoints, and BI connections only after Airlift verifies the frozen wave and current approvals. Retain extraction completion, target observations, and rollback evidence because converted SQL alone cannot prove appliance retirement.

Modernize after parity

Replace appliance utilities, map tables to Delta and liquid clustering from measured workloads, move jobs into Lakeflow, and apply Unity Catalog governance in a separate modernization release.

Complete developer command sequence

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

fa source recipe netezza
fa source recipe netezza --variant netezza_performance_server --json > .airlift/netezza-recipe.json

The App is engagement-aware. Netezza 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 netezza --json > .airlift/netezza-profile.json
fa source plan netezza --variant netezza_performance_server --json > .airlift/netezza-capability-plan.json

Expected artifacts:

.airlift/netezza-profile.json
.airlift/netezza-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 netezza-estate.json --idempotency-key netezza-estate-v1
fa connection register --file netezza-connection.json --idempotency-key netezza-connection-v1
fa engagement update --file netezza-scope.json --idempotency-key netezza-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 netezza-assessment-start.json --idempotency-key netezza-assessment-start-v1
fa assessment status <assessment-id> --json
fa assessment record --file netezza-assessment-record.json --idempotency-key netezza-assessment-record-v1
fa assessment accept --file netezza-assessment-accept.json --idempotency-key netezza-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/netezza 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 netezza-migration-plan.json --idempotency-key netezza-plan-v1
fa conversion batch create --file netezza-batch.json --idempotency-key netezza-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 netezza-transfer.json --idempotency-key netezza-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 netezza-validation.json --idempotency-key netezza-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 netezza-evidence-export.json --idempotency-key netezza-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.

Airlift Netezza source workspace showing the governed estate and developer command entry point — Netezza has its own engagement-scoped workspace; unrelated source systems are not shown.
What you are seeing
This public synthetic capture demonstrates Airlift setup and navigation for Netezza; it is not evidence of a live connection or certified migration.
What to do next
Register the client estate, bind a credential reference, run the Netezza assessment recipe, and admit the resulting evidence.
Read the developer workflow

These are automated captures from public synthetic engagements. The source workspace is specific to Netezza; 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.

Netezza

On this page