The right SAP licensing partner is the one that can translate your existing contract estate — classic named users, engines, digital access exposure — into the FUE arithmetic of RISE and GROW before SAP’s own commercial team does that translation for you. Nearly every SAP engagement in 2026 is a conversion across contract generations with a deadline attached, so test candidates on conversion mechanics and measurement discipline, not on generic SAM credentials.
Published 21 October 2025 · Last reviewed 4 November 2025
SAP’s commercial model is mid-migration, and so is almost every customer. Estates built over decades on classic named-user categories and engine metrics are being repriced into Full Use Equivalents as customers weigh RISE with SAP, GROW with SAP, or a private-cloud and on-premise path for S/4HANA — all against the end of mainstream maintenance for most ECC releases in 2027. Layer on digital access, which charges for documents created by connected non-SAP systems rather than for people logging in, and the question every buyer faces is the same: what does our old paper become in the new model, and who controls that arithmetic?
That is why partner selection in SAP work is a test of translation skill. A firm can be fluent in Microsoft or Oracle mechanics and still misread an SAP engine metric, miscount a document type, or accept SAP’s first FUE conversion as if it were a fixed exchange rate rather than an opening position. The SAP vendor hub maps the full landscape; if you have not yet decided which of the seven services you are actually buying, start with the cross-vendor framework in how to choose a software licensing consultant and come back for the SAP-specific layer below.
General information for buyers, not legal or licensing advice; no firms are named here. The directory, filtered to SAP, lists the firms covering this vendor — alphabetical, balanced pros and cons, listed not ranked.
Contract-generation literacy. Your entitlements live in agreements signed under different price lists, user definitions and engine metrics. A capable partner reads the whole stack — including the conversion and exchange clauses SAP added along the way — before modelling anything. Ask candidates what documents they request first; the answer reveals whether they think in estates or in price lists.
FUE conversion arithmetic. RISE and GROW price in Full Use Equivalents, and the ratios that turn your named-user categories into FUEs are where value is won or lost. Firms that have negotiated these conversions repeatedly know which assumptions move, which user populations are routinely over-classified, and how shelfware should be treated in the exchange. Firms that have not will discover this on your contract.
Digital access exposure modelling. Counting documents created by interfaced systems means tracing integration architecture — middleware, e-commerce front ends, EDI flows — not running a user report. Verify hands-on work: which document types, what tooling, what conversion or adoption-program terms they have actually negotiated when exposure surfaced.
Measurement discipline. The annual system measurement and SAP’s measurement tooling produce the data SAP sees. Engine metrics the tools capture poorly, user classifications no one has maintained, and orphaned accounts all flow straight into your declared position. A partner who treats the measurement as routine admin, rather than as the most consequential document you send SAP each year, is the wrong partner.
Credibility in both directions. The cloud decision is not foregone. A firm that has steered some clients into RISE and kept others on-premise — and can explain both calls — is giving advice. A firm whose every engagement ends in the same destination is selling a destination. The same both-ways test applies at renewal: ask for one engagement where walking toward SAP’s offer was the right answer and one where holding position was.
| YOUR SITUATION | CAPABILITY TO TEST FOR | EVIDENCE TO ASK FOR |
|---|---|---|
| Weighing RISE / GROW vs staying put | FUE conversion modelling, cloud-vs-on-premise economics, exit and portability terms | Recent conversions negotiated, with clients steered both into and away from RISE |
| ECC to S/4HANA migration | Contract-conversion mechanics, credit treatment of existing licenses, maintenance-clock strategy | Migration negotiations completed since the 2027 deadline became binding reality |
| Digital access question or claim | Document-type counting, integration tracing, conversion-program negotiation | Indirect-use exposures modelled and resolved, with method described (labelled indicative) |
| Measurement request or audit notice | Measurement-tool fluency, declaration strategy, scope control with SAP’s compliance organisation | Measurements and audits managed end to end — see SAP audit defense |
| Estate cost out of proportion | User reclassification, engine right-sizing, shelfware strategy ahead of any conversion | Optimization work done before a renewal, where the savings survived SAP’s scrutiny |
One firm rarely covers every row with equal depth. The discipline is matching the row you are in to demonstrated work in that row — a brilliant measurement firm is not automatically the right negotiator for a RISE conversion, and vice versa. The SAP license negotiation page lists the firms doing the deal-side work.
The provider types are the usual five, but SAP redraws their conflict map. The largest conflict surface in SAP work is not the reseller desk — it is the implementation pipeline. The same houses that advise on licensing strategy often hold S/4HANA migration practices, RISE delivery partnerships, or SAP alliance relationships measured in project revenue, and a migration that gets larger is rarely bad news for the firm advising on it. That does not disqualify Big 4 and global SI-attached advisors — their multi-country reach is real and sometimes necessary — but it makes the written conflicts statement non-negotiable: what revenue, from SAP or from SAP-dependent work, does the advising entity and its affiliates receive?
Independent boutiques dominate the adversarial and measurement-heavy end, many founded by alumni of SAP’s own license organisation or of the big SAM practices; history is an asset when it is history, which is the distinction the independence test exists to draw. Law firms enter where indirect-use exposure hardens toward dispute — digital access disagreements have reached court before, and privilege has real value once positions are exchanged; most contested matters pair counsel with a consultancy rather than choosing between them. SAM tooling measures user activity and some engines well, but no tool reads a 1998 ordering document or negotiates a conversion ratio; treat tooling as evidence infrastructure, not advice.
Whatever the badge on the firm, insist the named individuals carry the SAP scar tissue. SAP practices are small even inside large organisations, and the partner who pitched is not always the analyst who will defend your FUE model.
1. “Walk us through a FUE conversion you negotiated — what did SAP’s first model assume, and what moved?” If nothing moved, the firm watched a conversion rather than negotiated one.
2. “What revenue do you or your affiliates receive that depends on SAP — implementation, resale, alliances, RISE delivery?” In writing, before engagement.
3. “How would you establish our digital access exposure, concretely?” Listen for document types and integration tracing, not reassurance.
4. “Show us one client you kept on-premise and one you moved to RISE. Why each?” The both-directions test in its simplest form.
5. “What do you do with our annual measurement before it goes to SAP?” A practiced firm describes review, reclassification and engine-metric checks unprompted.
6. “Who exactly does the work, and how many live SAP matters do they carry?” Logos do not analyse contracts; named people do.
7. “Where does your role stop and a lawyer’s begin?” Firms that have done contested indirect-use work answer this precisely.
The red flags are the mirror image: a conversion model produced before your contract stack has been read; savings guarantees ahead of any data; “we have a special relationship with SAP” offered as the credential; pressure to accept SAP’s migration timeline as fixed; gain-share-only pricing pushed hard for advisory work; and vagueness about who currently pays the firm. Fee structures — fixed, day-rate, retainer, gain-share — each carry incentives, unpacked in fee models explained; no prices are published here.
Adjacent guides and the working pages for this vendor, plus the directory filtered to SAP.
The full SAP landscape on this site →
The firms doing renewal and contract work →
The renewal-specific selection layer →
Deal-side selection for new purchases →
Who your advisor really works for →
Every field guide on the site →
Yes, and ideally before SAP runs its own conversion model for you. The FUE translation of your existing named users and engines is negotiable, and the assumptions baked into the first model tend to anchor everything that follows. A partner engaged after the proposal lands is renegotiating someone else’s arithmetic; one engaged before it lands shapes the arithmetic itself.
Contractually they are distinct: the annual measurement is a self-declaration exercise run through SAP’s measurement tools, while an audit is a formal compliance review with broader scope. In practice the measurement feeds the same machinery — what you submit can trigger commercial follow-up, and engine metrics the tools measure poorly are often where disputes start. Experienced advisors treat the measurement with audit-grade care.
It is part of competent SAP advice, but verify it specifically. Digital access moves the charging question from who logs in to which documents your connected systems create, and modelling that exposure requires tracing integration architecture, not reading a price list. Ask candidates how they would count your document types and what conversion options they have actually negotiated.
They can advise on configuration, but an integrator whose revenue depends on SAP project work faces a structural pull when licensing advice points away from the bigger migration or the larger subscription. For commercial decisions — RISE versus staying on-premise, conversion timing, measurement disputes — most buyers keep the licensing seat separate from the implementation seat.
No, but it sets the negotiation clock. Mainstream maintenance for most ECC releases runs to the end of 2027, with extended options beyond that at a premium. The closer you are to the deadline, the fewer credible alternatives you hold in a conversation with SAP — which is exactly why the timing of your decision is itself a negotiation asset worth professional attention.
Alphabetically, with balanced pros and cons on every profile — independence stated as a pro, reseller, Big-Four or vendor-side ties as a con. Listed, not ranked; the directory is free for buyers and takes no money from software publishers.
Tell us which SAP decision you are facing — RISE or GROW, S/4 migration, digital access, measurement or renewal — and we will route your brief to firms that genuinely cover it, with each firm’s independence status stated on its profile. Free for buyers, no vendor ever sees your brief, no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.