Unused Cloud Commitments Are Not AWS Migration Savings
Separate past payments, unavoidable future obligations and genuinely reusable discounts before counting source-cloud commitments as AWS migration savings.
Moving a workload does not make its existing commitment disappear. Count a source payment as migration savings only when the move changes what the organization must pay. A prepaid, nonrecoverable amount belongs in payment history. An unpaid obligation that survives the move belongs in the future cash schedule. A discount that can cover other necessary work may retain value, but that value needs its own eligibility and invoice evidence.
For a CTO and finance owner evaluating a migration to AWS, those distinctions can reverse the decision. They also apply to moves between AWS services or accounts. This article produces a commitment reconciliation for one workload, with a month-by-month example and a reusable evidence record. It does not interpret a reader's contract, recommend a commitment purchase or estimate an AWS funding entitlement. All amounts below are fictional US dollars, not AWS prices, quotes or customer results. No AWS account was queried.
Classify the payment and the remaining right separately
“Sunk” has a narrower meaning than “we signed something.” Here it means money already paid before the decision that cannot be recovered under either alternative. Future payments may be unavoidable under the actual agreement, but they are still future cash outflows. Calling them sunk must not erase them from treasury planning.
A remaining right can also have value even when its payment is sunk. If a prepaid discount covers necessary future work, using it can avoid another payment. If it cannot cover the destination or any other required work, an unused accounting balance does not become cash returned to the business.
| Item at the decision date | Cash treatment | Separate question about value |
|---|---|---|
| Past, nonrefundable upfront payment | History; do not pay it again in either future cash schedule | Can its remaining benefit displace a future payment? |
| Future payment due under both stay and move | Include once in each option until its supported stop date | Does unused capacity or discount benefit have a permitted use? |
| Charge that ends after approved retirement | Include until the actual stop date, then remove | What acceptance and contract evidence allows it to end? |
| Refund, sale or negotiated release | Separate conditional scenario until supported | What net amount, fees, effective date and approval are established? |
| Cost allocated to the departing application | Reconcile to the underlying invoice obligation | Does changing the allocation change the organization's payment? |
Past, nonrefundable upfront payment
Cash treatment: History; do not pay it again in either future cash schedule
Separate question about value: Can its remaining benefit displace a future payment?
Future payment due under both stay and move
Cash treatment: Include once in each option until its supported stop date
Separate question about value: Does unused capacity or discount benefit have a permitted use?
Charge that ends after approved retirement
Cash treatment: Include until the actual stop date, then remove
Separate question about value: What acceptance and contract evidence allows it to end?
Refund, sale or negotiated release
Cash treatment: Separate conditional scenario until supported
Separate question about value: What net amount, fees, effective date and approval are established?
Cost allocated to the departing application
Cash treatment: Reconcile to the underlying invoice obligation
Separate question about value: Does changing the allocation change the organization's payment?
Use these as independent fields, not mutually exclusive labels for an entire contract. A partially prepaid agreement can contain past cash, future payments, usage above a floor and rights that remain useful elsewhere. Procurement should identify the instrument and governing terms before an analyst selects a formula.
Do not add a minimum spend to the usage bill if the same eligible usage already satisfies that minimum. A simplified use-or-pay floor may require the greater of the floor and eligible usage, plus excluded charges, rather than their sum. The actual agreement determines how purchases, credits, support and shortfalls are treated. UNKNOWN terms are an unresolved input, not permission to choose the cheaper interpretation.
Check the exact AWS instrument before assuming portability
AWS products illustrate why “transferable commitment” is too vague for a financial model. The Savings Plans types documentation gives Compute Savings Plans a broader eligible scope than EC2 Instance Savings Plans: the former includes eligible EC2, Fargate and Lambda usage; the latter remains tied to a selected EC2 family and Region. That can preserve benefit for an eligible EC2-to-Fargate move with a Compute plan, while an EC2 Instance plan does not become Fargate coverage. Database Savings Plans are a separate type; an existing Compute plan does not turn into a database plan when the application moves to RDS.
These are product boundaries, not a dollar-for-dollar transfer guarantee. Check the exact destination usage, current inventory and applicable rates. AWS applies plans to eligible usage under its application rules; each hour's commitment is usable only within that hour. A quiet morning cannot be repaired by equal monthly usage concentrated in the evening. A monthly planning table must therefore reconcile to hourly evidence when modeling Savings Plans.
Account scope also matters. AWS billing preferences support account and group controls, including restricted groups where unused benefit does not flow outside the group. The purchase documentation states that Savings Plans and Reserved Instances cannot be shared outside the purchasing organization, including when billing transfer is used. A new payer or customer-owned organization does not establish reusable coverage.
For another source provider, read that provider's agreement. AWS documentation cannot establish cancellation, assignment, resale or discount eligibility for a different cloud. Record a proposed contract transfer separately from ordinary application of an existing discount to eligible usage; neither is implied by moving the workload's code.
Do not assume retirement creates a refund
AWS says EC2 Reserved Instances remain payable for their term regardless of actual use. Stopping the instance does not cancel the reservation obligation. Payment timing and benefit matching are separate from runtime state.
Nor should the model assume every commitment is permanently unrecoverable. AWS has a limited Savings Plan return mechanism: the guide specifies an hourly commitment of $100 or less, purchase within the last seven days and the same UTC calendar month, with additional state, permission, seller-of-record and account restrictions. Return quotas also apply. A return reprices previously covered usage to On-Demand or another applicable plan. It is not a general mid-term migration exit right. Check the actual instrument before including net proceeds or a revised bill; no return action is proposed here.
The EC2 Reserved Instance Marketplace is another bounded route: eligible EC2 Standard reservations can be sold, while Convertible and other-service reservations cannot. Seller eligibility matters; AWS India customers cannot register to sell there. Listing is not a sale, and ownership remains with the seller until sold. Model an uncertain sale separately, with its net proceeds and effective date, rather than deleting the remaining payments on the day someone proposes a listing.
Worked case: reconcile twelve months of future cash
Assume a fictional source agreement with a fixed remaining payment of $6,000 per month through Month 6. It includes a committed service bundle. An additional $4,000 per month pays for usage and services outside that bundle while the source workload runs. Those two amounts do not overlap. The organization previously paid a nonrefundable $12,000 upfront; that historical payment is excluded from both future cash totals.
The retained alternative costs $10,000 each month. For Months 1–6 that consists of the fixed $6,000 plus the $4,000 additional charge. For Months 7–12, assume a documented pay-as-you-go continuation at $10,000, with no new term commitment. This flat continuation is a synthetic assumption, not a provider renewal quote.
Migration starts target capacity in Month 1. The source retires at the end of Month 2 after acceptance. Additional source charges then stop, but fixed payments continue through Month 6. No refund, sale, termination fee or useful redeployment is available in this base case. The fully loaded target costs $7,000 each month. Transition invoices are $5,000 in each of Months 1 and 2. These stipulated target and transition totals include every modeled cost; they must not be counted again as separate delivery or compute lines.
This is an undiscounted, before-tax cash model. Equivalent service, flat demand, on-time acceptance and monthly payment timing are assumed. Financing, foreign exchange, tax, residual asset value, credits and noncash engineering opportunity cost are excluded. It is not an AWS Savings Plans billing simulation: the fictional source contract has explicit fixed monthly payments, unlike an hourly commitment's varying calendar-month total.
First, separate the cash components. Each amount in this schedule is per month, not the total for its period. The three periods contain two, four and six months respectively.
| Move cash component | Months 1–2 | Months 3–6 | Months 7–12 |
|---|---|---|---|
| Fixed source payment | $6,000 | $6,000 | $0 |
| Additional source charges | $4,000 | $0 | $0 |
| Target operation | $7,000 | $7,000 | $7,000 |
| Transition invoices | $5,000 | $0 | $0 |
| Move total per month | $22,000 | $13,000 | $7,000 |
Fixed source payment
Months 1–2: $6,000
Months 3–6: $6,000
Months 7–12: $0
Additional source charges
Months 1–2: $4,000
Months 3–6: $0
Months 7–12: $0
Target operation
Months 1–2: $7,000
Months 3–6: $7,000
Months 7–12: $7,000
Transition invoices
Months 1–2: $5,000
Months 3–6: $0
Months 7–12: $0
Move total per month
Months 1–2: $22,000
Months 3–6: $13,000
Months 7–12: $7,000
Across twelve months, these components total $36,000 in fixed source payments, $8,000 in additional source charges, $84,000 in target operation and $10,000 in transition invoices. Their sum is $138,000. Staying costs $10,000 in each month, totaling $120,000.
Now compare the two alternatives month by month. Extra cash to date means cumulative move cash minus cumulative stay cash.
| Month | Stay cash | Move cash | Extra cash to date |
|---|---|---|---|
| 1 | $10,000 | $22,000 | $12,000 |
| 2 | $10,000 | $22,000 | $24,000 |
| 3 | $10,000 | $13,000 | $27,000 |
| 4 | $10,000 | $13,000 | $30,000 |
| 5 | $10,000 | $13,000 | $33,000 |
| 6 | $10,000 | $13,000 | $36,000 |
| 7 | $10,000 | $7,000 | $33,000 |
| 8 | $10,000 | $7,000 | $30,000 |
| 9 | $10,000 | $7,000 | $27,000 |
| 10 | $10,000 | $7,000 | $24,000 |
| 11 | $10,000 | $7,000 | $21,000 |
| 12 | $10,000 | $7,000 | $18,000 |
| Twelve-month total / ending difference | $120,000 | $138,000 | $18,000 |
1
Stay cash: $10,000
Move cash: $22,000
Extra cash to date: $12,000
2
Stay cash: $10,000
Move cash: $22,000
Extra cash to date: $24,000
3
Stay cash: $10,000
Move cash: $13,000
Extra cash to date: $27,000
4
Stay cash: $10,000
Move cash: $13,000
Extra cash to date: $30,000
5
Stay cash: $10,000
Move cash: $13,000
Extra cash to date: $33,000
6
Stay cash: $10,000
Move cash: $13,000
Extra cash to date: $36,000
7
Stay cash: $10,000
Move cash: $7,000
Extra cash to date: $33,000
8
Stay cash: $10,000
Move cash: $7,000
Extra cash to date: $30,000
9
Stay cash: $10,000
Move cash: $7,000
Extra cash to date: $27,000
10
Stay cash: $10,000
Move cash: $7,000
Extra cash to date: $24,000
11
Stay cash: $10,000
Move cash: $7,000
Extra cash to date: $21,000
12
Stay cash: $10,000
Move cash: $7,000
Extra cash to date: $18,000
Twelve-month total / ending difference
Stay cash: $120,000
Move cash: $138,000
Extra cash to date: $18,000
*Synthetic commitment timeline. Source operation ends after Month 2; source payments end after Month 6. Positive cumulative values mean migration has consumed more cash than staying. The last column is a running difference, not a monthly charge: do not sum it. Its final value is the ending difference.*
The move costs $18,000 more within this horizon, despite the lower target run rate. It requires a maximum additional $36,000 relative to the funded stay baseline, reached at the end of Month 6. This is incremental cash headroom, not the organization's total bank balance requirement.
Check the arithmetic independently: stay is 12 × $10,000 = $120,000. Move is 6 × $6,000 + 2 × $4,000 + 12 × $7,000 + 2 × $5,000 = $138,000. The $12,000 previously paid does not appear in either future total. An accounting report may still recognize that payment over time; finance should reconcile its expense view to this cash view instead of adding amortization as a new invoice.
If an analyst removes the whole source bill after Month 2, the apparent move total becomes $20,000 + $84,000 + $10,000 = $114,000, suggesting a $6,000 saving. The omitted Months 3–6 obligation is $6,000 × 4 = $24,000. Restoring it changes the result from $6,000 less cash to $18,000 more. That correction is the purpose of the reconciliation.
Give reusable benefit a counterfactual, not a face value
The base case has no other permitted use. Suppose instead that another necessary workload can absorb released benefit in Months 3–6. An authorized billing analysis establishes that this would displace $2,500 of otherwise payable charges each month. The $2,500 is a separate stipulated net invoice effect, not the face value of the $6,000 payment or a discount derived from it.
Expand both alternatives to include that other workload. Staying now totals $120,000 + 4 × $2,500 = $130,000. Moving remains $138,000 because the existing source payments cover the stipulated displaced charges. Migration is still $8,000 more expensive, but its disadvantage is $10,000 smaller than in the no-reuse case.
Do not also subtract $10,000 from the $138,000 total: the expanded comparison already includes the benefit by removing those additional charges under move. Do not claim the whole $36,000 commitment as reusable value. Its price, remaining balance and avoided alternative payment answer different questions.
For a real AWS scenario, establish eligible usage in each relevant hour, account-sharing scope, competing reservations and plans, and any added costs of moving the other workload. Keep the necessary-workload demand forecast separate from its historical utilization. Running unnecessary work to improve a utilization percentage supplies no avoided-payment benefit.
Counterexample: waiting can waste avoidable cash
Residual commitments do not automatically justify deferral. Consider a different fictional case in which a source discount is fully prepaid, nonrefundable and unusable elsewhere. There are no future committed payments. Keeping the workload requires $4,000 per month of additional source charges. An immediately accepted equivalent target costs $2,500 per month, and migration costs $3,000 once. There is no overlap in this deliberately simplified case.
Over twelve months, stay requires $4,000 × 12 = $48,000 of future cash. Move requires $2,500 × 12 + $3,000 = $33,000, or $15,000 less. Adding an unrecoverable historical prepayment only to move would falsely penalize that option. Removing the same prepayment from both schedules does not deny its accounting impact; it isolates the cash the decision can change.
The conclusion changes if staying can use the prepaid right to avoid more cash than assumed, moving can obtain a refund, or equivalent target operation requires extra resources. Put those effects into their respective schedules. A shorter remaining term, contractual release or technical deadline can also favor a different migration date. Compare dates against the same horizon and service requirements; do not choose a delay solely to make a committed-usage dashboard look fuller.
Complete one commitment evidence record
Use one row per instrument or contract component. Store actual contracts and billing exports in an approved restricted location, not a public worksheet. Use aliases here; account IDs, negotiated terms, customer details and credit codes are unnecessary for an initial discussion. A denied read means UNKNOWN, not an empty inventory. Do not buy, return, list, change sharing or terminate anything while collecting this record.
| Field | Enter for the real decision | Missing-evidence gate |
|---|---|---|
| Workload and alternatives | Workload alias, stay/move dates, equivalent-service owner, horizon and currency | No cost comparison until scope is equivalent |
| Instrument and authority | Provider, contract/plan type, purchaser, governing terms version, procurement owner | Contract interpretation held for its authorized owner |
| Historical cash | Amount already paid, payment date, recoverability evidence; keep book value separate | Refund or write-off treatment remains UNKNOWN |
| Future obligations | Payment schedule, minimum-spend mechanics, expiry, notice and renewal conditions | Retain uncertain charges in a clearly labeled downside; do not claim avoidance |
| Stop condition | Earliest legally and operationally supported stop date for each charge | Keep charge until acceptance and release are supported |
| Reuse candidate | Necessary receiving workload, service/rate eligibility, hourly evidence where required, account/group scope | Use no-reuse base case pending proof |
| Reuse value | Additional charges displaced under move versus stay, costs to enable reuse, overlap with other claims | No benefit subtraction without a counterfactual |
| Release or resale | Written approval or completed transaction, net proceeds, fees, revised obligations and date | Separate conditional scenario; no assumed sale |
| Reconciliation | Future stay and move totals, monthly differences, peak cumulative difference, expense-to-cash bridge | Finance verifies each charge appears once |
| Disposition | Supported comparison, bounded downside, or HELD; named missing-input owner and due date | Do not turn an incomplete packet into purchase or migration approval |
Workload and alternatives
Enter for the real decision: Workload alias, stay/move dates, equivalent-service owner, horizon and currency
Missing-evidence gate: No cost comparison until scope is equivalent
Instrument and authority
Enter for the real decision: Provider, contract/plan type, purchaser, governing terms version, procurement owner
Missing-evidence gate: Contract interpretation held for its authorized owner
Historical cash
Enter for the real decision: Amount already paid, payment date, recoverability evidence; keep book value separate
Missing-evidence gate: Refund or write-off treatment remains UNKNOWN
Future obligations
Enter for the real decision: Payment schedule, minimum-spend mechanics, expiry, notice and renewal conditions
Missing-evidence gate: Retain uncertain charges in a clearly labeled downside; do not claim avoidance
Stop condition
Enter for the real decision: Earliest legally and operationally supported stop date for each charge
Missing-evidence gate: Keep charge until acceptance and release are supported
Reuse candidate
Enter for the real decision: Necessary receiving workload, service/rate eligibility, hourly evidence where required, account/group scope
Missing-evidence gate: Use no-reuse base case pending proof
Reuse value
Enter for the real decision: Additional charges displaced under move versus stay, costs to enable reuse, overlap with other claims
Missing-evidence gate: No benefit subtraction without a counterfactual
Release or resale
Enter for the real decision: Written approval or completed transaction, net proceeds, fees, revised obligations and date
Missing-evidence gate: Separate conditional scenario; no assumed sale
Reconciliation
Enter for the real decision: Future stay and move totals, monthly differences, peak cumulative difference, expense-to-cash bridge
Missing-evidence gate: Finance verifies each charge appears once
Disposition
Enter for the real decision: Supported comparison, bounded downside, or HELD; named missing-input owner and due date
Missing-evidence gate: Do not turn an incomplete packet into purchase or migration approval
Start with one commitment being counted as migration savings. Ask finance to identify the specific payment that will stop and procurement to identify the clause or completed transaction that permits it. Ask engineering for the acceptance evidence that makes retirement safe. Complete that commitment's evidence record before approving the savings claim, and revisit it when the cutover date, demand, account boundary or terms change.
Use the migration overlap budget for the full approval case, including delivery, customer effort and conditional support. Use the Savings Plans input-validity check if a post-migration recommendation is being offered as evidence. This record supplies the commitment rows those broader decisions need; it does not replace either review.