Software Modernization Costs

Costs vary enormously by scope and domain. A targeted database migration (e.g., Oracle to PostgreSQL) can cost $25K–$1M. A full mainframe modernization program runs $2M–$15M+. The median across all modernization types is roughly $450K–$2.3M depending on codebase size, technical debt, and team readiness. Use the domain sections on this page for project-specific benchmarks.

Cloud migrations typically take 6–18 months. Simple rehost (lift-and-shift) migrations complete in 3–6 months. Replatform projects run 6–12 months. Full refactor or re-architect programs take 12–24+ months. Data gravity - the time needed to move large datasets - is the most common timeline surprise that extends projects beyond initial estimates.

Three factors drive mainframe cost above all others: (1) COBOL expertise is scarce - qualified developers command $150K+/year and booking lead times can exceed 12 months. (2) Mainframe logic is deeply embedded in batch sequences and VSAM file structures, not discrete services - you cannot lift individual components. (3) Financial calculation equivalence testing is mandatory - you must prove bit-for-bit identical outputs across all code paths. A 1M LOC COBOL codebase typically costs $1.5M–$4M and takes 18–36 months.

The five biggest cost drivers are: (1) Codebase size - measured in LOC for backend systems, forms/screens for desktop apps, and schema count for databases. (2) Technical debt density - undocumented dependencies, hardcoded configuration, missing test coverage. (3) Data complexity - stored procedure count, data volume, and the rigor required for migration validation. (4) Team readiness - whether your internal team can own the new architecture post-migration or requires extended vendor support. (5) Vendor tier - boutique specialists cost less per hour but have capacity limits; enterprise SIs charge premium rates but provide risk transfer and contractual SLAs.

Rehost is 30–50% cheaper upfront but generates higher cloud costs because unoptimized workloads typically run 40% more expensive in the cloud than their optimized equivalents. Refactor has a higher day-1 cost but generates ongoing savings. The decision depends on cloud bill scale: if you are spending less than $500K/year on cloud, the refactor ROI rarely justifies the cost difference. Above $1M/year in cloud spend, refactoring typically breaks even within 18–24 months.

Use the median cost for your migration type as your baseline, then add: 20% contingency for unknowns discovered during discovery (dependency audits almost always reveal surprises), 10–15% for testing and validation (the most chronically underbudgeted line item in modernization projects), and 10% for change management and training. Always include a knowledge transfer budget - if your vendor leaves and no one on your team understands the new system, you will spend the modernization cost again to recover.

Cloud migrations break even in 18–24 months through infrastructure savings and licensing cost reductions. Database migrations from Oracle or Teradata to open-source platforms break even faster - often 12–18 months - because licensing savings begin immediately. Mainframe modernizations have the longest ROI horizon (3–5 years) due to high upfront costs, but deliver the largest long-term savings: mainframe operations typically cost 3–5× equivalent cloud infrastructure per workload.

All cost ranges are derived from analysis of verified modernization engagements. Median costs reflect actual project outcomes where data was available. Ranges reflect real variance - the difference between a $25K and $1M Oracle migration is real and driven primarily by stored procedure complexity and data volume, not vendor margin. Use this data for order-of-magnitude budgeting and vendor conversation framing, not for fixed-price contracting.