Scorecard · Cloud
Honest readiness score across 7 dimensions — workloads, identity, network, data, security, FinOps, skills — with the 90-day priorities to close the gaps before you lift-and-shift.
Most "failed" cloud migrations weren't failures in the cloud — they were failures of readiness. Teams move workloads before identity, network, and FinOps are ready, then spend 18 months fighting spend surprises and access chaos. This scorecard surfaces the gaps before you commit.
Out of 28. 22+ is ready — start migration waves. 15-21 is passable — remediate top-3 gaps before scaling. Below 15 means slow down: start with identity and network before any workload moves.
The three gaps that stall migrations most: identity (users can't get to workloads cleanly without a solid IdP), network (latency and cost blow up when MPLS hairpins cloud traffic through the DC), and FinOps (month 3 surprise bills drain executive sponsorship). Workload inventory with real dependencies saves the most time during wave planning — assume double the time you think if you don't have one. Data residency determines region selection and sometimes blocks SaaS outright. Skills gap is real but solvable with a partner on the first 2-3 waves.
No. For EoL hardware deadlines or DC exit dates, lift-and-shift buys time. Replatform/refactor in wave 2+ once FinOps signals are in.
Spend 90 days on identity (SSO + MFA), a connectivity design (SD-WAN + private peering), and an inventory pass before the first wave. You'll save 6 months downstream.
Score 18/28. Priorities: SCIM to Entra, SD-WAN ExpressRoute, CSPM (Defender for Cloud).
Score 12/28 pre, 21/28 six months in. Biggest lifts: Okta rollout, Megaport to AWS, tagging policy enforcement, CCoE stood up with partner.