SAP S/4HANA Migration Negotiation: Controlling the Cost of the Mandated Upgrade

The Negotiation Window Is Real — and Closing

Every SAP account executive will tell you that the window to negotiate a migration deal is closing. For once, they are right. But the closing window creates negotiation leverage for buyers, not just urgency for SAP. Understanding why the window matters — and how to use it — is the starting point for any effective migration negotiation strategy.

SAP's fiscal year ends December 31. Quarter four, running from October through December, is when SAP's field teams are under maximum pressure to close deals and hit their annual quota. Deals that have stalled throughout the year get approved for additional discounts and concessions in the final weeks of the year that would not have been approved in Q1. For large migration deals — RISE contracts, licence conversion packages, multi-year BTP commitments — the Q4 effect can translate to an additional 10 to 20 percent discount on the software component of the deal.

The credit trajectory is equally important. Organisations migrating in 2025 to 2026 are receiving approximately 70 to 80 percent of their net licence value as credit against the new S/4HANA baseline. SAP has signalled that this percentage will decrease as the ECC end-of-mainstream-maintenance date approaches, with estimates suggesting 50 to 60 percent credit for organisations that delay until the final months before the deadline. In simple terms, each year of delay costs you 5 to 10 percentage points of credit on whatever perpetual licence value you hold — which, for a large SAP customer, can represent $5 million to $20 million in incremental cost.

The Licence Baseline: Where Every Negotiation Starts

Before any meaningful negotiation can take place, you need to establish your true licence baseline with precision. This sounds obvious but is consistently under-prepared by organisations entering migration negotiations.

What Counts as Net Licence Value

Net licence value is the amount your organisation actually paid for SAP perpetual licences, as evidenced by invoices and contracts — not the list price of those licences at the time of purchase, not an inflated figure that SAP may present in their migration proposal. The discrepancy between what SAP says your licences are worth and what the invoices and contracts confirm can be material, particularly for organisations that negotiated significant discounts at original purchase or that have acquired additional entities with their own SAP licence positions.

Gather every SAP contract, order form, and licence invoice from your entire SAP history. Build a licence inventory that maps each product, the metric it was purchased under, the list price at time of purchase, and the actual net price paid. This document is the factual basis for your credit negotiation and needs to be prepared before you enter any SAP migration conversation.

Understanding the S/4HANA Licence Baseline Reset

S/4HANA migration is a significant opportunity for SAP to reset your licence baseline — often upward. Under ECC, many organisations were licensed for a defined set of modules at specific named user counts. Under S/4HANA, several factors can create pressure to expand the licence baseline.

First, S/4HANA's Digital Access model — measured by the Digital Document Licence Count (DDLC) metric — creates a new exposure for organisations whose third-party systems access SAP data or trigger SAP processes. Under ECC, indirect access was measured (and disputed) on a named user basis. Under S/4HANA, SAP has moved to a document-count basis. If your environment involves third-party order management, e-commerce, warehouse management, or manufacturing execution systems that interface with SAP, you need to model DDLC exposure before finalising any migration commercial structure.

Second, the RISE bundle includes capabilities — BTP integration, Signavio process insights, SAP Datasphere — that your organisation was not previously licensed for. SAP's migration proposal will often price these as included, but the underlying message is that you are now licensing a broader portfolio. Ensure the RISE bundle breakdown is itemised in full before you assess the migration cost.

Migration Paths and What They Mean Commercially

SAP offers two primary migration paths, each with materially different commercial structures. Understanding both is essential for negotiation.

Product Conversion: Preserving the Perpetual Licence Model

Under product conversion, you convert individual ECC products to their S/4HANA equivalents on a product-by-product basis, maintaining a perpetual licence structure with annual support obligations. The credit applied is your historical net licence value for the specific products being converted. Annual support continues at approximately 22 percent of net licence value on the new S/4HANA baseline.

