Replication runs 24/7 until cutover
AWS Transform MGN Pricing Calculator
Estimate replication server compute and staging storage for each migration wave before the first replication job starts.
- No signup
- Instant results
- ~3 min
Rates reviewed
Read the full breakdown — Companion pricing guide covers billing dimensions, traps, and a 30-day cleanup plan.
Migration wave profile
us-east-1list rates, pricing as of 2026-10-20. Landing zone, VPN/Direct Connect, and target environment runtime are excluded. Source: AWS public pricing.
Replication and staging profile
Estimated MGN Cost
Monthly migration wave estimate
Total Monthly Cost
live resultCost per server and shorter-window savings unlock after email.
Unlock Migration Cost Breakdown
See cost per server and cutover window impact.
Full breakdown unlocked
Migration optimization guidance is now visible.
Want this applied to your real account?
FactualMinds plans migration waves that minimize replication overlap and shrink staging time without increasing cutover risk.
Explore AWS Migration Services →Who This Tool Is For
IT directors and migration leads estimating lift-and-shift wave cost before locking cutover dates.
Why We Built This Tool
Migration replication servers run continuously, and long parallel-run windows can dominate migration spend.
What Problem It Solves
- Replication overhang. Delayed cutovers keep compute and staging storage running for weeks.
- Wrong staging media. SSD staging on low-change workloads overpays versus HDD options.
- No cost-per-server baseline. Program teams lose forecast precision without a per-wave unit cost.
Frequently Asked Questions
What costs are included for AWS Transform MGN here?
AWS renamed Application Migration Service (MGN) to AWS Transform MGN in June 2026; pricing works the same way. This estimate covers replication server compute, staging storage, and the MGN service fee. Each source server gets 2,160 free hours (90 days), then $0.042 per hour. Replication into AWS is inbound data transfer, which AWS does not charge for.
Does this include target EC2 runtime after cutover?
No. This calculator covers migration-period replication costs only.
How can I reduce MGN cost quickly?
Shorten replication windows, batch cutovers by readiness, and avoid oversized replication servers.
Should I use gp3 or st1 for staging?
gp3 is faster but more expensive. st1 can be sufficient for cost-sensitive waves with lower I/O pressure.
Why show cost per server?
Per-server unit cost makes migration wave budgeting and stakeholder communication much easier.
Are these exact billing numbers?
Use this as a planning model. Actual billing changes with real replication throughput and instance sizing.
