This case study describes how a telecommunications operator negotiated a migration to Oracle Cloud Infrastructure on terms that protected it rather than trapping it, resisting the oversized commitment Oracle initially proposed. Details have been anonymised, but the approach is one we apply to every cloud negotiation. The lesson is that the cloud move itself can be a sound decision while Oracle's first proposal for it is still a bad deal, and that the difference lies in commitment sizing and exit terms.
This article sits within our case studies pillar and illustrates the principles behind our cloud migration advisory service.
The Starting Position
The operator was approaching the renewal of a large on premises Oracle estate, and Oracle had proposed converting the relationship into a substantial OCI commitment instead. The proposal came with attractive looking cloud credits and a strong discount headline, and parts of the business were genuinely interested in moving to the cloud for sound architectural reasons. The risk was that the enthusiasm for the move would lead the operator to accept Oracle's sizing and terms without scrutiny.
The first discipline was to separate the question of whether to move from the question of on what terms. The cloud move could be a good idea and Oracle's specific proposal could still be a poor deal, and conflating the two is exactly how customers over commit. Keeping them distinct is the principle we set out in our cloud sales pressure article.
Sizing the Commitment to Real Demand
The operator built its own consumption forecast based on its actual workloads, growth plans, and migration timeline, rather than relying on Oracle's sizing. The analysis showed that Oracle's proposed commitment was significantly larger than the operator would realistically consume, with the generous credits attached to a capacity number that assumed faster and fuller migration than was prudent. The oversized commitment would have left the operator paying for capacity it could not use.
Oracle's proposed commitment assumed a migration pace the operator could not safely achieve. Sizing the commitment to an evidenced, realistic forecast cut the committed spend substantially while still capturing meaningful cloud credits on the capacity actually needed.
Armed with its own demand model, the operator negotiated a commitment sized to realistic consumption, with the ability to grow on favourable terms rather than being locked into an inflated number from the start. This is the commit and burn discipline we describe in our commit and burn tactics article, and it was the single largest driver of the improved outcome, supported by our Oracle OCI product guidance.
Locking in the Exit Terms
Oracle's first proposal said little about what would happen at the end of the commitment or if the operator wanted to change course. The operator insisted on negotiating these terms before signing: how data could be retrieved on exit, in what format and timeframe, what would happen to unused credits, and whether it could adjust the commitment if its consumption forecast proved wrong. These terms were far easier to secure while Oracle wanted to close the deal than they would have been afterward.
The exit and flexibility terms mattered because a cloud commitment without them is a trap, however good the headline pricing. The operator secured defined data retrieval rights, a ramp structure that allowed it to grow into the commitment, and protection against being stranded if its plans changed. These are the cloud contract terms we treat as essential, as set out in our OCI universal credits guidance.
The Outcome
The operator proceeded with the OCI migration, but on a commitment sized to its real demand, with strong cloud credits applied to capacity it would actually use, and with the exit and flexibility terms its business needed to manage the risk. The committed spend was substantially lower than Oracle's initial proposal, and the operator retained the freedom to adjust as its migration progressed rather than being locked into assumptions made at signing.
The result was a cloud move the operator could defend on its merits rather than one driven by Oracle's targets. By separating the decision to move from the terms of the move, sizing the commitment to evidence, and securing the exit terms upfront, the operator captured the genuine benefits of the cloud without the over commitment that Oracle's first proposal would have imposed. This balanced outcome reflects the framework in our article on when Oracle cloud makes sense.
What Other Buyers Can Take From This
The transferable lesson is to never let enthusiasm for the cloud override scrutiny of the deal. A cloud move can be right while the proposal in front of you is wrong, and the way to tell the difference is to build your own demand forecast and negotiate the exit terms before you sign. Customers who accept Oracle's sizing over commit; customers who bring their own evidence commit to what they will use.
The case also shows the value of negotiating exit terms while you still have leverage. Once the deal is signed, the operator would have had little ability to secure data retrieval rights or commitment flexibility, but before signing, with Oracle eager to close, these terms were achievable. Bringing that discipline to the moment of maximum leverage is exactly what we do on cloud engagements, guided by the framework in our Oracle Negotiation Playbook.
Where to Read Next
For a full migration off Oracle see our retail chain migration case study. The full set of outcomes is in our case studies pillar, and the methodology behind them is in the Oracle Negotiation Playbook.