This is a case-study blueprint; no deployment results or customer endorsement are claimed.
Business challenge
Transformation logic is embedded in exported ETL mappings and job graphs.
Migration approach
Extract supported expressions, joins, lookups, parameters, and reject paths into a versioned conversion specification. Propose SQL, dbt, or Spark transformation structures and explain missing source context.
Deterministic work
Extract supported expressions, joins, lookups, parameters, and reject paths into a versioned conversion specification. Record rule versions, target constraints, and unresolved exceptions; verify outputs against an agreed baseline.
Agentic assistance
Propose SQL, dbt, or Spark transformation structures and explain missing source context. Review generated proposals before adopting them as implementation or access rules.
Acceptance evidence
Review transformation parity, dependency order, failure handling, and restart behavior.
Delivery time
The 28 months (estimated) assumes the stated migration inventory, accessible source definitions, available reviewers, and an agreed target environment. Plan discovery, design, build, parity testing, business review, and release readiness as separate checkpoints. Re-estimate when access, custom features, data issues, or acceptance scope changes.