RISE with SAP, third-party support, and replacing workflows look like a choice between price tags. They're really a choice about control: who decides when you upgrade, who writes your tax updates, and how hard it is to leave later. This framework lays out what you get and give up with each, the criteria that point to each one, and the red flags to look for in a proposal.

The short answer

  • RISE buys a managed, current SAP platform, in exchange for a subscription that's hard to shrink or leave.
  • Third-party support buys lower fees on the system you already have, in exchange for no new SAP releases.
  • Replacing workflows buys ownership of the processes that matter, in exchange for building, hosting, and supporting them.

What changed in 2025 and 2026

Two shifts should shape your decision. First, SAP retired the RISE with SAP product package in 2025 and replaced it with SAP Cloud ERP Private, priced on full-use equivalents (FUEs). RISE lives on as the name of the overall program. According to The Register, Gartner warned that some volume tiers may pay higher list prices per FUE, and DSAG, the German-speaking SAP user group, said FUE costs more than the old RISE Premium package. SAP says the change doesn't mean a direct increase or decrease in cost.

Second, in July 2026 the European Commission accepted binding commitments from SAP on on-premise maintenance. Per SAP's support page, SAP now waives the reinstatement fee for customers returning to SAP support, and caps back-maintenance at the lower of 50% of the fees for the time off support or six months of payments. The commitments apply globally to on-premise products for 10 years. As CIO Dive notes, they don't cover SAP's cloud offerings. The practical result: third-party support is much less of a one-way door than it used to be, and RISE exit terms are still whatever you negotiate.

Three dates that change the SAP decision
  1. 2025RISE package retired

    Replaced by SAP Cloud ERP Private, priced per full-use equivalent.

  2. July 2026EU accepts SAP commitments

    No reinstatement fee to return to SAP support, and capped back-maintenance.

  3. December 2027ECC mainstream maintenance ends

    Extended maintenance runs through 2030 at a premium.

Sources: The Register; SAP Support; SAP News.

What you get and what you give up

FactorRISE with SAPThird-party supportReplace workflows
ControlSAP runs the infrastructure and technical operations, in a cloud account SAP ownsYou keep your system and hosting; the provider supports what you runYou own the code and data model for what you replace
UpgradesSAP executes technical upgrades; testing and preparation are yours; at least one upgrade every 7 years to stay in mainstream maintenanceNo new SAP releases; you stay on your current versionOn your schedule, at your cost
Legal and tax updatesDelivered by SAPDelivered by the provider; scope varies by provider and countryYours to maintain, or left on the packaged system you keep
Lock-inHigh: multi-year subscription, SAP-hostedLower since the 2026 commitmentsLow vendor lock-in; you depend on your team or partner instead
Cost modelSubscription per FUE, renewed each termAnnual fee, often well below SAP maintenanceOne-time build, plus hosting and support; SAP fees continue on what isn't replaced
ExitNegotiate exit and data return before signingReturn to SAP with no reinstatement fee and capped back-maintenanceKeep running it, or move it; it's yours

Upgrade terms from SAP Learning; account ownership from AWS documentation for RISE on AWS. We offer the third option, so weigh our view accordingly.

A closer look at each

RISE with SAP

RISE bundles the software, hyperscaler infrastructure, and SAP's technical operations under one contract. AWS documentation notes that SAP owns and manages the cloud account where your system runs. SAP's training material says SAP executes the technical upgrade, you can request one upgrade a year, and planning, preparation, and testing stay with you or your partner. S/4HANA moved to a two-year release cycle with seven years of mainstream maintenance per release. It isn't a migration, though. You still pay for the move to S/4HANA on top of the subscription.

Third-party support

Providers take over support of the SAP release you already run, at a lower fee. Rimini Street, which sells this service, says it can cut annual support costs by up to 50%, with tax, legal, and regulatory updates included at no extra charge across more than 150 locations. The Stack reported in 2025 that Rimini extended SAP ECC 6.0 and S/4HANA support through 2040. Spinnaker Support, a competitor, claims an average 60% reduction in support fees and lifetime support for your current version, with tax and regulatory updates tailored to each customer. These are vendor claims. Test them against your actual bill and your countries.

Replacing workflows

You rebuild your operational workflows as software you own, starting with the ones where SAP fits worst, with AI agents built in. Finance and payroll move to cloud products, and SAP is switched off in 24–30 months. In our worked example for a $200M manufacturer, that comes to about $5.8M over five years, including our fees.

Decision criteria

RISE fits when

  • You've decided to stay on SAP for the long term, and your processes run close to standard.
  • You want to stop running infrastructure and Basis operations yourself.
  • You have budget for the migration and a team that can test every upgrade.

Third-party support fits when

  • ECC does what you need, and your problem is the fee, not the functionality.
  • You need time to plan a move and want to spend less while you do.
  • You've confirmed tax and legal coverage for every country you operate in.

Replacing workflows fits when

  • A handful of workflows carry most of your custom code and most of the complaints.
  • Those workflows set you apart, such as scheduling, field operations, pricing, or asset management.
  • You want automation and AI working on data you control, and you can run a staged program with the old system live.

Combining them

These options aren't exclusive. You can put ECC on third-party support to cut fees now and replace workflows in stages. One catch: you generally can't drop SAP licenses module by module. SAP's support page lists specific cases where partial termination is allowed, such as failed implementations or a workforce reduction of more than 10%. Check your contract before you model savings from retired modules.

Red flags in a proposal

  • RISE with no cap on renewal increases. UpperEdge, an advisory firm, notes SAP's standard language lets it raise subscription fees at each renewal.
  • RISE pricing built on pre-2025 packaging, or an assumption that "managed" includes application management, testing, or functional changes.
  • Third-party savings quoted against list price instead of your actual maintenance bill, or vague tax coverage for your jurisdictions.
  • A big-bang rewrite of the whole ERP, or a build price with no hosting, support, or plan for who maintains it.
  • Any business case that assumes SAP fees stop before the modules are actually retired.

Put your own numbers in

Each option's cost depends on figures only you have: your net license value, maintenance rate, renewal date, and which workflows you'd move first. Run all three paths over five years before you pick one.

Six questions to settle first

  1. How long do we intend to stay on SAP? The answer rules options in or out faster than any price.
  2. Which workflows carry our custom code and our biggest complaints?
  3. What's our real annual maintenance bill, and when does it renew?
  4. Who handles tax and legal changes in each scenario, country by country?
  5. What does exit cost under each option in year three and year five?
  6. Can we combine options, and what does our contract let us retire?

Where to go from here

Pick the option that fits how long you'll stay and how much of the system you'd change. If you want an outside view, tell us what you run and what you pay, and we'll tell you honestly which path we'd take. You can also see how a staged replacement works on our Escape SAP page.

Sources