Program timeline

Enterprise Implementation Lifecycle & Milestone Roadmap

Every workstream on one illustrative 20-week grid — Initiation through Transition — with milestone diamonds for approvals, deliverables and decision points, and a cutover marker separating the pre-cutover build from post-cutover hypercare. Filter by workstream or lifecycle stage, and export the roadmap as an image or PDF for internal and customer stakeholders.

Illustrative 20-week shape within a typical 2–6 month journey · Order Form Part H carries the projected Target Go-Live Date

Enterprise Implementation Lifecycle & Milestone Roadmap

11 of 11 workstreams · 13 milestones · W1–W20

Pre-cutover · build & prove
Post-cutover · stabilize & transition
Workstream
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
W12
W13
W14
W15
W16
W17
W18
W19
W20

Initiation

Handoff, internal kickoff, customer kickoff

Stages 1–3 · Delivery Lead

Initiation runs week 1 through week 3

Discovery & scope

Current-state discovery, scope document drafted

Stages 4–5 · Delivery Lead and Engineering Authority (joint solution architecture)

Discovery & scope runs week 3 through week 6

Configuration build

Agency structure, workflows, policy and commission configuration

Stage 6 · Data Migration Lead / MAC Specialist

Configuration build runs week 5 through week 11

Data migration

Extract, map, load, reconcile

Stage 7 · Data Migration Lead

Data migration runs week 7 through week 13

Integrations

Elected Part F integrations configured and validated

Stage 6–8 · Engineering Authority

Integrations runs week 8 through week 13

Testing & UAT

Test scripts, defect triage, customer acceptance

Stage 8 · Delivery Lead

Testing & UAT runs week 11 through week 15

Training

Begins after Testing Sign-off — design and delivery per elected Part G category

Stage 7–9 · Training Lead

Training runs week 15 through week 16

Cutover

Go / no-go, freeze, final load, go-live

Stage 10 · Delivery Lead

Cutover runs week 15 through week 17

Hypercare

Daily standups, issue burn-down, stabilization

Stage 11 · Delivery Lead + Support team

Hypercare runs week 16 through week 19

Transition to CSM

Risk register at zero, account handover, first QBR set

Stages 12–13 · Customer Success Manager

Transition to CSM runs week 18 through week 20

Custom development (if required)

Conditional

Alternative route. Only runs when discovery surfaces a requirement configuration cannot meet: scoping request, engineering scope, signed Custom Development SOW and Change Order, build, internal QA, then customer acceptance inside UAT. Accounts with no custom work simply do not have this row.

Stages 4–8 · Engineering Authority (build) · Delivery Lead (template & status)

Conditional route. Custom development (if required) runs week 5 through week 14
Activity durationMilestone, approval or decision point — hover or click for detailCutover / go-liveConditional route — only if the account requires it
  • W1Contract sign-offApproval · Initiation
  • W5Custom development request raisedDeliverable · Custom development (if required)
  • W6Scope document sign-offApproval · Discovery & scope
  • W8Configuration baselineDeliverable · Configuration build
  • W8Custom Development SOW & Change Order approvedApproval · Custom development (if required)
  • W12Data correctness sign-offApproval · Data migration
  • W14Curriculum deliveredDeliverable · Training
  • W14Custom development acceptedApproval · Custom development (if required)
  • W15Testing passedApproval · Testing & UAT
  • W15Go / no-go decisionDecision point · Cutover
  • W16Go-live / cutoverDeliverable · Cutover
  • W19Hypercare exitDeliverable · Hypercare
  • W20Handover acceptedApproval · Transition to CSM

Illustrative standard program shape. Week positions are planning guidance only — the projected Target Go-Live Date lives in Order Form Part H and becomes a commitment at the Stage 5 scope sign-off. The complete journey from signature through hypercare and formal handover typically takes two to six months.

The dashed Custom development row is an alternative route, not standard work. Most enterprise accounts never trigger it. It only opens when discovery surfaces a requirement configuration cannot meet, and it only proceeds once a Custom Development SOW and Change Order are signed. For an account with no custom work, read the roadmap without that row.