Last updated: June 2026
To handle reserved instances during an M&A, inventory both commitment portfolios, consolidate billing so flexible coverage can pool, re-target coverage onto the combined usage before decommissioning duplicated workloads, and re-baseline the merged estate under one buying policy. Commitments remain valid obligations through the deal, so the work is consolidation and re-targeting, not cancellation, and the goal is to keep every discount you already paid for working.
- Reservations and savings plans survive the deal; they are obligations, not options.
- Consolidated billing lets flexible commitments pool across the combined estate.
- Re-target coverage onto surviving usage before switching off old workloads.
- Re-baseline and centralize buying so two portfolios become one function.
Handling reserved instances during a merger or acquisition means consolidating two independently built commitment portfolios into one without stranding the discounts either side already bought. Reservations and savings plans are binding obligations that survive the transaction, so the task is inventory, consolidation, and re-targeting rather than cancellation. This article is part of our commitment cluster; the pillar it links up to is the complete guide to cloud commitment management. Pooling and re-targeting coverage across the merged estate is a Lock step in our See, Cut, Lock, Run method, where governance keeps the combined discount in place.
What happens to reserved instances in a merger or acquisition?
Reserved instances and savings plans remain valid obligations through a merger or acquisition; they do not disappear, and the combined company keeps paying for them until they expire. The real risk is not loss of the commitments but waste: two portfolios bought independently almost always overlap, and some coverage strands once usage is consolidated or duplicated workloads are decommissioned. A reservation that perfectly fit the acquired company's standalone estate can become idle the moment its workload is merged into the parent's platform. The work, therefore, is to inventory both sides, consolidate billing so flexible coverage can pool, and re-baseline the merged estate under one policy, the same consolidation logic behind a centralized commitment buying function.
Can you transfer reserved instances between companies?
You generally cannot transfer a commitment to an unrelated billing account, but once the merged entities are brought under one billing family or organization, flexible commitments pool and apply across the combined usage automatically. Where a portfolio holds convertible or exchangeable reservations, you can exchange them for configurations that fit the combined estate, which is exactly when the flexibility built into flexible commitments pays off. Standard, configuration-locked reservations cannot be moved, so they must be matched to surviving usage of the same shape or run to expiry. This is why the inventory step matters: you need to know which commitments are flexible, which are exchangeable, and which are locked before you plan the integration.
How do you handle the portfolios, step by step?
These five steps consolidate two books of commitments into one governed estate.
- Inventory both commitment portfoliosCatalog every reservation, savings plan, and CUD on both sides with term, expiry, utilization, and balance. The result is full visibility before any integration decision.
- Consolidate billing where the deal allowsBring both estates under one billing family so flexible commitments can pool. The result is coverage that applies across the combined usage instead of per entity.
- Pool and re-target coverageLet flexible commitments float across the merged usage and point one side's coverage at the other's on-demand spend. The result is higher overall utilization.
- Resolve overlaps, orphans, and carve-outsFind duplicated or idle commitments, plan exchanges where supported, and isolate commitments tied to any divested unit. The result is stranding caught before it is locked in.
- Re-baseline and set a combined buying policyBuild one clean baseline and one coverage target for the merged estate and centralize future buying. The result is two portfolios becoming one governed function.
Inheriting a second portfolio of reservations?
Our commitment management service inventories both books, consolidates billing, re-targets flexible coverage across the merged estate, resolves overlaps and orphans, and re-baselines under one policy. On the performance model you pay only from realized savings. No savings, no fee.
Book a commitment review →How do you avoid stranded commitments in an M&A?
Avoid stranding by sequencing the integration so coverage is re-pointed at surviving usage before the duplicated workloads are switched off. The classic M&A mistake is decommissioning the acquired company's workloads on the integration timeline while their reservations sit untouched, instantly stranding that coverage. Instead, inventory early, consolidate billing so flexible commitments can pool, re-target coverage onto the combined estate, and only then decommission. Commitments tied to a divested unit should be isolated and carved out with that unit so they leave with the business they serve. Reporting this on a shared commitment ROI dashboard keeps utilization visible throughout the integration. When the acquired estate is also still migrating into the cloud, sequence the buying with the same discipline used to forecast commitment needs for a cloud migration.
Commitment transfer, exchange, and consolidated-billing behavior reflect AWS, Azure, Google Cloud, and OCI as of June 2026. Verify current rules in the relevant provider documentation before acting, because commitment and billing-consolidation terms change.
The Commitment Strategy Playbook includes the M&A commitment integration checklist and the portfolio consolidation worksheet we apply on engagements. It is the downloadable companion to this article.
Frequently asked questions
What happens to reserved instances in a merger or acquisition?
Reserved instances and savings plans remain valid obligations through a merger or acquisition; they do not disappear, and the combined company keeps paying for them until they expire. The risk is that two independently bought portfolios overlap, strand, or sit unutilized once usage is consolidated or workloads are decommissioned. The work is to inventory both sides, consolidate billing so flexible coverage can pool, and re-baseline the merged estate under one policy.
Can you transfer reserved instances between companies?
You generally cannot transfer a commitment to an unrelated billing account, but once the merged entities are brought under one billing family or organization, flexible commitments pool and apply across the combined usage automatically. Where a portfolio holds convertible or exchangeable reservations, you can exchange them for configurations that fit the combined estate. Standard configuration-locked reservations cannot be moved, so they must be matched to surviving usage or run to expiry.
How do you avoid stranded commitments in an M&A?
Avoid stranding by inventorying both portfolios early, consolidating billing so coverage can pool, and re-targeting flexible commitments onto the combined usage before decommissioning the duplicated workloads that those commitments were covering. Sequence the integration so a commitment is re-pointed at surviving usage before its original workload is switched off. Commitments tied to a divested unit should be isolated and carved out with that unit.
Who should own commitments after a merger?
A single combined FinOps function should own all commitments after a merger, with one consolidated baseline, one coverage target, and one buying policy. Leaving each legacy team to manage its own portfolio recreates the per-team buying problem at a larger scale. Centralizing ownership is what lets the merged estate pool coverage, resolve overlaps, and buy future commitments against the whole baseline.
The short version
Through an M&A, commitments survive as obligations, so the job is to inventory both portfolios, consolidate billing, pool and re-target flexible coverage onto the combined estate, resolve overlaps, and re-baseline under one policy. When you want two commitment books merged without stranding the discounts you already bought, that is exactly what our commitment management service delivers.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: FinOps Foundation Framework ↗ and FinOps Rate Optimization capability ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.