Free DIY Resource • Server & Cloud Migration Planning
Server-to-Cloud Migration Checklist: 4 Checks You Can Run Yourself Today
Servers don't fail politely. When yours goes, you're either signing off on another expensive hardware refresh or scrambling to migrate under pressure, on someone else's timeline instead of yours. Here's what's actually at stake, a few blind spots most teams miss, and four checks you can run yourself in under an hour.
A migration doesn't have to be a fire drill. Most of the risk comes down to a handful of things nobody's checked recently: how old the hardware actually is, whether the backups would really restore, whether anyone's mapped what depends on what. None of the four checks below need a migration project plan, just access to your environment and about an hour.
What's At Stake
- Sinking six figures into hardware that's already outdated within five years, with no plan for what comes next.
- A forced, unplanned migration once a server fails outright, on someone else's timeline instead of yours.
- A cloud bill that arrives as a surprise instead of a number you budgeted and understood in advance.
Other Blind Spots
- Licensing or compliance terms that don't carry over cleanly once workloads move to the cloud.
- Dependencies between servers that exist only as institutional knowledge, undocumented anywhere.
- Backup and rollback plans that have never actually been tested end to end.
4 Checks You Can Run Yourself Today
0 of 4 complete
-
Inventory every server and workload you're running. You can't plan a migration, or even know what's at risk, if half your environment is undocumented and nobody remembers setting it up. Walk your network switch by switch, cross-reference against your asset list, and flag anything unaccounted for.
-
Check each server's age against the vendor's end-of-support date. A server past its end-of-support date stops receiving security patches, whether or not it's still running fine today. Cross-reference each model and serial number against the manufacturer's published support lifecycle page.
-
Confirm your backups actually restore, not just that they run on schedule. A backup job completing successfully tells you nothing about whether the data inside it is actually usable. Pick one non-critical system, run a full test restore to a separate environment, and confirm the data opens correctly.
-
Get real cloud pricing for your actual workloads before assuming a refresh is cheaper. Generic cloud cost calculators routinely miss egress fees, storage tiers, and licensing, and the real number often surprises people in both directions. Use the CPU, memory, and storage numbers from step one to get a quote based on how your workloads actually run, not a rough estimate.
Common Questions
Do I need to migrate everything to the cloud, or can some servers stay on-premises?
Not everything needs to move. A hybrid approach, cloud for some workloads and on-premises for others, is common and often the right call depending on compliance requirements, latency needs, and existing hardware investment. The point of this checklist is knowing your real options, not getting pushed toward the cloud by default.
How do I know if a server is actually at end-of-support?
Check the manufacturer's published lifecycle page using the exact model and serial number, not just the purchase date. Vendors sometimes extend or shorten support windows after a product ships, so the sticker on the box isn't always current.
What's the difference between this checklist and a full migration assessment?
This checklist surfaces the handful of risks that turn a planned migration into an unplanned one: undocumented infrastructure, untested backups, and pricing assumptions that don't hold up. A full assessment goes further, mapping every dependency and building an actual migration sequence and timeline.
Is cloud always cheaper than keeping servers on-premises?
Not always. It depends heavily on your actual usage patterns, and a workload that runs constantly at high utilization can sometimes cost more in the cloud than on owned hardware. That's exactly why getting real pricing against your actual workloads (step 4 above) matters more than a rule of thumb.
How often should I re-run this checklist?
Revisit it annually at minimum, and any time you're evaluating a hardware refresh, onboarding a new MSP, or going through a merger or acquisition that brings unfamiliar infrastructure into the mix.