"We should move to the cloud" is easy to say. But when a portfolio company's leadership team proposes a $2M cloud migration project, PE firms need hard ROI numbers—not vague promises about "scalability" and "flexibility."
Here's how to actually calculate cloud migration ROI, including the costs and benefits that most people miss.
The True Cost of Cloud Migration
Most cloud migration business cases dramatically underestimate total costs. Here's what to actually include:
One-Time Migration Costs:
- Application refactoring and modernization
- Data migration and validation
- Testing and quality assurance
- Training and change management
- Third-party consulting/integration partners
Ongoing Operational Changes:
- Monthly cloud infrastructure costs (compute, storage, networking)
- New tooling and monitoring platforms
- Cloud expertise hiring or training
- Increased bandwidth and connectivity costs
The Hidden Benefits That Justify the Investment
Now for the returns. Most business cases focus only on infrastructure cost savings, but the real value is elsewhere:
1. Reduced Time-to-Market (The Big One)
This is where cloud delivers outsized returns. On-premise infrastructure requires weeks or months to provision new environments. Cloud infrastructure provisions in minutes. For portfolio companies trying to launch new products or enter new markets fast, this acceleration is worth millions.
2. Eliminated Capital Expenditures
On-premise data centers require 3-5 year hardware refresh cycles with significant capital outlays. Cloud converts this to predictable operating expenses, improving cash flow and balance sheet metrics that matter at exit.
3. Scalability Revenue Enablement
Companies with on-premise infrastructure often can't scale fast enough to capture market opportunities. Cloud infrastructure scales with demand, removing growth ceiling limitations. This directly impacts revenue projections.
4. Disaster Recovery & Business Continuity
Building proper DR/BC on-premise costs $500K+. Cloud providers include geo-redundancy and automated failover as standard features. This dramatically reduces risk and insurance costs.
5. Security & Compliance
Enterprise customers increasingly require SOC 2, HIPAA, or other certifications. AWS/Azure/GCP already have these certifications, dramatically reducing time and cost to achieve compliance. This unlocks enterprise revenue faster.
The ROI Calculation Framework
Here's the actual formula we use with PE firms:
(Revenue Acceleration × 3 Years) +
(Operational Cost Savings × 3 Years) +
(CapEx Avoidance) +
(Exit Multiple Improvement) -
(One-Time Migration Costs) -
(Increased OpEx × 3 Years)
Example: $50M ARR SaaS Company
- Revenue acceleration: Faster product launches = $2M additional ARR/year = $6M over 3 years
- Operational savings: Reduced IT headcount, no hardware refresh = $400K/year = $1.2M
- CapEx avoidance: No $1.5M data center upgrade
- Exit multiple: Improved operational profile adds 0.5x revenue multiple = $25M value at exit
- Migration costs: -$1.2M one-time
- Increased cloud spend: -$600K/year net = -$1.8M over 3 years
Net 3-Year Value: $30.7M
That's a 25x return on the initial migration investment—driven primarily by revenue acceleration and exit value improvement, not infrastructure cost savings.
When Cloud Migration Makes Sense
Not every portfolio company should migrate immediately. Cloud makes most sense when:
- Growth trajectory requires rapid scaling (50%+ annual growth)
- Company is targeting enterprise customers requiring compliance certifications
- Product roadmap includes rapid feature velocity and new market entry
- Current infrastructure is approaching end-of-life refresh cycles
- Company plans to integrate acquisitions onto unified platform
Cloud makes less sense when:
- Stable, mature business with minimal growth and no M&A plans
- Highly regulated environment requiring on-premise data storage
- Recently refreshed infrastructure with 3+ years of useful life
- Applications require extensive refactoring with no business case for modernization
The Timeline Reality
Most cloud migrations take longer than projected. Budget for:
- Simple migration (lift-and-shift): 6-9 months
- Moderate refactoring: 9-15 months
- Full modernization: 15-24 months
The complexity of your portfolio company's application architecture, data dependencies, and integration requirements will determine which bucket they fall into.
The question isn't "can we afford to migrate?" It's "can we afford not to?"