5. Migration Timeline

Day(s)

Phase & Environment

Key Deliverables

Days 1–3

Assessment & Planning

Custom app audit, API compat matrix, go/no-go criteria, rollback plan, staging servers provisioned

Days 3–6

V15 Staging Setup (Env 2)

V15 bench running, V14 DB restored, bench migrate clean on V15, V15 assets built

Days 5–9

V15 App Remediation

All custom apps on v15-compat branch, pytest suites passing on V15 staging

Days 9–11

V15 Staging UAT

V15 UAT sign-off obtained, clean V15 DB backup taken, go/no-go for V16 phase approved

Days 11–13

V16 Staging Setup (Env 3)

V16 bench running, V15 DB restored, bench migrate clean on V16, V16 assets built

Days 12–15

V16 App Remediation

All custom apps on v16-compat branch, Vue 3 migration complete, pytest suites passing on V16

Days 15–17

V16 Staging UAT + Pre-Prod Prep

V16 UAT sign-off, final dry run, change freeze, management go/no-go obtained

Day 18

Production Cutover

V14→V15 hop on production, V15→V16 hop on production, go-live smoke tests, hypercare starts

Days 19–20+

Post-Live Stabilisation

P1/P2 issues resolved, scheduler verified, performance tuned, retrospective completed

Timeline Assumptions

Total delivery target: 18 to 20 days from kickoff to production go-live.

Assumes 5 to 15 custom Frappe apps with moderate complexity.

App remediation phases (Days 5–9 and Days 12–15) run in parallel with staging bench setup where possible.

Vue 2 → Vue 3 migration is the most time-sensitive task — must start on Day 1 alongside assessment.

Production cutover (Day 18) requires a full day window (6 to 14 hours); schedule on a low-traffic day.

Post-live stabilisation continues beyond Day 20; Day 20 marks the end of formal hypercare.

Each additional 5 custom apps may add 1 to 2 days to remediation phases.