Telecom operator · West Africa · 2026 · 3 months
The cutover window is not one night, it is a quarter
A telecom operator had to leave an aging infrastructure without stopping billing or provisioning. A single cutover would have concentrated all the risk on one night. The client wanted the opposite: short, reversible, observable steps.
We split the migration to Kubernetes into twenty cutovers, one per service, all reversible. Each cutover was rehearsed in pre-production, then executed in a window agreed with the client's teams. Three months separate the first cutover from the last.
3 months
from the first cutover to the last
20
cutovers, all reversible
0 min
of billable downtime