Score how ready an estate is for cloud and edge delivery, then estimate migration waves and elapsed months.
The three pillars are scored from coverage percentages you can gather from a CMDB, a pipeline audit and a skills survey, with operational readiness weighted highest because an unmapped dependency is what rolls a wave back. The wave count comes from raw application count, and the friction multiplier stretches the schedule as readiness falls — a 50-point estate takes half again as long per wave as a 100-point one. Migration plans slip because the wave schedule was drawn from application count alone, ignoring that low readiness makes every wave slower. The cacheable-traffic figure is the exception worth acting on immediately: putting a CDN in front of static content improves latency and origin load before a single workload is re-platformed.
Cloud Readiness Assessment
readiness = technical × 0.35 + operational × 0.40 + people × 0.25; waves = ceil(applications ÷ applications per wave); elapsed months = waves × weeks per wave × friction ÷ 4.345, where friction = 1 + (100 − readiness) ÷ 100.
readiness = technical × 0.35 + operational × 0.40 + people × 0.25; waves = ceil(applications ÷ applications per wave); elapsed months = waves × weeks per wave × friction ÷ 4.345, where friction = 1 + (100 − readiness) ÷ 100. The three pillars are scored from coverage percentages you can gather from a CMDB, a pipeline audit and a skills survey, with operational readiness weighted highest because an unmapped dependency is what rolls a wave back. The wave count comes from raw application count, and the friction multiplier stretches the schedule as readiness falls — a 50-point estate takes half again as long per wave as a 100-point one.
Migration plans slip because the wave schedule was drawn from application count alone, ignoring that low readiness makes every wave slower. The cacheable-traffic figure is the exception worth acting on immediately: putting a CDN in front of static content improves latency and origin load before a single workload is re-platformed.
This calculator takes 10 inputs: Applications in scope, Applications fully inventoried, Applications with mapped dependencies, Workloads already containerised, Infrastructure defined as code, Traffic that is cacheable static content, Engineers with hands-on cloud experience, Workloads with a cleared compliance path, Applications per migration wave, Weeks per wave. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.