Product conversion suits organisations that want to maintain the perpetual licence model, have significant ECC investments they want to preserve as credit, and are not ready to commit to RISE's bundled infrastructure and cloud services model. However, SAP is actively steering customers away from product conversion and toward RISE — the commercial incentives for SAP are substantially better under RISE's recurring subscription model.

Negotiation focus under product conversion is on maximising the credit percentage, minimising the net new licence cost for any incremental S/4HANA capabilities, and negotiating the annual support rate. Support at 22 percent of net licence value is SAP's standard rate but can be reduced to 18 to 20 percent for large customers or in competitive contexts.

RISE with SAP: The Subscription Migration

RISE with SAP is a bundled subscription that converts your perpetual licence position into an annual subscription including S/4HANA Private Cloud, infrastructure management, BTP credits, Signavio, and Business Process Intelligence. The credit mechanism applies your historical net licence value as a discount against the cumulative subscription value over the initial contract term.

The key variables in RISE negotiation are the annual subscription rate, the annual escalation clause, the BTP credit allocation, the Signavio entitlement, the infrastructure tier, and the contract duration. None of these variables is fixed — all are negotiable at the time of signing, and almost none are easily renegotiated at renewal.

SAP's standard RISE contracts include an annual price escalation clause of 5 to 7 percent. Over a five-year RISE term, a 6 percent annual escalation means Year 5 costs are 26 percent higher than Year 1. Negotiate an escalation cap at signing — a 3 percent annual cap is achievable in competitive contexts, and a fixed price for the full initial term is achievable for large deals where SAP has strong motivation to close before year end.

Negotiation Levers That Buyers Underuse

Beyond the mechanics of credit calculation and escalation caps, several negotiation levers are available to buyers that are rarely used to their full potential.

Competitive Tension with Rimini Street and Third-Party Maintenance

SAP's annual support obligation — approximately 22 percent of net licence value — is not the only maintenance option available to ECC customers. Third-party maintenance providers, most notably Rimini Street, offer support services for SAP ECC at fees of 50 percent or less of SAP's standard support rate, with service commitments that extend well beyond SAP's mainstream maintenance deadline.

Introducing a credible third-party maintenance alternative into your migration conversation changes the dynamics substantially. From SAP's perspective, an organisation that commits to third-party maintenance is reducing its annual support revenue, potentially for an extended period. That prospect — losing five to seven years of 22 percent annual support revenue — is a significant commercial incentive for SAP to offer better migration terms to customers who demonstrate genuine willingness to use third-party maintenance as a bridge strategy.

You do not need to actually deploy Rimini Street to use this lever. A credible evaluation, a signed evaluation agreement, or a documented board-level consideration of the alternative is sufficient to change SAP's posture in negotiations.

Dual-Use Rights Negotiation

The transition from ECC to S/4HANA typically requires a period during which both systems run concurrently. Standard SAP contracts do not automatically provide dual-use rights — the right to run ECC and S/4HANA simultaneously without incurring licence fees for both. Negotiate dual-use rights explicitly, with a defined time window (typically 12 to 24 months), as part of the migration commercial package. Without this provision, you face the risk of SAP claiming that dual-run constitutes dual-licensing.

BTP Credit Adequacy

RISE bundles a BTP credit allocation, but in the majority of production environments, this allocation is consumed faster than expected. BTP pricing is consumption-based and covers a wide range of services — integration, extension, analytics, workflow, and AI processing. Before finalising RISE terms, map your anticipated BTP consumption based on the integrations and extensions you plan to build, and negotiate the BTP credit allocation explicitly in the contract. Accepting SAP's default BTP credit allocation is almost always insufficient for a mature S/4HANA deployment.

Signavio Entitlement Clarity

SAP includes a Signavio entitlement in some RISE bundles, but the scope of this entitlement varies significantly and is rarely articulated clearly in the RISE proposal. Signavio's full Process Transformation Suite — covering process management, process mining, process intelligence, and governance — is a separate subscription product with material annual fees. Negotiate the Signavio entitlement scope explicitly in the RISE contract: which modules are included, at what user count, and on what renewal terms.

