Cloud Readiness Assessment Calculator
Score how ready an estate is for cloud and edge delivery, then estimate migration waves and elapsed months.
About Cloud Readiness Assessment Calculator
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.
Formula
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.
- technical readiness
- Containerisation, infrastructure-as-code and cacheable traffic share
- operational readiness
- Inventory, dependency mapping and a cleared compliance path
- friction
- Schedule multiplier that grows as readiness falls, up to 2× at zero readiness
Worked example
With the default values below, Cloud Readiness Assessment Calculator returns Cloud Readiness Score of 52.8. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Applications in scopeaccepts 1–100,000 applications
- 120 applications
- Applications fully inventoriedaccepts 0–100 %
- 70 %
- Applications with mapped dependenciesaccepts 0–100 %
- 55 %
- Workloads already containerisedaccepts 0–100 %
- 35 %
- Infrastructure defined as codeaccepts 0–100 %
- 45 %
- Traffic that is cacheable static contentaccepts 0–100 %
- 55 %
- Engineers with hands-on cloud experienceaccepts 0–100 %
- 50 %
- Workloads with a cleared compliance pathaccepts 0–100 %
- 65 %
- Applications per migration waveaccepts 1–500 applications
- 12 applications
- Weeks per waveaccepts 0.5–52 weeks
- 4 weeks
Results
- Cloud Readiness Score
- 52.8 / 100
- Grade
- D — Weak
- Technical Readiness
- 43.0 / 100
- Operational Readiness
- 63.0 / 100
- People Readiness
- 50.0 / 100
- Traffic Movable to the Edge Immediately
- 55.0%
- Migration Waves
- 10
- Estimated Elapsed Time
- 13.6 months
- Do This First
- Raise infrastructure-as-code coverage and containerise the next wave's workloads
Step by step
- 1Values used
- 2Cloud Readiness Assessment
- 3Cloud Readiness Score= 52.8 / 100
- 4Grade= D — Weak
- 5Technical Readiness= 43.0 / 100
- 6Operational Readiness= 63.0 / 100
- 7People Readiness= 50.0 / 100
- 8Traffic Movable to the Edge Immediately= 55.0
Assumptions and limits
- The result is derived only from the 10 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax or compounding frequency into account.
- Figures are rounded for display to 1 decimal place, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
How is Cloud Readiness Assessment calculated?
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.
Why does Cloud Readiness Assessment matter?
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.
What values do I need to enter?
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.