Cloud Migration Readiness Assessment
Migrations overrun because the assessment covered infrastructure and skipped the two things that actually cause delay: undocumented application dependencies and a team that has never operated the target platform.
7 free templates
Migration assessments, tagging schemas, cost allocation sheets, and cloud governance checklists.
Each one is free as a print-ready PDF, and most include an editable CSV. One form unlocks the whole library.
Migrations overrun because the assessment covered infrastructure and skipped the two things that actually cause delay: undocumented application dependencies and a team that has never operated the target platform.
Cost optimisation reports identify savings that are never realised, because nobody owns the change and nobody verifies it landed. This tracker follows each opportunity to a confirmed reduction on the bill.
Untagged cloud resources make cost attribution guesswork and orphaned resources invisible. Tagging only works if it is enforced at creation. Retrofitting tags across thousands of resources is a project nobody finishes.
Cloud cost allocation stalls on shared services: the network, logging, and identity that nobody owns and everybody uses. Deciding the split rule in advance is what makes showback credible rather than a monthly argument.
Wave planning goes wrong when waves are grouped by team or by datacentre rack rather than by dependency. Applications that talk to each other must move together or tolerate the latency of being split, and that decision belongs in the plan.
Dependency maps built from interviews are wrong, because teams know what their application calls and rarely know what calls it. This one is built from observed traffic, with the interview used only to explain what you found.
Landing zone decisions are cheap before any workload exists and painful afterwards. Account structure in particular is close to irreversible once production is running, so it is worth deciding deliberately rather than discovering.