Already on S/4HANA: the retained-cost and exit test for SAP Cloud ERP Private

Sarah Chen, Lead SAP Architect, SAPExpert.AI
Decision analysis | 19 October 2026

Thesis — inference: For an organization already running S/4HANA, SAP Cloud ERP Private is principally a decision about transferring operational responsibilities, retaining control and preserving a workable exit—not a demonstrated saving from “moving to cloud.” The decisive questions are which funded activities disappear, which remain, and what the business can lawfully and operationally do after separation or contract end.

This report provides a five-year decision framework for lean SAP teams, strict change-control environments and likely divestitures. The supplied evidence establishes neither a universal savings percentage nor a five-year cost winner.

Recommendation: Shortlist by operating need. Approve only after retained costs, required controls and terminal rights reconcile.

1. Buy an operating model, not a location

For this analysis, distinguish three operating models:

• Self-managed: The customer retains operational accountability and assembles the necessary internal capabilities and external services.
• Partner-managed: A provider operates an agreed scope, with customer responsibilities and service handoffs defined separately.
• SAP-managed: The proposed SAP Cloud ERP Private service transfers the responsibilities specified in its contracted scope.

These are accountability choices, not data-centre labels. A partner proposal is not automatically more controllable, and direct hosting does not establish licence portability. Both propositions require evidence.

The supplied sources use RISE and SAP S/4HANA Cloud Private Edition terminology. Require the exact offered product, incorporated roles-and-responsibilities document and purchased entitlements in every comparison. Do not assume matching product or service rights across differently labelled proposals.

This is an existing-S/4HANA operating-model decision. Do not import an ECC-conversion deadline or conversion saving into its justification. Freeze the required baseline before comparing prices. If current coverage falls short, price that gap: an under-covered operating model is not a cheaper equivalent.

2. The five-year shortlist matrix

Recommendation—not an empirical ranking. Measure five years from the proposed operating-model start; this does not imply a five-year contract. Mandatory controls and lawful continuity are approval gates, not disadvantages to offset with a lower fee.

Run each viable bid through three distinct scenarios:

1. Steady-state operation, including required upgrades, recovery and change controls.
2. Mid-term divestiture, including separation, transitional operation and revised capacity.
3. Contract-end exit, including historical-data retention and eventual decommissioning.

Keep obligations beyond year five visible. Do not invent probabilities, average scenarios without approved assumptions or add mutually exclusive exits together.

3. The retained-work ledger comes before the business case

What the service fee actually establishes

SAP’s general roles-and-responsibilities document, marked July 2026, describes a catalogue requiring customer-specific task selection. Standard Services are covered by the service fee where applicable. Excluded Tasks remain customer responsibilities. Additional and Optional Services are assigned to SAP and carry additional fees; Optional Services require explicit contracting. Availability can differ for sandbox or test environments.

Inference: A subscription quotation does not demonstrate that the entire SAP operating function transfers. Each relevant task needs an owner, applicable service category and cost treatment.

The existing-S/4HANA starting point matters. In ANDSI’s account of Plastivaloire’s evaluation, the company was considering RISE from an on-premise S/4HANA estate. Its CIO expected integrator-provided application maintenance to remain unchanged. That is directly relevant—but remains an expectation, not a verified post-move cost result.

Require a complete financial bridge

Build five annual cash-flow schedules and a separate terminal separation/retention schedule for each viable scenario.

Comparable cost = transition + fully loaded run/change costs + priced exit/retention scenario − enforceable offsets

Reconcile today’s funded operating model with the proposed one, rather than comparing infrastructure and subscription invoices alone.

For each ledger line, identify the current payer and future owner, then classify the expenditure as eliminated, transferred, retained or newly incurred. This exposes costs that move into the subscription without disappearing, and work that remains outside it.

Do not book an FTE saving merely because responsibility changes. Require an actual staffing change, reduced external-services commitment or separately justified redeployment benefit. Show cash savings and redeployment value separately. An accounting shift from capital to operating expenditure is not evidence of lower total cost.

Avoid double-counting bundled services. Treat unresolved charges as approval gaps, not zeroes, and subtract only offsets that are contractually available and usable.

Reject percentages that answer a different question

SAP Licensing Experts’ 20–45% claim concerns alleged overpayment against a properly negotiated RISE contract—not demonstrated savings from selecting self-managed operations. The supplied excerpt contains no reproducible calculation. A contractual discount also does not establish operational equivalence.

Nor can Applium’s historical approximately 20% retained-task claim become a current retained-labour percentage. Task counts and effort are different measures; neither identifies removable posts.

Approval condition: Every claimed saving must identify its cost line, accountable owner, removal date and evidence that expenditure genuinely stops.

4. “SAP handles upgrades” is not a complete control specification

Treat required controls as pass/fail conditions before scoring price. Obtain the applicable service schedule rather than relying on an assurance that upgrades are managed.

SAP’s enhanced managed-upgrade service description, marked 08-2025, offers planning, coordination and technical activities beyond standard SUM execution, subject to purchased usage volume. Adjustments are limited to the specified SAP namespace scope. It excludes hypercare, database migrations and ERP-to-S/4HANA conversions. Non-production execution is during business days/working hours, with a minimum advance planning window of ten business days.

These are boundaries of the enhanced service—not proof that every upgrade requires an additional purchase. Equally, offered scope does not establish achieved downtime, release success or SLA performance.

Before approving any model:

