What happened
On 18 November The Register published an interview with Thomas Henzler, the new chair of DSAG, the SAP user group for Germany, Austria and Switzerland. The article is about who can actually use SAP's AI on their own servers. SAP can now put its AI agent tooling, including Joule Studio 2.0, in front of customers still running SAP ECC or on-premise S/4HANA. Henzler's complaint is the price of entry. Access needs a substantial RISE with SAP commitment and a minimum ratio of cloud spend to on-premise maintenance. A company with a single ECC system would have to move all of its on-premise maintenance into a cloud subscription to qualify. In Henzler's view, the offer makes sense for large groups with several SAP systems that can move one at a time. He says it doesn't make sense for most mid-sized customers.
SAP's reply to The Register was that the offer separates the money commitment from the timing of the technical migration. A single-system customer can qualify if it meets the commercial and technical tests. SAP's own line was short: "Eligibility is not determined by the number of ERP instances."
The offer itself dates from SAP Sapphire on 12 May. SAP's Sapphire release said on-premise ECC and S/4HANA customers who commit to moving most of their current systems to SAP Cloud ERP would get access to selected AI scenarios. The release didn't list which scenarios were included or what the commitment terms were. DSAG's response at the time called the offer a useful interim step. DSAG described the condition as a RISE contract that converts at least 50% of contract volume into cloud subscriptions. DSAG also said the covered scenarios, technical requirements and contract wording were still unclear, and that it was still negotiating the details with SAP.
What the fine print says
ERP News summarised the terms SAP published in its October 2026 supplemental terms for SAP Cloud ERP Private. If a customer's first qualifying cloud ERP subscription started on or after 7 October 2024, the customer has to convert at least half of its annual on-premise support fee into eligible cloud ERP subscriptions. Customers who subscribed before that date have a second route: their annual Core Cloud ERP fee has to equal at least half of their on-premise support fee. ERP News gives a hypothetical: a firm paying $200,000 a year in qualifying support would need to convert at least $100,000 of it. Subscriptions to SuccessFactors, SAP Analytics Cloud, SAP Business Technology Platform or Business Data Cloud don't count toward the threshold on their own.
Software versions matter too. ERP News reports that ECC systems need Enhancement Package 8 at minimum, and on-premise S/4HANA needs the 2023 release with maintenance continuing past 2026. Individual AI agents can have extra requirements, listed in SAP's AI Catalog in the Discovery Center. SAP hasn't published a list price for any of this. Each customer has to get its own quote.
Why NZ SAP customers should pay attention
In New Zealand and Australia, many SAP sites are single ECC systems run by mid-sized manufacturers, distributors, utilities and public bodies. That's the group Henzler says the commercial model leaves out. These customers are also up against SAP's maintenance dates. According to SAPinsider, mainstream maintenance for ECC ends at the end of 2027. Extended maintenance runs to the end of 2030 at an extra two percentage points on the maintenance basis. Many local SAP owners will be reviewing their SAP contracts within the next 12 months anyway. SAP's AI terms will shape the timing of those reviews and the size of the commitments.
The awkward part for a single-system site is order of operations. A multi-system group can move one business unit to the cloud, count that subscription toward the 50% threshold, and use AI on the systems still on-premise. A single-system company has nothing to move first. It meets the threshold by signing a cloud subscription covering at least half its support spend, possibly well before the migration project starts. The firm could end up paying for cloud and on-premise support at the same time, and the AI features it signed up for would still depend on which agents SAP supports on its ECC version.
The Register also cites Gartner figures from late 2024: only 39% of roughly 35,000 ECC customers worldwide had bought or subscribed to S/4HANA licences. Most ECC customers still haven't committed, and SAP clearly wants to use AI to move them.
What we'd weigh
For most NZ firms on a single ECC system, the business case for AI agents should be judged separately from the migration decision. AI features with clearly measured value, such as invoice matching, supply disruption planning or service ticket triage, could justify an earlier cloud commitment. A general promise of "SAP AI" shouldn't. The same automation is often available from tools that already sit beside the ERP. Examples include integration platforms, Microsoft's Power Platform, or a well-built process automation layer that reads and writes through SAP's standard interfaces. These options don't change the SAP contract. They do mean extra integration work and someone has to run them.
DSAG's warning cuts both ways. If SAP keeps AI tied to RISE, customers will buy AI from other vendors, and those tools will be hard to remove once embedded. For a NZ owner, the takeaway is to decide where AI logic should sit in your own systems. Don't let SAP's contract terms make that decision for you. Our ERP page explains how we think about building around a core system.
Next steps
- Pull your current annual SAP support fee and work out what half of it is. That's the cloud subscription value you'd likely need to commit to qualify.
- Find out when your first cloud ERP subscription started, if you have one, since 7 October 2024 decides which threshold route applies.
- Confirm your ECC enhancement package or S/4HANA release against SAP's AI Catalog for the agents you actually want, before any commercial conversation.
- Ask your SAP account manager for the AI scenarios available on your installed release, in writing, with a dated quote. SAP hasn't published a public list or prices.
- List two or three processes where you'd use an AI agent, estimate the hours or errors each would save, and compare that saving with the cost of an earlier cloud subscription.
- Price at least one alternative that keeps the AI layer outside SAP, so the RISE offer has something to be measured against.
- Line up these decisions with your 2027 and 2030 maintenance plans so the AI discussion doesn't force a contract change you weren't planning to make.
Sources
- SAP opens AI to on-prem customers, but cloud commitments could shut smaller firms out (The Register)
- How Companies With One ERP System Can Use SAP AI Before Moving to the Cloud (ERP News)
- SAP Sapphire: SAP unveils the autonomous enterprise (SAP News)
- KI auch für S/4HANA-On-Premises-Kunden (DSAG)
- SAP support deadlines 2027, 2030, 2033 (SAPinsider)
Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.
Get my free assessment How we help