The Digital Access Adoption Programme — SAP’s commercial route for replacing legacy indirect-access exposure with a document-based subscription — is, for many buyers, a sensible commercial outcome. It converts a contingent liability that has lived on the audit risk register for a decade into a measurable annual subscription line. The risk is not whether to convert. The risk is the price at which the conversion is struck. We have seen conversions priced on the SAP-side estimate of document volume that overstated the real volume by a factor of three. We have seen others priced cleanly because the buyer arrived with a measured baseline. The migration sequence below is the one that produces the clean number.
Why SAP wants the conversion
The indirect-access exposure on the historical estate — the unmeasured integrations, the third-party document creation, the RFC traffic into ECC — sits on SAP’s revenue planning as an unrealised number. Converting that exposure into a Digital Access subscription does three things for SAP. It moves a contingent claim into recurring revenue. It locks the document model into the contract for the rest of the term. And it removes the buyer’s ability to argue the historical exposure was never real in the first place. SAP’s sales teams are incentivised to close conversions in the renewal cycle that precedes a RISE migration or an S/4HANA transition, and the commercial packaging often bundles the three together.
The buyer’s task is to convert on the buyer’s measured volume, not on SAP’s implied volume. The two numbers are typically very different.
The four-phase migration sequence
The sequence has four phases: baseline, exposure model, conversion structure, contract close. Each runs three to six weeks. A complete migration cycle, run properly, takes four to six months. Rushed conversions — closed in eight weeks because a renewal deadline was on the table — consistently land at two to three times the price the same conversion would have carried with a measured baseline.
Phase 1: document baseline
The baseline is a count, by SAP system and document type, of the documents created by non-licensed users and processes during a representative twelve-month window. The methodology is described in the digital-access document counting article and in the Digital Access Pricing Decoded white paper. The work uses SAP-provided estimation tools (the Digital Access Estimation Note and the Passport service), validated against the buyer’s own extracts, with carve-outs for documents created by licensed named users, by SAP-to-SAP traffic, and by historical loads.
Phase 2: exposure model
The exposure model takes the baseline and projects it across the contract term, accounting for growth, planned integrations, M&A pipeline, and the S/4HANA migration timeline. The output is a curve of expected documents per year and a 95th-percentile upper bound. SAP’s opening proposal will be sized to the upper bound or above; the buyer’s position is sized to the expected value plus an explicit reserve.
Phase 3: conversion structure
The conversion structure decides three commercial elements. First, the tier structure — whether the buyer takes a single annual tier, a stepped commitment, or a true-up mechanism. Second, the price per document, which is heavily negotiable below SAP’s rate-card numbers in renewal cycles. Third, the carve-outs — the named integrations and document types that are explicitly out of scope for the digital-access count.
Phase 4: contract close
The contract clauses that go into the master agreement at close determine the next decade of exposure. Three clauses matter most. A document-tier cap that fixes the price per document for the term. A measurement-methodology clause that fixes the agreed counting approach. And a carve-out schedule that lists the integrations explicitly outside the digital-access scope. The clause patterns are covered in the contract clauses article.
The baseline measurement work in detail
The single piece of work that determines whether the conversion is fairly priced is the document baseline. The measurement window must cover a full year, ideally calendar year aligned, with explicit notes on any non-representative events — a major data migration, a divestment, an acquisition. For each document type in scope — sales documents, purchase documents, financial documents, material documents, quality notifications, service documents, time-management documents, manufacturing documents — the count is broken down by origin: licensed named user, SAP-to-SAP, third-party integration, manual posting via shared technical user, batch job, RPA process.
Only documents originating from non-licensed users and processes count toward the digital-access volume. Documents created by named users are already licensed under the named-user fee and must be excluded from the digital-access count even though SAP’s estimation tools may report them. This carve-out alone often removes thirty to fifty per cent of the gross volume.
Common over-pricing patterns
Across the conversions we have reviewed, three patterns drive over-pricing. The first is the use of SAP’s Passport estimation without buyer-side carve-outs — the gross number becomes the negotiation anchor and the buyer ends up paying for documents it has already licensed twice. The second is the bundling of the conversion with a RISE migration commitment, where the digital-access pricing is buried in a multi-line subscription proposal and the per-document price is not visible. The third is the failure to negotiate the term price — the buyer accepts the rate-card price on the assumption it is fixed, when in renewal cycles it is discountable by thirty to fifty per cent. The pattern is documented in the logistics firm digital access rebuilt case file.
The negotiation leverage in the conversion cycle
The buyer has more leverage in a digital-access conversion than in most other SAP commercial discussions. The reasons are structural. SAP wants the conversion closed before the next audit cycle. The conversion is often packaged with a RISE or S/4HANA decision that SAP also wants closed. The buyer has the option to do nothing and keep the historical position, which is uncomfortable for SAP because the historical position is an unrealised number. Those three pressures combine into a negotiation window in which document tier pricing, contract clauses, and carve-out schedules are all on the table.
The leverage closes once the conversion is signed. The position at the next renewal will be a re-pricing of the existing model, not a re-opening of the scope. This is why the conversion cycle is the right moment to invest in the measurement work, the contract clause negotiation, and the independent advisory support. The broader leverage pattern is covered in the SAP RISE topic page.
What a good conversion looks like
A well-structured digital-access conversion has six characteristics. A measured document baseline that the buyer can defend in writing. A document-tier that is sized to the expected volume plus a defined reserve, not to the upper bound. A per-document price that has been benchmarked against comparable buyer-side data. A measurement methodology written into the contract. A carve-out schedule listing named integrations out of scope. And a re-measurement clause that triggers a tier review after twenty-four months if the actual volume falls more than a defined percentage below the contracted tier. None of those characteristics is in SAP’s standard proposal. All six are negotiable when the conversion is structured properly.
The internal alignment work that runs in parallel
The migration is not just a procurement exercise. The conversion changes the accounting treatment of the licence spend (from capex-heavy to opex), changes the audit-rights regime, and changes the operational support model. The finance team, the internal audit team, the SAM team, and the IT operations team all need to be aligned before the contract is signed. Finance needs to model the cash impact of the conversion against the existing depreciation schedule. Internal audit needs to confirm the new audit clauses are within the buyer’s risk appetite. SAM needs to understand the measurement methodology that will produce the future true-up exposure. IT operations needs to understand how the digital-access tier interacts with the planned integration roadmap.
The internal alignment work runs in parallel with the SAP-facing negotiation and should be sequenced to close in the same week. Buyers who close the SAP-facing contract before the internal alignment is done typically discover, six months later, that one of the four functions above has a position the contract did not accommodate. The remediation cost — usually a contract amendment under SAP’s unilateral terms — is consistently several times the cost of doing the internal alignment work in advance.
The governance position after the conversion
Once the conversion is signed, the governance discipline shifts. The named-user counts continue to matter, but the digital-access volume becomes the primary commercial variable. The monthly governance pack should report the document volume against the contracted tier, the integration-level breakdown, and the projected year-end position with a confidence interval. The pattern fits into the quarterly forecasting cadence covered in the true-up forecasting article. Without the governance discipline in place, the contracted tier can drift out of alignment with the actual volume in either direction — over-licensing if volume falls, exposure if volume rises — and the re-measurement clause is the only mechanism to recover.
The migration is worth doing. The price at which it is worth doing depends on whether the buyer has measured the documents before the contract is signed.
If a Digital Access conversion is being proposed in the current cycle, the priority is the measured baseline and the contract structure, not the speed of close. The SAP digital access negotiation service page describes how we structure the engagement, and the digital access adoption programme article covers the SAP-side commercial mechanics.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.