This is a case-study blueprint; no deployment results or customer endorsement are claimed.
Business challenge
A reporting estate is moving to a different analytical SQL engine.
Migration approach
Apply approved mappings for functions, types, joins, and aggregation patterns; flag unsupported constructs. Explain business logic and propose target SQL for ambiguous expressions.
Deterministic work
Apply approved mappings for functions, types, joins, and aggregation patterns; flag unsupported constructs. Record rule versions, target constraints, and unresolved exceptions; verify outputs against an agreed baseline.
Agentic assistance
Explain business logic and propose target SQL for ambiguous expressions. Review generated proposals before adopting them as implementation or access rules.
Acceptance evidence
Compare representative periods, edge-case inputs, numeric precision, and downstream report outputs.
Delivery time
The 2 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.