This is a case-study blueprint; no deployment results or customer endorsement are claimed.
Business challenge
Business rules live in procedures with transactions, cursors, temporary objects, and exception branches.
Migration approach
Map supported statements and retain explicit transaction and error-handling boundaries. Propose alternatives for procedural patterns that lack a direct target equivalent.
Deterministic work
Map supported statements and retain explicit transaction and error-handling boundaries. Record rule versions, target constraints, and unresolved exceptions; verify outputs against an agreed baseline.
Agentic assistance
Propose alternatives for procedural patterns that lack a direct target equivalent. Review generated proposals before adopting them as implementation or access rules.
Acceptance evidence
Test commit and rollback behavior, concurrency assumptions, branch coverage, and business-rule outputs.
Delivery time
The 11 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.