Cloud Migration Costs in the USA: A Budgeting Guide

Why Cloud Migration Budgets Fail

A 2024 Gartner survey found that more than half of US enterprise cloud migrations exceeded their initial budget, and the pattern repeats year after year. The reason is almost never compute pricing — it is the cost categories that do not appear in a hyperscaler's pricing calculator: labor for application re-architecture, data egress from legacy hosting, extended parallel-run periods, and the optimization work that happens in the six months after go-live.

This guide is for US IT leaders and CFOs building a credible cloud migration budget — one that will survive a board-level review and not require a surprise addendum six months after cutover.

The Five Cost Buckets That Drive Every Migration

1. Assessment and Planning

The discovery phase is the most underbudgeted line item in most migration plans. A thorough application portfolio assessment — cataloging every workload, its dependencies, its data residency requirements, and its target state (rehost, replatform, refactor, retire) — takes weeks for a mid-sized US business and often requires specialist tooling (AWS Migration Hub, Azure Migrate, or third-party platforms like Cloudamize or Movere).

For a business with 50–200 servers, budget $15,000–$60,000 for a professional-grade discovery and dependency-mapping exercise before the first workload moves. Skipping or compressing this phase is the leading cause of migration cost overruns because hidden dependencies surface at the worst possible moment — during cutover.

2. Direct Cloud Infrastructure Costs

This is the number most teams compute first, and it is the least likely to surprise them. The key variables:

• Right-sizing gap: On-premises servers are typically provisioned at peak capacity and run at 10–25% average utilization. A direct lift-and-shift without right-sizing replicates that waste in the cloud at pay-per-use pricing. Right-sizing analysis before migration is not optional — it is how you achieve the cost reduction the business case promised.
• Reserved vs. on-demand: One-year reserved instances on Azure and AWS typically cost 30–40% less than on-demand. Three-year reservations push savings to 50–60%. The break-even point for committing depends on workload stability; variable or experimental workloads should stay on-demand or use savings plans.
• Storage tiers: Hot, cool, and archive storage pricing varies 5–10x between tiers. Data that has not been accessed in 90 days rarely needs to sit in hot storage. Lifecycle policies applied at migration can cut storage bills by 30% or more without any application changes.

3. Data Transfer and Egress Costs

This is where the first major budget surprise usually lands. Ingressing data into a cloud provider is free or near-free. Moving data out — whether to users, to another cloud, or back on-premises — is not. AWS and Azure both charge $0.08–$0.09 per GB for standard egress; Google Cloud is lower. For a US business migrating 100 TB of data, the ongoing egress cost for a data-intensive workload can run $8,000–$10,000 per month and must be modeled before committing to a platform.

Physical data transfer via AWS Snowball, Azure Data Box, or Google Transfer Appliance is cost-effective for initial migrations of multi-terabyte datasets — at scale it is nearly always cheaper than transferring over the public internet, and it avoids saturating the business's internet connection during migration.

4. Application Modernization and Re-Architecture Labor

This is consistently the largest and most variable budget category. A pure rehost (lift-and-shift) of a well-understood application costs dramatically less than a refactor to a cloud-native architecture — but also delivers less long-term value. US labor rates for senior cloud architects and DevOps engineers run $140–$220/hour for consulting engagements. A meaningful modernization project for a mid-market business with 10–20 applications can run $200,000–$800,000 in professional services alone.

The architectural decision — rehost vs. replatform vs. refactor — is fundamentally a financial decision that should be made with the CFO in the room, not just the CTO.

5. Post-Migration Optimization and Operations

Most migration budgets end at go-live. In practice, the first 90–180 days after cutover are when significant optimization work happens: shutting down zombie resources, right-sizing instances based on real utilization data, moving data to appropriate storage tiers, and fixing reserved-instance commitments. Budget 15–25% of year-one cloud spend for this optimization phase. Businesses that skip it typically overpay on cloud by 30–40% in year one.

A Rough Budget Framework by Business Size

Business Size	Server Count	Typical Migration Budget Range	Primary Cost Driver
Small (under 50 employees)	5–20	$20,000–$80,000	Labor and licensing
Mid-market (50–500 employees)	20–200	$100,000–$600,000	Re-architecture labor and data transfer
Enterprise (500+ employees)	200+	$500,000–$5M+	Application modernization and governance

These ranges assume a hybrid rehost-and-replatform approach typical of US mid-market migrations. Pure lift-and-shift costs land at the lower end; full application refactoring at the upper end or beyond.

Costs That Appear After the Budget Is Approved

Several cost categories consistently appear as surprises in post-migration retrospectives with US clients:

• Extended parallel run: When legacy and cloud environments run simultaneously during cutover, you pay for both. Parallel runs that were planned for two weeks often stretch to six or eight, doubling that line item.
• Third-party licensing: Many ISV licenses are tied to physical cores or MAC addresses. Moving to virtual or cloud instances may trigger re-licensing fees that are not covered by cloud provider migration credits.
• Security and compliance tooling: Cloud environments require new or reconfigured SIEM, vulnerability scanning, and compliance monitoring tools. These costs are rarely in the initial migration budget.
• Training: Staff who managed on-premises infrastructure need cloud operations training. Budget for certifications, hands-on labs, and the productivity dip during the learning curve.

Migration Credits and Funded Programs

All three major cloud providers offer funded migration programs for US businesses: Azure Migrate and Modernize credits, AWS Migration Acceleration Program (MAP) funding, and Google Cloud's migration incentives. These programs can offset $20,000–$150,000 in migration costs for qualifying workloads. Access is typically through a certified migration partner, not directly — another reason to engage an experienced MSP early in the process.

GR IT Services helps US businesses build realistic cloud migration budgets and access available migration funding programs. Contact us at inquiry@gritservices.io to discuss your migration scope.