A transparent pricing guide for cloud migration based on 500+ projects we have delivered. Real numbers, not marketing ranges — $10K–$40K for simple builds, $200K–$300K+ for enterprise scale.
| Tier | Price Range | Timeline | Best For |
|---|---|---|---|
| Basic / Lift-and-Shift | $10K–$40K | 4–8 weeks | Move existing workloads to cloud VMs with minimal changes. Basic networking and security setup. |
| Re-Platforming | $40K–$120K | 8–18 weeks | Migrate to managed services (RDS, ECS), containerization, updated CI/CD, and monitoring. |
| Cloud-Native Refactoring | $120K–$200K | 18–32 weeks | Decompose monolith into microservices, serverless, event-driven architecture, auto-scaling. |
| Enterprise Migration | $200K–$300K+ | 6–12 months | Multi-cloud strategy, compliance (FedRAMP, HIPAA), disaster recovery, and zero-downtime migration. |
Same infrastructure: 30 VMs, 2 databases, 5 TB storage, moderate traffic. Indicative 2026 numbers including people time.
~$250K–$450K over 3 years including hardware, DC space, power, and 1 FTE sysadmin. Wins for stable, predictable workloads with strict data-residency rules.
$10K–$40K migration + ~$15K–$35K/mo cloud run rate + ongoing FinOps tuning. 3-year TCO is usually 10–25% higher than on-prem unless you right-size aggressively within 6 months.
$40K–$120K migration + ~$8K–$20K/mo run rate after tuning. Pays back in 12–20 months vs on-prem when growth is >20%/yr and elasticity matters. Best common option for mid-sized teams.
$120K–$300K+ upfront, $5K–$15K/mo steady state at moderate scale. Break-even is 2–4 years; justified when the app needs rapid horizontal scale or fault tolerance that on-prem cannot match.
Quick answer: Cloud migration costs $10,000–$300,000+ depending on infrastructure complexity, data volume, and compliance requirements. A simple lift-and-shift migration costs $10K–$40K. A re-platforming project runs $40K–$120K. Full cloud-native modernization costs $120K–$300K+. Want a tailored estimate? Talk to us →
A single monolithic app is simpler to migrate than a distributed system with 20+ services, multiple databases, and legacy dependencies. Complexity can double migration costs.
Migrating 100 GB is quick. Migrating 10+ TB requires transfer acceleration, data validation, and potentially physical data transfer — adding $10K–$30K.
Scheduled-downtime migrations are 40–60% cheaper. Zero-downtime migrations require blue-green deployment, data sync, and rollback planning, adding $15K–$40K.
HIPAA, PCI, or FedRAMP compliance in the cloud requires specific configurations, encryption, and audit trails — adding $15K–$40K.
Same-engine migration (PostgreSQL to RDS) is simpler. Cross-engine migration (Oracle to PostgreSQL) requires schema conversion and query rewriting — $10K–$35K.
Training your team on cloud services, IaC, and new deployment workflows costs $5K–$15K but prevents long-term operational issues.
Infrastructure audit, dependency mapping, cloud architecture design, cost modeling
VPC, networking, IAM, security groups, IaC (Terraform/CloudFormation)
Workload migration, database migration, data transfer, configuration
Functional testing, performance testing, security validation, failover testing
DNS cutover, monitoring setup, cost optimization, documentation
Practical steps we use with clients to control scope and spend.
Plan for discovery, a realistic MVP, and a 15–20% contingency before you lock a number for cloud migration. Scope changes and integrations are where estimates drift — we help you sequence work so you fund value in the right order.
Ranges reflect a re-platforming migration: ~30 VMs, 2 databases, 5 TB data, move to managed services (RDS, ECS/EKS), IaC, monitoring, and updated CI/CD.
| Vendor Type | Typical Cost | Timeline | Risk Profile |
|---|---|---|---|
| Cloud vendor Professional Services (AWS/GCP/Azure) | $50K–$150K | 3–7 months | Low on cloud expertise, high on vendor lock-in bias — guidance optimized for the home cloud, not multi-cloud flexibility |
| Big 4 consultancy (Accenture, Deloitte, IBM) | $150K–$500K+ | 6–12 months | Low on delivery risk, very high on cost — heavy PMO overhead; often subcontracts build to offshore teams |
| Boutique cloud specialist (ZTABS tier) | $60K–$180K | 3–7 months | Low — senior cloud engineers, Terraform/IaC standard, FinOps tuning in-house, vendor-agnostic advice |
| Offshore systems integrator (IN/PH/UA) | $40K–$120K | 5–10 months | Medium — cost advantage offset by timezone friction during cutover and weaker on right-sizing after migration |
| In-house lift (existing ops team + vendor training) | $30K–$100K training + 6–12 months FTE time | 6–14 months | High — under-trained teams over-provision 30–50%; cloud bill balloons within 12 months without FinOps discipline |
Ranges are 2026 US-buyer benchmarks; ongoing cloud run costs ($5K–$35K/mo depending on workload), post-migration right-sizing (typically 2–4 months of tuning), and parallel-running costs during cutover run separately. Compliance layers (HIPAA, FedRAMP, PCI) add $15K–$40K regardless of vendor.
Honest scenarios where the numbers above are the wrong benchmark for your situation.
Moving stable, fully-depreciated hardware to the cloud often raises 3-year TCO by 20–40%. The case for migration is weakest when capacity is not constrained and the app is not growing. Wait for a hardware refresh cycle or a capacity crunch.
A VM-to-VM lift of a monolith with heavy inter-service traffic often costs more in the cloud than on-prem because of egress and cross-AZ fees. Plan to re-platform or refactor at the same time, or expect to pay more for the same app.
A $60K migration handed to an untrained ops team becomes a $200K/yr AWS bill from mis-provisioned resources within 12 months. Budget team training ($5K–$20K) and a 3–6 month managed-ops arrangement, or stay on-prem until the skills exist.
Full migrations are overkill when one batch job or GPU training run needs elasticity. Hybrid options (cloud bursting, dedicated GPU providers like RunPod or Lambda Labs) often solve the real problem for $5K–$15K without touching the rest of the stack.
Real build-vs-buy options with pricing signals and the honest gotcha each one carries.
| Alternative | Best For | Pricing Signal | Biggest Gotcha |
|---|---|---|---|
| Lift-and-shift (VM-level rehost to AWS/Azure/GCP) | Data-center exit under deadline, minimal app refactor tolerance, 50–500 VMs | $10K–$80K assessment + $40K–$200K execution at $120–$220/hr | Cloud bill post-migration is usually 20–40% higher than on-prem TCO because VM-sized workloads do not use cloud-native economics. |
| Re-platforming (move to managed services — RDS, ECS, GKE) | Teams with cloud-native skills, 12–18 month migration window, want TCO improvement | $40K–$250K over 16–30 weeks at $130–$230/hr | Managed service feature gaps. Aurora lacks some Postgres extensions; switching back is a 2-month rebuild. Validate extensions/features before committing. |
| Cloud-native refactor (microservices, serverless, containers) | Long-term strategic investment, product-aligned engineering, 2+ year horizon | $150K–$500K+ over 30–60 weeks at $140–$250/hr | Distributed systems complexity. Without observability (Datadog, Honeycomb) + SRE maturity, microservices slow delivery 30–50% vs. the monolith. |
| Stay on-prem / hybrid | Predictable workloads, data residency requirements, existing capex amortization | Hardware refresh $200K–$2M every 4–5 years + DC operating costs | On-prem hides real TCO (facilities, power, DR, staffing). A proper 5-year TCO model usually shows cloud-native within 10–15% of on-prem — but without elasticity. |
Client split app (cloud) and DB (on-prem DC). AWS egress bill hit $18K/mo in month 3 because every read query pulled data cross-zone. Total cost of hybrid was 2.4× what a full-cloud option would have been.
Lift-and-shift to RDS used default param group; client Postgres had custom work_mem and max_connections. Prod fell over at peak traffic on day 2. Spent 3 days reconciling params; $14K of overtime + lost revenue.
Client bought 3-year RIs at month 6 to save 40%. Six months later, refactored to Lambda and the RIs sat idle. $84K written off. Never commit RI/SP beyond what rolling 3-month usage actually sustains.
Share your goals and timeline — we will map scope, options, and a clear investment range.
Get a free consultation