European Pharmaceutical Group: How We Exited RISE and Restructured to Cloud ERP Private Without Breaking GxP Continuity

The Situation

The pharmaceutical group had moved to RISE with SAP in 2022 on a 5-year initial term. The original deal had been signed to support an S/4HANA conversion and to consolidate three legacy ECC tenants into a single production estate. Two years into the term, the operational pattern had not delivered the promised flexibility. The hyperscaler infrastructure layer was rigid against GxP change-control requirements. Quarterly cloud release cycles created revalidation overhead the QA organisation could not absorb without interfering with manufacturing campaigns. The BTP credit allocation had been consumed at roughly 40 percent over two years, and the AI Units and Joule capabilities the SAP account team kept marketing did not fit into the regulated production environment.

The July 2025 SAP rebrand turned Cloud ERP Private into a distinct product name with a separate commercial wrapper. For a regulated manufacturer, the rebrand mattered for two reasons. First, it surfaced a contractual route to disentangle the S/4HANA workload from the bundled RISE infrastructure and operations contract. Second, it created an opening to renegotiate the FUE bundle separately from the hyperscaler hosting, which is where most of the operational pain originated. The group's CIO and Head of Quality wrote a joint paper to the executive committee recommending an exit from RISE and a restructure to Cloud ERP Private with a separately procured GxP-grade hosting arrangement. We were retained to design the licensing pathway and run the SAP negotiation.

SAP's initial response framed exit as expensive and risky. The account team quoted exit fees against the remaining contract term, indicated that the FUE bundle would need to be re-purchased at then-current list pricing in the new structure, and signalled that any timing slippage would force a Q4 settlement on SAP's terms. The framing was familiar. The execution had to be different.

What We Did

1. Reread the original RISE contract end-to-end. The 2022 Order Form contained termination-for-convenience language and a specific clause covering material change to SAP's RISE product structure. We argued the July 2025 rebrand and the formal split of Cloud ERP Private as a distinct product met the material change threshold. SAP initially disputed the argument. The written history of SAP's own product positioning between 2023 and 2025 supported our reading.
2. Built a parallel pricing model for Cloud ERP Private. We mapped every FUE, every named user count, and every engine licence in the existing RISE bundle onto the Cloud ERP Private product list. The exercise showed that, on like-for-like scope, the underlying SAP software economics were broadly comparable. The premium the group was paying inside RISE sat in the infrastructure, the operations service, and the BTP allocation, not in the FUE bundle itself. That finding became the negotiating frame.
3. Challenged the exit-fee calculation. SAP's opening exit fee quote applied the full contracted run rate against the remaining term. We applied the contractual mitigation provisions, the credit for unused BTP allocation, and the credit for the operations-service component which would not be consumed post-exit. The recalculated exit-fee position landed materially below the SAP opening number. Negotiated, it landed lower again.
4. Preserved the FUE bundle economics. Rather than accept the SAP-proposed re-purchase at list pricing, we negotiated a contractual transfer of the existing FUE entitlement into the new Cloud ERP Private Order Form at the unit pricing implied by the original RISE deal. The transfer mechanism is contractually awkward but supportable, and SAP's commercial team accepted it once the alternative scenarios were modelled.
5. Engineered the GxP transition timeline. The QA organisation set the pace, not the SAP commercial team. We sequenced the contractual exit, the new Cloud ERP Private signature, and the migration to a GxP-grade hosting partner over a 14-month transition with explicit cutover gates, revalidation windows, and contractual provisions for SAP support continuity through the cutover. The GxP audit trail through transition was protected by a written transition plan agreed in advance with the relevant national medicines agencies.
6. Locked in the contractual definitions. The new Cloud ERP Private Order Form contains explicit language defining the support model, the upgrade cadence, the validation impact of SAP-initiated changes, and the buyer's right to defer non-critical updates inside a defined GxP change-control window. The clauses remove the structural source of pain that drove the exit decision in the first place.

The Outcome

The group signed the Cloud ERP Private restructure within 14 months of the initial executive decision. The negotiated exit-fee position landed at roughly half of SAP's opening quote, with the credits for unused BTP and the unwound operations component recognised in the settlement. The FUE entitlement transferred into the new Order Form at terms that preserved the original RISE deal economics. The GxP-validated environment moved to a hosting partner with pharmaceutical-grade change-control capabilities, with no validated production break across the cutover. Annual run-rate cost in the new structure sits 12 to 18 percent below the trajectory the RISE renewal would have delivered, with the additional benefit of recovered control over the change-control calendar.

Two secondary outcomes were structurally important. First, the Cloud ERP Private Order Form contractually defines the upgrade cadence and the validation impact, which removes the QA organisation's principal complaint about RISE. Second, the separation of hosting from SAP software creates an exit option at the next renewal cycle that did not exist inside RISE. The group's CIO now has commercial optionality on infrastructure and operations that the original RISE deal had quietly eliminated.

What Other Enterprises Can Take From This

RISE is a bundle. Bundles trade simplicity for optionality. For some buyers, that trade works. For regulated manufacturers, asset-heavy operators, and anyone whose change-control calendar conflicts with SAP's cloud release cadence, the trade often does not. The July 2025 rebrand of Cloud ERP Private as a distinct product made the structural choice visible and contractually available where it had previously been blurred inside the RISE wrapper. If your current RISE deal does not fit your operating model, the rebrand is the moment to reread the contract.

Exit fees and FUE re-purchase costs are the two levers SAP uses to discourage restructure. Both are negotiable. The exit-fee math is governed by the contractual mitigation provisions and the credits for unconsumed elements. The FUE re-purchase argument breaks down once the buyer demonstrates a like-for-like mapping onto the Cloud ERP Private product list and insists on a contractual transfer of the existing entitlement. Neither lever is unmovable. The work is in the contract reading and the parallel pricing model, not in the negotiation rhetoric.

For regulated industries, the second-order question is harder than the licensing question. Where will the new environment run, what GxP qualification work transfers and what does not, and how is the change-control calendar protected through transition. None of that is a SAP licensing problem in the narrow sense, but the licensing contract has to accommodate the answer. For a fuller treatment of the underlying RISE bundle economics and the Cloud ERP Private positioning, our RISE with SAP licensing guide walks through the FUE math, the BTP credit model, and the contractual structures that make these restructures workable.