SAP's mainstream maintenance for ECC 6.0 ends on December 31, 2027. That date is real, but it isn't a cliff. ECC keeps running, and you have more than one way forward. What changes is what you pay, what support you get, and how much negotiating room you have left.

The short answer

  • You have five realistic paths: extended maintenance, the RISE transition option, S/4HANA, third-party support, or replacing the workflows that matter with software you own.
  • The first and fourth buy time. The second and third keep you with SAP. Only the last ends the fees for good.
  • The right answer depends on how customized your system is and how long you intend to stay on SAP at all.

What actually ends in 2027

After December 31, 2027, ECC 6.0 leaves mainstream maintenance. Nothing switches off that day, and SAP has offered optional extended maintenance from 2028 through 2030. It's widely reported at about two percentage points on top of your maintenance base, though quotes vary by contract.

Check your enhancement-package level with SAP before you plan around these dates, because older releases aren't treated the same way as current ones.

SAP has also introduced a separate SAP ERP, private edition, transition option. It's easy to misread as a longer ECC deadline. It's a paid RISE subscription for customers already on the path to S/4HANA, not an extension of on-premise maintenance.

How long each SAP ECC support route lastsSupport and subscription windows, by year
202520282031203420372040Mainstream maintenanceMainstream maintenance: Ends December 31, 2027Ends December 31, 2027Extended maintenanceExtended maintenance: 2028 to 2030, at about 2 points more2028 to 2030, at about 2 points moreRISE transition optionRISE transition option: Through 2033; later reports say 2035RISE transition option: Through 2033; later reports say 2035Through 2033; later reports say 2035Third-party supportThird-party support: Rimini Street offers support through 2040Rimini Street offers support through 2040

Sources: SAP via E-3 Magazine; SAP News; The Stack. The transition option is a RISE subscription, not ECC maintenance.

View the data
RouteWindow
Mainstream maintenanceTo December 31, 2027
Extended maintenance2028–2030, about 2 points more
RISE transition option2031–2033 (later reports: to 2035)
Third-party support (Rimini Street)Through 2040

The five options, side by side

These figures use an illustrative mid-size customer with about 500 users and $5M in net license value. Standard SAP maintenance at about 22% comes to roughly $1.1M a year.

OptionIllustrative costHow long it lastsThe catch
Extended maintenanceAbout $1.2M a year, at roughly 24%Through 2030Buys three years, and the decision still waits for you at the end.
RISE transition optionQuoted by SAP, at a reported premiumFirst announced through 2033; later reports say 2035Systems must reportedly be on private edition, on HANA, by the end of 2030.
Migrate to S/4HANA$2M–$5.5M one-time; complex migrations $5M–$14MLong termMedian delivery of 14–20 months, and SAP fees continue after go-live.
Third-party supportQuoted by provider; Rimini Street claims savings of up to 90%Rimini Street offers support through 2040You stay on ECC, without new releases from SAP.
The Escape PathAbout $5.8M over five years in our worked example, including our feesPermanent: SAP is switched off in 24–30 monthsYou own and run a platform, and finance and payroll move to cloud products.

Third-party planning estimates, not SAP price lists. Your figures will differ. We offer the last option, so weigh our view with that in mind.

How to choose

Extended maintenance suits a planned exit

It makes sense when you already have a destination and need more runway. Without a plan, it's three more years of fees at a higher rate.

The RISE transition option suits a committed SAP customer with a very large migration

It's built for organizations that have decided on S/4HANA but can't finish in time. Reported eligibility conditions are strict, so confirm them with SAP early.

S/4HANA suits a business that runs close to standard

If your processes fit the standard model and you want to stay in the SAP ecosystem, migration is the direct route. Heavy customization is what pushes projects into the higher cost tier.

Third-party support suits a stable system

If ECC does what you need and you don't expect major change, it can cut your bill sharply. Check how you'd handle legal and tax changes before committing.

Replacing workflows suits a business that has outgrown the fit

Most companies don't need to rebuild an entire ERP. The strongest candidates are the workflows that differentiate you and that you've already paid to customize. Rebuild the operational workflows in waves, starting with those, and move finance and payroll to proven cloud products instead of rebuilding them.

Five questions to answer before you sign anything

  1. What does our contract actually say? Confirm your net license value, maintenance rate, and renewal terms.
  2. Which modules do we really use? Usage data often shows you're paying for far more than you run.
  3. How much custom code do we carry? It drives migration cost, and it shows you what the business has been trying to build.
  4. What is the five-year cost of each path? Compare totals, including subscriptions, integrators, and staff, not just the first invoice.
  5. Are we deciding, or is the deadline deciding for us? Starting early protects your options and your negotiating position.

Where to go from here

Start with the numbers. If you'd like a second opinion on your situation, tell us what you run and what you pay, and we'll tell you honestly whether moving off SAP makes sense. You can also see how a staged approach works on our Escape SAP page.

Sources