This is a case-study blueprint; no deployment results or customer endorsement are claimed.
Business challenge
A desktop application contains valuable rules mixed with user-interface and persistence logic.
Migration approach
Classify modules, event handlers, shared routines, and external calls; preserve traceability to source assets. Propose separation of domain logic, interface behavior, and data-access responsibilities.
Deterministic work
Classify modules, event handlers, shared routines, and external calls; preserve traceability to source assets. Record rule versions, target constraints, and unresolved exceptions; verify outputs against an agreed baseline.
Agentic assistance
Propose separation of domain logic, interface behavior, and data-access responsibilities. Review generated proposals before adopting them as implementation or access rules.
Acceptance evidence
Exercise user journeys, validation rules, state transitions, and integration contracts before accepting a redesign.
Delivery time
The 17 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.