By The Refresh Quote Test: When a Federal Cloud Migration Pays for Itself
A five-year model of a 30-application federal migration shows a $2.23M difference in the agency's favor, payback in Year 2, and one scenario where the case disappears: no refresh or licensing event inside the window.
A hardware refresh quote is often the first honest total-cost number leadership sees for a legacy environment. It is also the best moment to price the alternative. Across government, agencies put about 80 percent of more than $100 billion in annual IT spending into operating and maintaining existing systems (opens in a new tab), so every refresh cycle renews that ratio for another five years.
Avalon built an illustrative five-year model to show when a migration beats the refresh (opens in a new tab) and when it does not. It is a planning illustration for a representative portfolio, not a quote and not a result from any agency.
The Portfolio and the Two Cost Paths
The model covers 30 unclassified applications. Disposition workshops retire 4, move 3 to SaaS, rehost 12, replatform 8, refactor 2, and retain 1 on premises.
The status quo runs at $3.40M a year: 10 sustainment FTEs at $165K fully loaded, $600K in hosting and facilities, $250K in hardware maintenance, and $900K in virtualization, OS, and database licensing. A $2.40M hardware refresh lands in Year 1.
The migration path replaces that with a $2.79M annual run cost from Year 2. Sustainment drops to 6 FTEs, cloud consumption for the 22 migrated applications runs $1.10M, and virtualization licensing goes away.
What It Costs to Get There
Avalon's services for this portfolio total $2.04M, inside the $900K to $3M band typical for a mid-size migration:
| Component | Price |
|---|---|
| Fixed-price assessment and migration plan | $85K |
| Landing zone validation, pilot wave setup, evidence packaging | $210K |
| Rehost waves (12 applications at $40K) | $480K |
| Replatform waves (8 applications at $95K) | $760K |
| Targeted refactor, T&M ceiling (2 applications at $250K) | $500K |
The agency carries its own $800K in Year 1 program costs: PMO, ISSO, and test staff time, reassessment of the new boundary, decommissioning, and a maintenance bridge on legacy hardware. Year 1 also carries dual running, since legacy systems keep operating until their wave cuts over.
Five Years, Side by Side
Figures are in constant FY2026 dollars:
| Year | Status quo | Migration path | Cumulative difference |
|---|---|---|---|
| Year 1 | $5.80M | $6.01M | -$0.21M |
| Year 2 | $3.40M | $2.79M | $0.40M |
| Year 3 | $3.40M | $2.79M | $1.01M |
| Year 4 | $3.40M | $2.79M | $1.62M |
| Year 5 | $3.40M | $2.79M | $2.23M |
| Total | $19.40M | $17.17M | $2.23M |
Year 1 costs $0.21M more than paying the refresh. From Year 2 the gap closes and keeps widening by $0.61M a year.
Discounted at 1.3%, the five-year real rate in OMB Circular A-94 Appendix C for 2026 (opens in a new tab), the five-year difference is worth $2.14M in net present value. Payback arrives in Year 2.
Where the Case Breaks
Each row below changes one assumption and holds the rest at the base case:
| Scenario | 5-year difference | NPV | Payback |
|---|---|---|---|
| Base case | $2.23M | $2.14M | Year 2 |
| Cloud consumption 30% higher | $0.74M | $0.70M | Year 3 |
| Only 2 sustainment FTEs released | $0.91M | $0.87M | Year 2 |
| Avalon services 25% higher | $1.72M | $1.63M | Year 3 |
| No hardware refresh in the window | -$0.02M | -$0.10M | Beyond Year 5 |
| $250K in CSP modernization credits | $2.48M | $2.39M | Year 1 |
The refresh row carries the argument. Without a refresh or licensing event inside five years, the migration roughly breaks even on cost alone, and the justification shifts to outage risk, compliance, and staffing. With one, it pays back in Year 2.
Staffing is the second lever. The savings assume the agency actually redeploys four sustainment positions. If only two move, the five-year difference falls to $0.91M.
Consumption is the third. A 30% overrun on cloud spend cuts the difference to $0.74M, which is why post-migration governance matters as much as the move itself. The idle resources that accumulate after a migration (opens in a new tab) are where most of that overrun comes from.
Credits Change the Consumption Line, Not the Services Line
GSA's OneGov agreement with AWS provides up to $1 billion in incentive credits across federal civilian agencies through December 31, 2028 (opens in a new tab), including modernization credits. In the model, $250K in credits moves payback into Year 1. Eligibility belongs in scoping, before the budget request goes forward.
Budget the Reassessment, Not Just the Move
A migration changes the system boundary, so the agency will reassess and reauthorize the system. The model carries $250K for that assessment in Year 1. Programs that leave it out discover it as a schedule slip, and a structured ATO facilitation roadmap (opens in a new tab) is how offices keep that line predictable.
The funding also shapes the timing. Migration of existing systems runs mostly on one-year O&M money, and a fixed-price assessment is severable, quick to award, and a clean fit for either mid-year spend plans or the fourth-quarter obligation window.
Avalon's Cloud Migration & Development engagement starts with a fixed-price assessment and migration plan, priced from $50K to $150K. It builds both cost paths from your own portfolio, refresh quote, and staffing, then prices each migration wave before any migration dollar is committed.