• Verify entitlement: Establish which upgrade services and usage volumes the proposed order includes.
• Allocate the whole change: Name owners for customer modifications, regression testing, business acceptance, contingency and hypercare. Price work not demonstrably included.
• Test the calendar: Reconcile contractual lead times, non-production availability, production windows, freeze periods and emergency changes.
• Contract the handoffs: Specify request ownership, escalation and responsibility when technical execution is complete but business acceptance is not.

Do not interpret a minimum planning requirement as a delivery guarantee. Identify how scheduling conflicts are resolved and who authorizes exceptions.

For strict change-control environments, define the required process independently of the vendor. SAP Private passes if its signed arrangements meet that specification. A partner faces the same test, while self-management must fund the coverage needed to deliver its promised control.

5. Exit requires three independent tests

A successful data export does not establish software-use rights or permission for a divested entity to operate.

Test 1: Software continuity

Establish which existing agreements survive, terminate or change. Document rights retained, surrendered or suspended, what the retained business and buyer may run afterwards, and any replacement or reinstatement cost. Establish replacement-system operating rights separately from rights to receive data.

Test 2: Corporate-change permission

Obtain applicable assignment, consent, change-of-control, divestiture and transitional-operation terms. Check third-party services and permitted capacity reductions. The permitted entities, users and transitional activities must match the proposed separation.

Test 3: Usable data continuity

Specify export content and formats, attachments, metadata, historical retrieval, read-only access where needed, retention periods and deletion arrangements. Acceptance must test usable retrieval—not merely successful delivery of files. Name the owner and cost of continuing archive operation.

Use warnings as clause-checking prompts

The Register’s 2023 report of Gartner’s warning described reduced running-cost control and “no residual rights” in the subscription-exit scenario discussed. This historical, secondary reporting does not establish that a particular already-on-S/4HANA customer loses every pre-existing licence right.

FinOptory describes a divestiture provision involving up to twelve months’ transitional use, two weeks’ advance notice and an exclusion for third-party cloud services. The underlying SAP agreement is not supplied. Treat these details as questions for counsel and procurement—not universal entitlements.

Likewise, E3’s forecast of fee-free switching/exit from 12 January 2027 lacks authoritative legislative text or applicability analysis in this packet. Do not budget a zero-cost exit or infer continuing software/runtime rights from it.

Make the exit executable

Approval condition: Name responsibilities, service availability, deadlines, assistance rates or caps, remaining charges and acceptance tests. Require a priced exit rehearsal with representative extraction and retrieval before relying on the design. Include continuing retention obligations even when they extend beyond the comparison horizon.

BriefGlance’s account of OCI Global reports retirement of legacy ECC and S/4HANA Cloud Private Edition systems following platform changes and divestitures, using Proceed Cella Cloud for historical data. It reports savings but supplies no quantified IT saving or operating-model comparator.

Inference: This illustrates a separate retention and decommissioning workstream. It does not establish Private Edition’s comparative TCO, nor does another hosting model automatically remove that workstream.

6. The strongest counterargument: scarce capacity can justify a premium

A lean team may reasonably prioritize operational capacity over the lowest quoted infrastructure cost. Avasant’s analysis describes coordination of provisioning, security, monitoring and updates under direct hyperscaler operation, whether handled internally or through a provider. It presents SAP-managed provisioning and technical operations as a simplification benefit.

Inference: A verified reduction in coordination burden may justify paying more. If the benefit is resilience or redeployment rather than reduced expenditure, describe it as a capability purchase—not a cash saving. Identify the work released, its intended use and ownership of remaining handoffs. Compare partner-managed operations against the same requirement.

The counterweight is that bundling does not demonstrate superior economics. A four-enterprise conference study using archival cost documents reports SaaS cost advantages in some cases while suggesting IaaS can offer larger companies better cost efficiency and vendor control. Its supplied abstract provides no transferable five-year saving for this audience.

The evidence therefore challenges both sides: unpriced customer coordination weakens a self-managed bid; unchanged application maintenance and retained governance weaken an SAP-managed savings claim.

What would change the conclusion? A reconciled customer-specific cash-flow comparison could establish a cost winner. Signed controls and a lawful, demonstrated separation design could establish an approvable model. A preferred model need not be the cheapest, but any premium should purchase an explicit, accepted capability benefit.

What to do next

1. Issue a common bid pack: Freeze the baseline and three scenarios before requesting comparable proposals.
2. Assign the reconciliation: Operations validates task ownership and coverage; finance validates expenditure removal, continuing costs and enforceable offsets.
3. Close contractual gaps: Legal and procurement verify incorporated documents, control commitments, software continuity and exit obligations. For likely divestitures, apply the continuity gate before commercial scoring.
4. Withhold approval where necessary: Resolve material unpriced work, unsupported savings and terminal-rights gaps. Record any accepted premium as a capability decision rather than relabelling it a saving.

Sources and limitations

This analysis uses only the supplied excerpts, with citations beside material claims. It is not a review of executed customer agreements or live operating performance.

SAP service documents establish offered scope, not achieved outcomes. Document markings are not independently verified publication dates. The general R&R excerpt does not provide complete task allocation or the full Packaged Services definition.

The four-enterprise study has limited generalizability. Adviser and provider commentary carries commercial perspectives; customer expectations and isolated project outcomes are not controlled comparisons.

No controlled five-year comparison for already-on-S/4HANA customers, complete customer licence position or authoritative legal-applicability analysis was supplied. These recommendations are approval conditions—not findings about a particular customer’s costs, rights or performance.