Checklist · free
VMware exit readiness checklist
For IT and finance leaders facing a VMware renewal, a datacenter exit or a hardware refresh: what to confirm before you commit to Azure, a renewal or a hybrid path.
Drivers and decision
| # | Question | Why it matters |
|---|
| 1 | Which date is driving the decision (renewal, lease end or hardware refresh), and is it fixed? | The deadline sets how much you can assess before you must act. |
| 2 | Are your VMware, datacenter and hardware support dates listed in one place? | A forgotten date can force a rushed decision. |
| 3 | Who must approve the platform decision and the business case? | Late approvers can reopen settled choices. |
| 4 | What would success look like 12 months from now? | A clear goal keeps cost, risk and speed in balance. |
Inventory and dependencies
| # | Question | Why it matters |
|---|
| 5 | Do you have a verified count of VMs, hosts and clusters, from tools rather than spreadsheets? | Estates usually grow faster than their documentation. |
| 6 | Have you collected performance data over a representative period (at least two weeks)? | Sizing from allocated capacity, not actual use, inflates every option. |
| 7 | Are dependencies between applications, databases and data feeds mapped? | Undocumented dependencies break cutovers. |
| 8 | Does each application have a named owner who can approve its move? | Without an owner, testing and sign-off stall. |
| 9 | Do you know your SQL Server instances, versions and operating system support dates? | Out-of-support systems limit where workloads can go. |
Options and business case
| # | Question | Why it matters |
|---|
| 10 | Have you compared renewing, moving to another on-premises platform, moving to public cloud and a mix, on the same cost and risk basis? | A fair comparison stops the deadline from making the choice for you. |
| 11 | Have you decided, per application, whether to rehost, replatform, refactor, retire or keep it where it is? | Not everything should move, and some things should be retired. |
| 12 | Do you have a cost baseline for today's datacenter and platform? | A business case needs a real starting point. |
| 13 | Is any cloud cost estimate based on measured sizing data? | Estimates built on guesses erode trust in the case. |
| 14 | Have you confirmed current VMware licensing terms for your renewal with your vendor or reseller? | Licensing and packaging have changed in recent years; check before you plan. |
Target platform readiness
| # | Question | Why it matters |
|---|
| 15 | If you already use the cloud, is it governed (identity, policy, network, tagging) before more workloads land? | Moving into an ungoverned foundation adds risk and rework. |
| 16 | Are network bandwidth, latency, DNS and private connectivity (dedicated circuit or VPN) planned, with circuit lead times known? | Connectivity delays often set the real start date. |
| 17 | Do you know which workloads depend on Active Directory or other identity services? | Identity dependencies break sign-in after a move. |
| 18 | Are recovery time and recovery point targets set per application, with a backup plan for the target platform? | Backup and recovery must work on day one, not later. |
Migration approach
| # | Question | Why it matters |
|---|
| 19 | Will a pilot wave of low-risk workloads go first? | A pilot proves the method before critical systems move. |
| 20 | Does every cutover have a test migration and written rollback criteria? | Rollback decided in the moment is rollback done badly. |
| 21 | Are cutover windows, owner sign-off and a support period after each wave agreed? | Users judge the move by the first week after it. |
| 22 | Who owns decommissioning the old platform and the related contract decisions? | Paying for both platforms erodes the savings. |
How to read your result
- Mostly "yes": you are ready to compare options and commit.
- Gaps in Inventory and dependencies: fix those first. Every option depends on them.
- Gaps in Options and business case: you may be about to let the renewal date decide for you.
- Gaps only in the last two sections: plan the foundation and the pilot before the first wave.
If you found gaps, especially in inventory or the business case, contact Kalosys today, before the renewal date decides for you. Your note goes straight to our Microsoft practice.