Timing Strategy: Using SAP's Fiscal Year

SAP's fiscal year ends December 31. The company's Q4 — October through December — is consistently its strongest quarter for deal closures, driven by field team quota pressure and discount approval processes that are more generous in the final weeks of the year.

Organisations that begin migration negotiations in Q1 or Q2 of a calendar year and allow those negotiations to reach maturity by Q3 put themselves in an excellent position to close in Q4 with maximum discount. SAP account teams will often accept additional concessions in November and December — extended BTP credits, lower escalation caps, higher licence credit percentages, additional Signavio entitlements — to close a deal that has been progressing through the year.

The converse is equally important: organisations that begin negotiations in Q4 in response to year-end pressure are negotiating from a position of artificial urgency that SAP has created. Starting your migration negotiation planning in Q1 or Q2, with a clear intention to close in Q4, is the most effective single timing decision available to buyers.

The DDLC Risk: Negotiating Digital Access

The Digital Document Licence Count (DDLC) metric is SAP's framework for measuring indirect access to S/4HANA — the usage of SAP functionality by third-party systems that trigger business processes or read data without a named SAP user. Under this metric, specific document types (sales orders, purchase orders, delivery notes, production orders, financial postings) generated or processed by non-SAP systems count against your digital access licence.

In every S/4HANA migration negotiation, the DDLC exposure must be modelled and addressed contractually before the migration agreement is signed. An unresolved DDLC position will generate an audit claim after go-live, and the audit cost in a post-migration environment — where SAP can argue that the new system has deployed digital access capabilities — is significantly higher than negotiating a resolved DDLC licence at migration.

The negotiation approach is to document your third-party integration landscape, estimate your annual digital document volume by document type, and present SAP with a documented DDLC position as part of the migration commercial package. SAP will then price DDLC licences — typically on a tiered annual basis per document type — within the migration deal. This converts an open-ended audit risk into a defined, contracted cost.

Seven Negotiation Principles for S/4HANA Migration

Start preparation at least six months before you want to sign. A migration negotiation that begins the month before the intended signing date is a negotiation that SAP controls. Preparation — licence baseline validation, RISE bundle analysis, BTP consumption modelling, DDLC assessment — takes time and generates the information that powers effective negotiation.

Never establish urgency before establishing leverage. SAP's account teams are trained to convert customer urgency into deal velocity. Once SAP knows you are under internal pressure to sign by a specific date, discount approvals tighten. Create leverage — through competitive alternatives, fiscal year timing, third-party maintenance evaluation — before disclosing your internal timeline.

Itemise the RISE bundle before evaluating the price. An aggregate RISE subscription price cannot be negotiated effectively. Require SAP to break down the RISE pricing into its component parts: software subscription, infrastructure, support, BTP credits, Signavio, and escalation schedule. You can only negotiate line items that are visible.

Validate credit calculations independently. SAP's licence credit calculations are based on their own records of your licence history. These records are not always accurate, and the methodology SAP applies to credit calculation is not always the most favourable to the customer. Independent validation of the credit calculation before entering negotiations has consistently identified additional credit entitlement for our clients.

Negotiate dual-use rights, BTP credits, and Signavio scope explicitly. These three elements are routinely under-negotiated or left as boilerplate in migration contracts. Each has material financial consequences over the life of the contract.

Address DDLC in the migration deal, not in a post-go-live audit. Resolving DDLC exposure at migration is categorically cheaper than resolving it in an audit context. An unresolved DDLC position is an audit liability that SAP retains the right to pursue post-migration.

Engage independent advisory support with no SAP or SI affiliation. Migration negotiations involve SAP commercial teams, your system integrator, and your internal procurement and IT teams — all of whom have different objectives and relationships. Independent advisory support with no financial relationship with SAP or the implementation partner provides the objective commercial analysis and negotiation expertise that is otherwise absent from this process.