This is a case-study blueprint; no deployment results or customer endorsement are claimed.
Business challenge
A platform transition changes how jobs are scheduled and recovered.
Migration approach
Map approved dependency, calendar, parameter, timeout, retry, and notification rules. Propose target workflow definitions and identify ambiguous operational assumptions.
Deterministic work
Map approved dependency, calendar, parameter, timeout, retry, and notification rules. Record rule versions, target constraints, and unresolved exceptions; verify outputs against an agreed baseline.
Agentic assistance
Propose target workflow definitions and identify ambiguous operational assumptions. Review generated proposals before adopting them as implementation or access rules.
Acceptance evidence
Rehearse dependency ordering, time zones, overlapping runs, failures, retries, and operator escalation.
Delivery time
The 14 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.