This case study follows a multi brand hospitality group through an Oracle Apps Unlimited renewal centred on its E-Business Suite estate. Apps Unlimited is Oracle's commitment to continue supporting and enhancing its established applications, including EBS, and the renewal of the support attached to that estate is a recurring negotiation for any organisation that runs these systems. The group is anonymised, but its position is typical, because hospitality companies often run large, stable EBS deployments that they intend to keep, while Oracle uses the renewal to push toward Fusion cloud applications. The group renewed on terms that protected its estate without accepting the cloud commitment Oracle attached.
The starting position.
The group ran EBS across finance, procurement, and property management for several hotel brands, on a stable estate it had no near term plans to replace. Its Apps Unlimited support renewal arrived with a meaningful uplift and a strong push toward Oracle Fusion cloud applications, framed as the natural next step and sweetened with credits that were really a commitment to future cloud spend. The group's applications team valued the stability of EBS and did not want to undertake a cloud migration it had not planned, but the procurement team was unsure whether it could decline the cloud push and still renew its support cleanly.
The group's first task was to separate the two things Oracle had bundled, the support renewal it needed and the cloud commitment it did not, so it could negotiate each on its merits. This framing, treating the renewal and the cloud push as distinct, is set out in the Apps Unlimited pricing note, and the deal structure in the Apps Unlimited deal page.
Understanding the estate.
The group reconstructed its own position before responding. It confirmed which EBS modules it ran, mapped its licences to its deployments, and verified that it was compliant, including on the database tier beneath EBS, where licensing questions often hide. This work confirmed the group was within its entitlements and gave it the data to test the uplift rather than accept it. The database tier review in particular mattered, because EBS sits on Oracle Database and the licensing of that tier is a common source of unexpected exposure, as explained in the EBS database tier note.
The group also checked its indirect access position, the question of whether other systems touching EBS data created additional licensing requirements, a risk covered in the indirect access note. Confirming it was clean on this point removed a lever Oracle might otherwise have used to justify the uplift or to press the cloud move.
Separating support from cloud.
With its position confirmed, the group declined to treat the cloud credits as a discount on its support renewal. It recognised that the credits represented a future spend commitment, not a saving, and that accepting them would lock it into a migration it had not decided to make. Instead it negotiated the support renewal on its own terms, holding the uplift to a defensible level by pointing to its compliance position and its prior rate, and declining the cloud commitment without that decision affecting its support.
This separation was the heart of the negotiation, because Oracle's strategy depended on the group treating the bundle as a single offer. By insisting on negotiating the support it needed independently of the cloud it did not, the group denied Oracle the leverage the bundle was designed to create, a framing discussed in the negotiation frameworks note.
Capping the support.
The group also addressed the longer term trajectory of its support cost. Rather than renewing for a single year and facing the same uplift pressure again, it negotiated a multi year price hold on its Apps Unlimited support, giving it cost certainty across the period it intended to keep EBS. This protected it from the annual erosion by which support cost drifts upward, and it removed the recurring leverage Oracle gains from a year by year renewal.
The group kept the negotiation in writing where the substance mattered, capturing the agreed rate, the price hold, and Oracle's confirmation that declining the cloud credits did not affect the support terms, the documentation discipline set out in the document trail note. This record protected the group against any later attempt to reinterpret the deal.
How the deal closed.
Oracle moved in stages. Its first response held the uplift and kept the cloud credits central, treating them as inseparable from the renewal. The group held its position, pointing to its clean compliance data and its decision to keep EBS, and made clear it would renew the support on reasonable terms but would not commit to cloud spend it had not planned. As the renewal date approached, Oracle released a better support number, dropped the insistence on the cloud commitment, and agreed the multi year price hold.
The group renewed its Apps Unlimited support at a defensible rate, with a multi year hold, and without the cloud commitment Oracle had attached, protecting the EBS estate it intended to keep. The outcome came from separating the bundle, proving its position, and holding through the pressure, the approach our renewal negotiation service brings to application renewals.
What the group learned.
The group drew several lessons. The first was that Oracle bundles the support a buyer needs with the cloud a buyer may not, and that separating the two is the central move in an Apps Unlimited renewal. The second was that compliance data is the foundation of leverage, because the group could only decline the cloud push and hold the uplift once it could prove its position, including on the database tier and indirect access. The third was that a multi year price hold protects the buyer that intends to keep a stable estate, removing the recurring uplift pressure.
The group also learned the value of deciding its own application roadmap before the renewal, so that Oracle's framing of cloud as inevitable did not drive a decision the group had not made. The product context it now tracks is in the Oracle Database product page, and the full framework behind the approach is in the Oracle Negotiation Playbook.
Applying the pattern.
A buyer facing an Apps Unlimited renewal can apply the same pattern. Decide your application roadmap first, so Oracle's cloud framing does not drive it. Reconstruct your position, including the database tier and indirect access, so you can test the uplift. Separate the support you need from the cloud commitment you may not, and negotiate each on its merits. Then secure a multi year price hold if you intend to keep the estate, and document the terms so they cannot be reinterpreted. The group protected its estate and its budget by following this order.
The group reached the outcome with independent advice on the buyer side, because the bundling of support and cloud, and the hidden questions in the database tier and indirect access, are where buyers most often lose ground without help. An advisor who has run many of these application renewals brings that knowledge to a buyer facing one, which is what our renewal negotiation service exists to provide.