SAP S/4HANA Selective Data Transition: Licensing Costs and Negotiation Tactics

What Is SAP S/4HANA Selective Data Transition?

SAP S/4HANA migration comes in three main flavours: greenfield (new implementation from scratch), brownfield (technical system conversion of your existing ECC system), and selective data transition (SDT) — sometimes called the "shell conversion" or "carve-and-merge" approach. SDT sits between greenfield and brownfield: you technically convert your system but selectively migrate only the business objects, data, and processes you want to carry forward into S/4HANA.

SAP and its certified SDT tooling partners — primarily IBM, Accenture, and a handful of specialist firms — facilitate this approach. The Unified Journal (ACDOCA), the new data model, and the Universal Journal entry structure in S/4HANA mean that historical data must be restructured during migration. SDT allows organisations to harmonise business units, merge legal entities, re-org post-acquisition, and clean historical data simultaneously with the technical migration.

From an SAP licensing perspective, SDT creates a discrete commercial event. You are not simply converting an existing deployment. SAP's position is that SDT can trigger new licensing discussions, changes to your RISE entitlements, and re-baseline your Named User counts — all of which creates opportunity for SAP's commercial team to expand your contract.

How SDT Affects Your SAP Licensing

The licensing implications of Selective Data Transition are broader than most enterprises anticipate. Here are the key areas where your contract value can expand during an SDT project:

1. RISE with SAP and the Conversion Path

