French Energy Provider Secures 35% Savings and Local Data Sovereignty in RISE with SAP Agreement

The Client: Regulated Energy Under Sovereign Cloud Pressure

The client is a French energy provider operating critical national infrastructure — electricity distribution networks and associated operational systems — with approximately 8,500 employees and an SAP ECC estate covering finance, HR, procurement, and asset management for a geographically distributed operation across metropolitan France and overseas territories.

The organisation was subject to French national security regulations — specifically the requirements under French law relating to operators of vital importance (OIV) — which restricted where certain categories of operational data could be processed and stored. The regulations did not apply uniformly across all data, but a significant portion of the SAP estate was classified as subject to French territorial requirements. A cloud migration that moved this data outside French infrastructure would require regulatory exemptions that the organisation did not have and could not obtain within the project timeline.

SAP's standard RISE with SAP offering runs on hyperscaler infrastructure with data centre locations across multiple geographies. The SAP account team's initial response to the sovereignty requirement was to propose the RISE with SAP Sovereign Edition — a configured offering designed specifically for organisations with national data sovereignty requirements — at a price that represented approximately 28 percent premium above the standard RISE offer. The account team characterised this premium as unavoidable, a reflection of the additional infrastructure and operational controls required to support sovereign cloud compliance.

Why SAP's Framing Was Incorrect

The 28 percent sovereign cloud premium that SAP presented as non-negotiable rests on a specific set of assumptions about deployment architecture that are not universally required to achieve French data sovereignty compliance. Understanding those assumptions — and identifying where they do not apply to a given client's regulatory situation — is the prerequisite for challenging the premium commercially.

The Architecture Options SAP Does Not Lead With

SAP offers multiple deployment models that can satisfy French data residency requirements without the full Sovereign Edition premium. The RISE with SAP Private Edition Customer Data Centre option allows the client's RISE instance to run on dedicated hardware located within the client's own data centre facilities or at a French colocation provider. This option maintains the managed service model of RISE — SAP operates the software layer — while allowing the client to own or control the physical infrastructure layer, which is where the territorial requirement applies.

This architecture satisfies French OIV data residency requirements for most operational data categories because the primary and disaster recovery infrastructure is located on French territory, operated under French legal jurisdiction. The full Sovereign Edition — with its 28 percent premium — adds additional controls around personnel access, encryption key management, and operational process segregation that some regulatory frameworks require but that French OIV regulations do not mandate as a universal requirement.

SAP's account teams are incentivised to sell Sovereign Edition when sovereignty is mentioned by a client, because Sovereign Edition generates higher revenue per deal. The Customer Data Centre option and the standard Private Edition with contractual data residency commitments are commercially available alternatives that SAP's account team did not present until the client's advisers specifically requested a structured comparison of all deployment options against the client's regulatory requirements. This is the fact that SAP would prefer buyers not to know: sovereign cloud premium is often a commercial choice, not a regulatory necessity.

The Negotiation: Eliminating the Premium

Step 1: Independent Regulatory Assessment

The first phase of the engagement was an independent assessment of the client's regulatory obligations under French OIV legislation, mapped against the specific data classifications within the SAP estate. This exercise established that approximately 60 percent of the SAP data set was subject to territorial requirements, while 40 percent — including HR analytics, benchmarking data, and some reporting workloads — was not subject to sovereignty restrictions.

This segmentation was commercially significant. It meant that a hybrid architecture — with sovereignty-restricted workloads on French-territory infrastructure and non-restricted workloads on standard RISE — was potentially compliant, and the sovereign cloud premium should apply only to the restricted portion of the estate, not the full SAP landscape. SAP's initial offer had applied the sovereign premium across the entire estate, producing a cost that was substantially higher than the regulatory requirement justified.

Step 2: Structuring the Alternative Architecture Proposal

Working from the regulatory assessment, the advisory team developed a structured architecture proposal based on RISE Private Edition with the Customer Data Centre option for sovereignty-restricted workloads, combined with standard RISE infrastructure for non-restricted workloads. The proposal included a detailed legal analysis confirming that the Customer Data Centre option, with contractual data residency commitments specifying primary and disaster recovery hosting on French territory, satisfied the client's OIV obligations for the restricted data categories.

