Maximize Savings with the SolarWinds VM to Cloud Calculator: A Step‑by‑Step GuideMigrating virtual machines (VMs) from on‑premises infrastructure to the cloud can deliver cost savings, flexibility, and scalability — but only when you plan carefully. The SolarWinds VM to Cloud Calculator is designed to help IT teams estimate total cost of ownership (TCO), compare cloud providers, and identify where savings are possible. This step‑by‑step guide walks you through using the tool effectively and translating its results into an actionable migration plan.
Why use a VM-to-cloud calculator?
Migrating without a realistic cost model can leave you with unexpected bills, underutilized resources, or performance gaps. A VM-to-cloud calculator helps you:
- Estimate direct compute, storage, and network costs in public cloud providers.
- Compare on‑premises TCO vs cloud TCO over a chosen timeframe.
- Model reserved or committed discounts, autoscaling, and rightsizing opportunities.
- Identify the most cost‑effective cloud instance types and regions for your workloads.
- Quantify potential savings and produce data to support business decisions.
Before you start: gather data
Accurate inputs yield useful output. Collect the following for each VM or workload group:
- VM name or ID (for tracking)
- vCPU count and average CPU utilization (%)
- RAM size (GB)
- Provisioned disk type(s) and capacity (GB) and IOPS if applicable
- Average and peak network egress (GB / month)
- Operating system and licensing model (bring-your-own-license vs included)
- Required availability (SLA), redundancy, and backup needs
- Typical I/O patterns and performance requirements
- Expected growth rate and planned retention timeframe (1–5 years)
- Any compliance or geographic constraints (region, data residency)
Group similar VMs (by role, performance profile, OS, or sensitivity) to simplify modeling.
Step 1 — Choose timeframe and cloud provider assumptions
Set the analysis period (commonly 1, 3, or 5 years). Decide which cloud provider(s) you want to compare — AWS, Azure, GCP — and set assumptions such as:
- On‑demand vs reserved/spot instance usage
- Committed use discounts (e.g., AWS Savings Plans, Azure Reserved Instances)
- Licensing costs (Windows Server, SQL Server)
- Expected egress rates and regional pricing differences
Tip: run multiple scenarios (conservative, expected, aggressive) to capture a range of outcomes.
Step 2 — Input VM inventory into the calculator
Enter each VM or aggregated VM group into the SolarWinds VM to Cloud Calculator. Key fields typically include:
- vCPU and RAM
- Disk type and size (OS and data disks)
- Monthly network egress
- Average CPU utilization (affects right‑sizing recommendations)
- OS and license details
If the tool supports bulk upload (CSV/XLS), use it to save time and reduce manual errors.
Step 3 — Apply rightsizing and instance selection
The calculator will often suggest cloud instance types based on your inputs and utilization. Use the tool’s rightsizing recommendations to:
- Reduce vCPU and memory allocations where utilization is low
- Choose instance families optimized for compute, memory, or storage
- Consider burstable/spot instances for noncritical workloads
When applying rightsizing, validate any suggested reductions against performance SLAs and peak workload needs. Use a phased rightsizing approach: smaller rightsizes first, then monitor performance.
Step 4 — Factor in discounts and purchasing models
Cloud savings heavily depend on purchasing strategy:
- Reserved Instances / Savings Plans: commit 1–3 years to get steep discounts.
- Spot / Preemptible instances: great for stateless or flexible workloads.
- Committed use discounts (GCP) and Azure Hybrid Benefit can reduce licensing costs.
- Enterprise agreements and marketplace pricing differences.
Model at least two purchasing strategies (e.g., partial reserved + on‑demand mix) to see how commitment levels affect savings.
Step 5 — Include additional cloud costs
Don’t forget these often‑overlooked costs:
- Data egress and cross‑region transfer charges
- Backup, snapshot storage, and long‑term archival
- Load balancers, NAT gateways, and managed services (RDS, managed Kubernetes)
- Monitoring, security services, and logging (these scale with usage)
- Migration costs (data transfer, replatforming, consulting)
Add estimates for these to avoid underestimating TCO.
Step 6 — Run sensitivity and scenario analysis
Use the calculator to run multiple scenarios:
- Base case (expected utilization and a moderate commitment)
- Optimistic (aggressive rightsizing, high reserved commitment)
- Pessimistic (high growth, minimal reservations)
Compare results to understand which assumptions drive the biggest cost changes (usually compute commitment levels, data egress, and storage tiering).
Step 7 — Interpret results and identify savings levers
Key outputs to review:
- Projected monthly and annual costs (on‑prem vs cloud)
- Breakdowns by compute, storage, network, and licensing
- Recommended instance types and right‑sizing changes
- ROI and payback period for migration costs
Major levers for savings:
- Rightsizing underutilized VMs
- Using reserved or committed pricing
- Moving to appropriate storage tiers (hot vs cool vs archive)
- Reducing data egress through architectural changes (caching, compression, region placement)
- Consolidating workloads to fewer, larger instances or leveraging containers/Kubernetes
Step 8 — Validate with a pilot migration
Before migrating everything:
- Pick a representative set of workloads for a pilot.
- Apply rightsizing and purchasing strategies from the calculator.
- Run performance and cost monitoring for 30–90 days.
- Compare real cloud bills and telemetry to the calculator’s estimates and refine inputs.
Pilots surface hidden costs (e.g., higher egress than expected, licensing surprises) and help build confidence with stakeholders.
Step 9 — Operationalize savings
To lock in savings after migration:
- Implement tagging and cost allocation to track spend by team, app, or environment.
- Use autoscaling and scheduled on/off for nonproduction environments.
- Monitor utilization and enforce size right‑sizing periodically.
- Reevaluate reserved/commitment purchases quarterly as usage patterns change.
- Automate cleanup of orphaned disks, snapshots, and idle resources.
Common pitfalls and how to avoid them
- Underestimating egress and managed service costs — track past network usage and include realistic buffers.
- Over‑optimistic rightsizing — validate in production-like conditions.
- Ignoring licensing nuances — confirm vendor licensing rules for cloud deployments.
- One‑time migration costs omitted — include data transfer, refactoring, and training.
- Not planning governance — without tagging and chargeback, savings get lost.
Example summary (concise)
- Typical savings often come from rightsizing and reserved/committed pricing.
- Include network, managed services, and migration costs to avoid surprises.
- Validate with a pilot and continuously monitor to preserve savings.
If you want, I can:
- Create a checklist you can use to collect inventory data, or
- Build example CSV templates for bulk import into the calculator.