If you are migrating to RISE with SAP (SAP's cloud-bundled subscription), your existing on-premise licences do not convert to RISE entitlements on a one-for-one basis. SAP uses a conversion methodology that maps your existing Named Users, FUE (Full Use Equivalents), and engine licences to RISE entitlements — but this mapping is commercially negotiated, not technically mandated. SAP's first proposal will nearly always include additional modules, higher user counts, or premium subscription tiers that your existing deployment does not require.

2. Re-Baselining Named Users During SDT

SDT typically involves harmonising user populations across legacy systems. SAP's position is that any harmonisation exercise requires a new user count assessment. If you are merging two SAP ECC systems into one S/4HANA tenant, SAP will often propose that the combined Named User count equals the sum of both systems' user populations, rather than the deduplicated active user count. This is a significant and unnecessary cost increase that should be challenged in every SDT negotiation.

3. SAP BTP Entitlements

Almost every SDT project involves some use of SAP Business Technology Platform (BTP) — for data migration services, integration, or the migration tooling itself. SAP's sales teams are incentivised to attach BTP capacity and services to SDT deals. These BTP entitlements are often sized well beyond what the migration itself requires, and the unused capacity rarely converts to commercial credit. Scrutinise every BTP line item in an SDT proposal.

4. Extended Maintenance During Transition

SDT projects typically take 18–36 months. During this period, your existing ECC system remains in production, often requiring extended maintenance or extended use rights. SAP charges for these rights separately in some contract structures. Ensure any SDT negotiation explicitly covers the maintenance obligations during the parallel running period without double-charging.

SAP's Commercial Tactics in SDT Negotiations

Understanding how SAP's commercial team approaches SDT negotiations is the first step to neutralising their advantage.

The "Migration Factory" Bundling Approach

SAP and its certified SDT partners often package the migration tooling, consulting services, and new software licences into a single commercial bundle — sometimes marketed as a "Migration Factory" or "Transformation Package." This bundling makes it difficult to assess the value of individual components and almost always includes licence uplift that is not strictly necessary for the migration. Always unbundle these proposals and assess each component independently.

Urgency Pressure Around ECC Maintenance Deadlines

SAP's commercial team will reference the SAP ECC end of mainstream maintenance deadlines to create urgency. The implication is that failure to commit to an SDT deal quickly will leave you stranded on an unsupported system. This pressure is partly legitimate but is also used commercially to accelerate contract signature before buyers can conduct proper due diligence on the commercial terms. Do not allow maintenance deadline pressure to compress your negotiation timeline.

Competitive Displacement FUD

SAP sales reps will often introduce competitive displacement concerns — suggesting that competitors in your industry are accelerating their S/4HANA migrations and that delay risks a competitive disadvantage. This is a classic sales tactic. Your migration decision should be driven by your business case, not by anecdotes about competitor timelines.

The Re-Measurement Risk

SAP's USMM (Usage and System Measurement) tool and LAW (Licence Audit Workbench) will generate a measurement of your current consumption during the SDT preparation phase. SAP's position is that this measurement establishes the baseline for your new S/4HANA entitlements. In practice, initial USMM measurements almost always show apparent over-consumption relative to your current licence position — because the measurement tools count in ways that differ from how licences were originally purchased. Challenge every line of a USMM-derived baseline before accepting it as the starting point for contract negotiations.

SDT Negotiation Tactics That Reduce Cost

Based on our experience negotiating SAP S/4HANA migration contracts, here are the most effective tactics for reducing SDT licensing costs:

Establish Your "Clean" Baseline Before Discussions Begin

Before engaging SAP commercially on SDT terms, conduct an independent analysis of your current licence entitlements versus your actual consumption. This independent measurement — not the USMM output — should be your baseline. Enterprises that go into SDT negotiations with a validated, independent baseline save 10–20% versus those who accept SAP's measurement as the starting point.

Right-Size the Named User Count at Migration

SDT is an ideal moment to right-size your SAP Named User licensing. Many enterprises carry Named Users who have left the business, changed roles, or whose access patterns have changed. A proper Named User clean-up exercise before committing to S/4HANA entitlements can reduce ongoing licence fees by 15–25%. SAP will not volunteer this opportunity — you have to drive it.

Separate Software from Services

Never allow SAP or a system integrator to present SDT costs as a single blended number. Separate the software licence or subscription cost, the migration tooling cost, the professional services cost, and the ongoing maintenance obligations. Each has different negotiation dynamics and different market benchmarks.

Negotiate Multi-Year Pricing Protections

S/4HANA subscription agreements — especially under RISE — include annual price escalation clauses. These escalation caps are negotiable. Industry standard is a cap of 3–5% per annum. SAP's standard terms often include higher caps or leave escalation to SAP's discretion. Lock in price escalation caps before you sign, not after.

Secure Credits for Unused BTP Capacity

If BTP capacity is bundled into your SDT deal, negotiate for explicit provisions that allow unused BTP credits to roll forward, convert to cash equivalent, or offset future licence fees. Without these provisions, unused BTP capacity in SDT projects is effectively a gift to SAP.

RISE with SAP vs On-Premise for SDT: The Commercial Decision

Many SDT engagements involve a parallel decision: migrate to RISE with SAP (cloud subscription) or maintain on-premise S/4HANA licences. The commercial implications of this decision are significant and should be modelled over a minimum 5-year horizon.

The "right" answer depends on your specific SAP estate size, existing licence investment, infrastructure strategy, and negotiation position. There is no universally correct answer — but enterprises that make this decision based primarily on SAP's commercial presentations, rather than independent financial modelling, consistently make suboptimal commercial choices.

What to Demand in Every SAP SDT Contract

Before signing any SAP S/4HANA Selective Data Transition contract, ensure the following provisions are in place:

• Named User baseline: Agreed and independently verified, not USMM-generated without challenge
• Price escalation cap: Maximum 3–4% per annum for RISE subscriptions, explicitly stated
• BTP credit portability: Unused BTP credits roll forward or can offset future fees
• Parallel running rights: Explicit rights to run ECC in production during migration without additional licence fees
• Licence conversion credit: Full credit for existing on-premise investments when converting to RISE
• S/4HANA access rights: Defined scope of S/4HANA modules included in RISE subscription versus requiring add-on purchase
• Exit provisions: Data portability and exit terms clearly defined — particularly important in RISE contracts
• True-up timing: Annual true-up cycle defined, with limits on retroactive charges

Key Takeaways

• SDT is a commercial trigger SAP uses to expand contract value — enter negotiations with independent advisors, not just SI consultants
• Never accept a USMM-based baseline without independent challenge — initial measurements almost always overstate consumption
• Right-size Named Users at migration — SDT is your best opportunity to reduce ongoing annual licence fees
• Unbundle SDT proposals: negotiate software, tooling, and services separately
• Negotiate price escalation caps, BTP credit portability, and parallel running rights before signature
• Model RISE vs on-premise over 5+ years — subscription costs frequently exceed on-premise TCO at scale
• Our SAP negotiation service delivers average savings of 22–35% on SDT engagements on a gainshare basis