This proposal was presented to SAP's account team and deal desk as a technically complete, legally validated alternative to the Sovereign Edition. It placed the burden on SAP to demonstrate why the premium architecture was required for this client's specific regulatory situation — rather than accepting SAP's characterisation of sovereignty as requiring Sovereign Edition by default.

Step 3: Commercial Leverage Through Migration Commitment

The client was migrating from a fully on-premise SAP ECC estate with substantial perpetual licence investments. The migration from ECC to RISE represented a significant revenue opportunity for SAP — not merely the RISE subscription itself, but the long-term contractual relationship, the migration services, and the BTP workload expansion expected over the contract term.

SAP's fiscal year ends on 30 September. The timing of the commercial discussions was structured to place the decision point in SAP's Q4 — the July to September period when account teams have maximum discount authority and the highest incentive to close large, multi-year deals before fiscal year-end. A regulated energy provider committing to a five-year RISE relationship, with a defined BTP expansion roadmap and migration services spend, represented the kind of strategic deal that SAP's regional leadership was incentivised to support with exceptional pricing.

The Terms Secured

Migration Credits: The Timing Dimension

One of the most commercially significant elements of the negotiation was the application of migration credits for the client's existing SAP ECC perpetual licence investments. SAP offers migration credits that allow customers to convert the value of existing perpetual licences toward the cost of a RISE subscription, reducing the net cost of the transition. These credits decrease by approximately 10 percent per year of delay — meaning a migration completed in 2025 receives materially more credit than the same migration completed in 2027.

The client had been evaluating its migration options for eighteen months without committing to a timeline. This delay had already cost approximately 10 percent of available migration credits. Committing to the RISE agreement in SAP's Q4 2025 — before the next 10 percent annual reduction — secured credits at the 2025 rate for the full on-premise licence estate, producing an additional first-year cost reduction of approximately €640,000 compared to the equivalent commitment made twelve months later.

The migration credit structure is a fact that SAP does not volunteer proactively in conversations about "taking time to evaluate." Every year of evaluation is a year of credit reduction. Organisations that have been considering RISE migration for more than eighteen months are already carrying a credit deficit relative to where they started — and that deficit compounds annually until migration is completed.

What Regulated Industries Should Know About SAP Sovereignty Pricing

The pattern we see across regulated industries — energy, utilities, financial services, healthcare, and defence supply chain — is consistent: SAP leads with Sovereign Edition when sovereignty is mentioned, presents the premium as technically required, and does not surface alternative deployment options unless directly challenged by a client with independent technical expertise.

The commercial reality is more nuanced. European data sovereignty requirements vary significantly by industry, by data classification, and by the specific regulatory framework applicable to the organisation. What GDPR requires, what NIS2 requires, what French OIV legislation requires, and what German BSI regulations require are meaningfully different, and the deployment options that satisfy each vary accordingly. A blanket Sovereign Edition recommendation applied to a procurement team without independent regulatory and technical expertise is a commercial strategy, not a compliance assessment.

For regulated organisations evaluating RISE with SAP, the correct sequence is: independent regulatory assessment of actual data sovereignty obligations, then technical evaluation of which deployment options satisfy those obligations, then commercial negotiation based on the compliant architecture — not the premium architecture SAP recommends by default.

The Outcome in Context

The 35 percent cost reduction achieved for this client represents the difference between SAP's Sovereign Edition pricing and a correctly structured Private Edition deployment with contractual data residency guarantees, negotiated at optimal timing against SAP's fiscal calendar, with a credible multi-year commitment and independent regulatory validation of the deployment architecture.

The client received everything the regulatory framework required: primary and disaster recovery hosting confirmed on French territory, contractual data residency guarantees enforceable under French law, and full RISE managed service support at the same SLA levels as the standard offering. The 28 percent sovereign premium was not a reflection of additional value — it was a reflection of SAP's commercial assumption that regulated buyers would not challenge the architecture recommendation. Challenging it produced a 35 percent improvement in a single negotiation cycle.