Migration Cutover Downtime Risk Estimator
Estimate migration cutover downtime, calculate business impact, and assess rollback risk. Enter values for instant results with step-by-step formulas.
Worked Examples
Example 1: E-Commerce Platform Migration
Problem: Migrate 500GB database to new cloud provider. 100Mbps transfer speed. 12 cutover steps (DNS, app deploy, validation, etc.), 15 min each avg. 50% buffer. Schedule during 2-6 AM. Risk?
Solution: Data Transfer:\n- 500 GB × 8 × 1,024 / 100 / 60 = 683 minutes (11.4 hours)\n\nCutover Steps:\n- 12 steps × 15 min = 180 min (3 hours)\n- With 50% buffer: 270 min (4.5 hours)\n\nTotal Downtime:\n- Transfer: 683 min (11.4h)\n- Cutover: 270 min (4.5h)\n- Total: 953 min (15.9 hours)\n\nProblem:\n- 4-hour maintenance window insufficient\n- Need ~16 hours\n\nRevised Plan:\n1. Pre-transfer bulk data Friday night\n - Transfer 495 GB (99%)\n - Time: ~11 hours\n2. Sunday 2 AM cutover:\n - Transfer final 5 GB delta: ~40 min\n - Execute cutover: 270 min\n - Total downtime: 310 min (5.2 hours)\n\nRisk Mitigation:\n- Dry run in staging (required)\n- Rollback plan: switch DNS back (30 min)\n- Monitoring: dashboard for data sync validation\n\nDowntime Window: Sunday 2-8 AM (6 hours scheduled, 5.
Result: Initial: 16h downtime (unacceptable) | Revised with pre-transfer: 5.2h | Sunday 2-8 AM window
Frequently Asked Questions
What is cutover in migrations?
Cutover is the moment you switch from old system to new. It's the riskiest part of migrations. Activities include: final data sync, DNS changes, traffic routing, smoke tests, validation. Cutover window is planned downtime needed to complete these steps. Poor planning causes extended outages.
What migration strategies minimize downtime?
Big-bang (full cutover at once, highest risk), Blue-green (new environment fully built, instant switch), Rolling (gradual user migration), Canary (small user %, then expand), Strangler pattern (incrementally migrate features). Blue-green and canary minimize downtime but require parallel systems. Rolling balances risk and complexity.
How much buffer should I plan for cutover?
Minimum 50% buffer (if plan says 60 min, schedule 90 min window). Complex migrations: 100% buffer. Murphy's law applies—something unexpected always happens. Larger buffer reduces pressure and prevents rushed decisions. Communicate worst-case timeline to stakeholders, not best-case.
When should I schedule the cutover window?
Lowest traffic period—typically 2-6 AM local time on weekends for B2C; Sunday 12-4 AM for B2B. Avoid: end of month (financial closes), holidays (limited support staff), major events (Super Bowl for sports betting apps). Consider global operations—'low traffic' for US may be peak for Asia.
What is the difference between migration and cutover?
Migration is the full process: planning, building new system, testing, data transfer. Cutover is the specific moment of switching traffic from old to new. Migration may take months; cutover takes hours. Cutover is the highest-risk phase requiring the most careful planning and the migration cutover window.
How do I validate migration success?
Validation steps: (1) Smoke tests (basic functionality works), (2) Data integrity checks (row counts match, checksums valid), (3) Performance tests (latency acceptable), (4) User acceptance testing (key workflows), (5) Monitoring (errors, latency, throughput). Define go/no-go criteria before cutover—objective tests, not gut feel.