SAP ECC End-of-Support in 2027: Your Realistic Options If You Haven’t Started

SAP ECC end of support arrives on December 31, 2027, and if your move hasn’t started, you still have workable options. They cost more and leave less room for error than they did a few years ago. SAP’s mainstream maintenance for ECC 6.0 stops at the end of 2027. What you can do after that depends mostly on your enhancement package and your database. It also depends on how far you’re willing to commit to SAP’s cloud path. This guide covers each realistic route for a late starter and the conditions attached to it. It also flags the deadlines that are easy to miss, including a 2030 cutoff that SAP spelled out in October 2026.

TL;DR

·        Mainstream maintenance for ECC 6.0 with enhancement packages 6 to 8 ends on December 31, 2027. Older enhancement packages lost mainstream maintenance at the end of 2025.

·        SAP extended maintenance runs through 2030 for a 2-point premium, but you have to opt in by the end of 2027.

·        A transition option originally covered 2031 to 2033. On October 13, 2026, SAP said qualifying subscriptions may reach December 31, 2035, subject to added conditions. The 2030 private-edition move remains required.

·        If ECC runs on a database other than SAP HANA, plan any system conversion before the end of 2030. After that, SAP says only new implementations will be possible.

·        Third-party SAP support can buy time, but it won’t move you to S/4HANA on its own.

What the 2027 Deadline Actually Covers

The SAP ECC end of support date applies to mainstream maintenance for SAP ERP 6.0 with enhancement packages 6, 7, and 8. In its 2020 maintenance announcement, SAP set December 31, 2027 as the end of mainstream maintenance for core Business Suite 7 applications, followed by optional extended maintenance until the end of 2030. SAP committed to keeping at least 1 SAP S/4HANA release in maintenance through 2040. Each release has its own maintenance period. The years between those dates are the window SAP expects ECC customers to cross.

Your enhancement package decides which date applies to you. According to SAP’s own timeline post, mainstream maintenance for ERP 6.0 without an enhancement package, or with packages 1 to 5, ended on December 31, 2025. Extended maintenance is offered only for packages 6 to 8. If you’re on an older package today, you’re already outside mainstream maintenance, and your first task is to confirm what support you actually have.

The same dates apply beyond ERP. SAP’s support portal lists the latest 3 enhancement packages of SAP CRM 7.0, SCM 7.0, and SRM 7.0 under the same Business Suite 7 timeline. If those systems feed your ECC processes, the SAP ECC end of support plan has to include them too. Leaving a satellite system on an unsupported release can stall an ERP cutover just as easily as a problem in the core.

The end of mainstream maintenance doesn’t switch your system off. ECC will keep running on January 1, 2028. What changes is the help you get from SAP when something breaks or a tax rule changes. The rest of this guide is about keeping that help in place long enough to finish your move.

Why a Late Start Is Riskier Than It Looks

Starting late is common, but it leaves you very little margin. When The Register covered a Gartner analysis in early 2025, Gartner estimated that about two-thirds of ECC customers had yet to take any action toward S/4HANA. It also expected 4 in 10 of today’s ECC customers to still use ECC in key business areas by 2030. You’re in good company, and that’s part of the problem. Late movers compete for the same consultants and the same project slots.

Projects also tend to run long. A Horváth survey of 200 SAP user companies, reported by CIO.com in 2025, found that projects took 30% longer than planned on average. Only 8% of the companies that finished their S/4HANA migration did so on schedule, and more than 6 in 10 went over budget. Looking back, 46% of respondents said they’d plan for a longer project from the start. If your plan assumes everything runs to schedule, it’s already behind.

Skills are the third constraint. In ASUG’s 2025 research, 35% of respondents said finding employees with the internal skills to manage new technology was a top challenge. A late S/4HANA migration usually pulls your best ECC people onto the project while someone else keeps the old system running. Plan for both jobs early, because the people who know your custom code are the hardest to replace.

Delay also narrows your choices in a way that’s easy to miss. Each quarter you wait before starting cuts into the time a brownfield conversion needs before the 2030 database cutoff covered later in this guide. It also shortens the time to lock in today’s transition option terms, since SAP hasn’t published pricing for sign-ups after 2026. A late response to SAP ECC end of support still leaves room for a sound project. Every month of planning you skip now comes back later as schedule pressure, though, so the first decisions deserve attention this quarter.

Extended Maintenance Through 2030

For most late starters, extended maintenance is the simplest answer to SAP ECC end of support. It runs from January 1, 2028 to December 31, 2030 and costs a premium of 2 percentage points on your existing maintenance basis. SAP describes its scope as similar to mainstream maintenance, so you keep problem fixes and legal changes for those 3 years. It was designed for customers who are in the middle of a longer conversion and need extra time.

The decision has a deadline of its own. SAP’s announcement says customers who haven’t chosen extended maintenance by the end of 2027, and who keep running Business Suite 7, move automatically to customer-specific maintenance. Put this decision on your 2027 calendar now and involve procurement and legal, since it changes your maintenance contract. Leaving it to the last quarter of 2027 gives you no room to negotiate.

You’d be in large company if you take this route. The DSAG’s 2026 investment survey, covered by CIO.com, found that almost half of companies using ECC plan to pay for SAP extended maintenance and finish their S/4HANA migration by the end of 2030. DSAG’s chair said many need that time because of how complex their landscapes are. It’s a sound plan as long as you treat 2030 as a hard stop. Extended maintenance buys 3 years, and a good part of the first one can go to planning and preparation.

Know what extended maintenance won’t give you. SAP’s own training material notes that it doesn’t add new features or enhancement packages. You’re paying to keep a fixed release supported, so any business change you want from ERP should wait for S/4HANA rather than land in ECC. Budget the premium as the price of extra time and keep it out of any ECC improvement plans.

The Private Edition Transition Option: 2033 or 2035

The transition option is SAP’s offer for ECC customers who can’t finish by 2030, and it comes with strict conditions. In SAP’s updated announcement, the original 2031 to 2033 subscription includes continuity services such as legal changes and security patches. SAP added a note on October 13, 2026 saying some subscriptions may run until December 31, 2035, subject to further prerequisites. The added conditions aren’t fully public. Confirm eligibility under SAP Note 3591251 and current terms. Published baseline requirements include:

·        Your systems must move to SAP ERP, private edition on SAP HANA before December 31, 2030.

·        SAP HANA is the only supported database.

·        Each subscribed system has to be at least 2 TB in size.

·        The original offer also requires SAP’s max success plan for 2031 to 2033 at an extra fee. Confirm any requirements and fees for 2034 and 2035 with SAP.

Timing affects the price under the published 2031 to 2033 terms. Customers who committed to SAP ERP, private edition by the end of 2025 can switch to the transition option in 2031 on equal commercial terms. Those who sign in 2026 face a standard 20% uplift when they switch, while SAP hasn’t disclosed the uplift for later sign-ups. SAP hasn’t published 2034 to 2035 pricing. Request it in writing. SAP has also said that the option doesn’t support Java-dependent capabilities, so check every Java-based component before you count on it.

For a late starter, this is a 2-step move. You’d first move ECC into SAP’s private cloud as SAP ERP, private edition, and then complete S/4HANA by 2033 under the original term. A 2035 finish needs SAP’s confirmation of the added requirements. Forrester’s earlier analysis described the original offer as a route for customers with very complex landscapes. If you’re a midsize company with a single modest ECC system, the published 2 TB minimum may rule it out.

If you may qualify, get specific answers before you plan around it. SAP lists covered products in SAP Note 3591251, so check each add-on and industry solution. Request the max success plan fee, 2034 to 2035 charges, and any extra prerequisites in writing. Also ask what happens to systems that miss the 2030 move, because the published offer requires that step. Keep your planned go-live well ahead of the expiry in your own contract.

Customer-Specific Maintenance and Running Unsupported

Customer-specific maintenance is what you get by default, and it’s much thinner than it sounds. You keep paying your annual support fee. In return, as SAPinsider explains, there are no legal changes and no new support packages, new interfaces aren’t supported, and SAP resolves only problems it already knows about. Tax and payroll rules change every year, so a system without legal updates gets riskier with each quarter it runs.

The 2030 Database and Java Cutoff

SAP added an important detail in October 2026. In SAP’s beyond-2030 guidance, CTO Philipp Herzig wrote that SAP’s reselling and support agreements for third-party databases and Java end with extended maintenance on December 31, 2030. After that, SAP won’t provide database-specific support for those environments, including kernel patches and kernel security patches. A system conversion from Business Suite 7 on a third-party database to S/4HANA will only be available before that date. After it, SAP says only new implementations will be possible.

That turns 2030 into a hard date for many ECC customers. If your ECC runs on a database other than SAP HANA, you need to finish a conversion by the end of 2030 or accept a full new implementation afterward. SAP also notes that moving ECC to HANA doesn’t extend mainstream or extended maintenance. You’d still land in customer-specific maintenance, which SAP doesn’t recommend as a long-term path.

What Running Unsupported Really Means

Some companies consider dropping maintenance altogether and running ECC as it stands. That cuts cost, but you lose SAP’s fixes and security patches and carry the full risk of every regulatory change yourself. It can make sense for a system you’ll retire within months. For the core ERP that runs your finance and payroll, it’s a hard position to defend to auditors and to your board. Auditors will ask how a critical system gets security fixes, and “it doesn’t” is a difficult answer to give. If you’re considering this route for any system, write down who’ll fix what when something breaks, and get that plan approved before the support ends.

Third-Party SAP Support as a Bridge

Third-party SAP support replaces SAP’s maintenance with a contract from an independent provider. These firms typically fix problems in your existing ECC release and deliver tax and regulatory updates. Many also support custom code that SAP’s own support doesn’t cover. You keep running the release you already have. For a company facing SAP ECC end of support with a project that’s barely started, the appeal is stability at a lower annual cost than SAP maintenance while the migration runs.

Analysts treat it as a real option. A June 2026 Gartner research note argues that third-party software support can play a strategic role for ECC and S/4HANA customers, whatever their modernization timeline. Gartner’s earlier analysis also called it a viable choice for organizations keeping ECC past the mainstream deadline and after 2030. That matters for the database cutoff above, since it gives companies a support path if their project runs past 2030.

Check the terms carefully before you switch. Third-party SAP support won’t move you to S/4HANA, and it doesn’t give you new SAP software. Ask SAP in writing what it would charge to return to SAP maintenance later. Then confirm how your future S/4HANA licensing or RISE with SAP offer would treat a gap in maintenance, because that answer can change the business case.

Timing matters here too. You may be negotiating a RISE with SAP contract during the same window in which you’d leave SAP maintenance. Leaving can affect the credits and terms SAP puts on the table for that deal. Model both paths, with and without a third-party provider, before you give notice on your current contract.

Choosing a Target: RISE, GROW, or On-Premise S/4HANA

Every bridge option ends in the same place: you still need a target system. SAP offers 3 main ways to run S/4HANA, and the choice shapes how much of your ECC setup survives the S/4HANA migration. Pick the target before you pick a bridge, because the target decides which bridges make sense.

On the private cloud side, RISE with SAP bundles the private cloud edition of S/4HANA with SAP-managed infrastructure and services. It supports a conversion from ECC, so you can keep custom code and history if you choose. GROW with SAP is aimed at midsize companies and centers on the public cloud edition, which runs SAP’s standard processes and leaves little room for custom code. On-premise S/4HANA keeps hosting and upgrade timing in your hands.

SAP is steering customers toward its cloud editions, and its newest support offers, including the transition option, assume a RISE with SAP path. On-premise S/4HANA remains a valid choice if your business case supports it. SAP’s 2040 commitment means at least 1 S/4HANA release will remain in maintenance through that year; it doesn’t extend every individual release to 2040.

A few questions usually settle the choice. How much of your custom code supports processes that set you apart from competitors? How many legal entities and countries does ECC serve today? Does your IT team want to manage infrastructure and upgrade timing, or hand both to SAP? How soon does the new system need to be live? The answers point toward private cloud, public cloud, or on-premise more reliably than any vendor pitch. Whichever you pick, get the decision signed off early. Changing targets halfway through a late project is one of the most expensive mistakes you can make.

Brownfield, Greenfield, or Selective Data Transition

How you move matters as much as where you move, and late starters feel the effect of this choice more than anyone. There are 3 broad approaches to an S/4HANA migration, and a late starter should pick the one that fits the time left, along with the target chosen above.

Brownfield System Conversion

A brownfield conversion turns your existing ECC system into S/4HANA and keeps your configuration and custom code. Your transaction history comes along too. It can take less time when the existing setup is in good condition and process changes are limited. Heavy custom code, poor data quality, and complex integrations can make conversion slower than expected. You may also carry technical debt forward. If your ECC runs on a third-party database, this approach is directly affected by SAP’s 2030 cutoff.

Greenfield New Implementation

A greenfield project builds S/4HANA from scratch and moves only the data you need, such as open items and master data. It gives you a chance to adopt standard processes. A broad process redesign can make it lengthy and demand significant business involvement, but a focused new implementation may be quicker than converting a heavily customized ECC system. Master data quality becomes a project of its own, since you’re choosing what to bring across rather than copying everything. Compare timelines using custom code, data quality, process scope, and system complexity before choosing a support bridge.

Selective Data Transition

Selective data transition sits between the other 2. You build a new system from a copy or template and choose which data comes across, for example by company code or by years of history. It suits companies that want to clean up some areas while keeping others intact. In the Horváth study, 31% of respondents chose a selective approach. It needs specialist tools and experienced partners, so confirm availability before you commit to it.

How the Options Compare Side by Side

Most late starters will answer SAP ECC end of support by pairing a target platform with at least 1 bridge. The table below compares the support routes that keep ECC covered while you move.

One workable plan pairs a cloud or on-premise target with extended maintenance and holds third-party support in reserve in case the project slips past 2030. Larger companies with complex landscapes may examine the transition option instead. The term may extend from 2033 to 2035 for eligible subscriptions. Whatever you choose, write down the approval date and contracted end date for each route, because the general announcement can’t establish your own eligibility.

Costs and Contract Terms to Check

The bridge costs are easier to estimate than the project itself. SAP extended maintenance adds 2 percentage points to your maintenance basis each year from 2028 through 2030, so an Enterprise Support rate of 22% would rise to 24%. The transition option is priced as a subscription at an uplift over SAP ERP, private edition pricing, with the max success plan fee added on top. For 2026 sign-ups, the published uplift for switching in 2031 is 20%; SAP hasn’t published the figure for 2027 or later. The possible 2034 to 2035 subscription period may carry further charges, so request a separate price and eligibility confirmation.

Project costs are harder to pin down, and they depend heavily on choices made earlier. A HANA system has to be sized and paid for, whether you host it or SAP does. Java-based components may need a replacement plan before 2030 under SAP’s latest guidance. Custom code adaptation is another big variable, which is why the readiness check results matter so much for the budget. Treat any SAP ECC end of support estimate made before those results arrive as a rough range rather than a number to commit to.

Before you sign anything, check these contract terms:

·        The opt-in date for SAP extended maintenance and the products it covers in your landscape

·        Whether your cloud offer credits your existing licenses and maintenance spend

·        Notice periods for ending SAP maintenance if you plan to switch to a third-party provider

·        What SAP would charge to reinstate maintenance after a gap

·        Who carries the cost of delays in your implementation partner’s contract

Internal costs are the ones teams forget. You’ll need people to backfill ECC support while your experts work on the project. You’ll also need a contingency line that reflects how often these projects run long. Build both into the first budget, since asking for more money halfway through is harder than asking once.

Keeping ECC Stable While You Migrate

Your ECC system has to keep running well until the day you switch it off, which may be years after SAP ECC end of support. Freeze nonessential custom development so the target doesn’t move under you. Every new ABAP object you add now is 1 more object to test or rebuild later. Route new requests through a simple review that asks whether the change can wait for S/4HANA.

Keep patching on the normal cycle. Until your maintenance model changes, apply SAP security notes as they’re released each month. List the legal changes you’ll need from 2028 to 2030, such as tax rate updates, and confirm that your chosen support model covers them. That’s true whether you pick extended maintenance or third-party support.

Protect what your team knows. Document custom code and interfaces while the people who built them are still with you. Archive data you no longer need, because a smaller database means less data to convert and a smaller HANA system to size and pay for. These steps cost little now and shorten the S/4HANA migration later. They also make ECC easier to support under any of the bridge options, because a smaller, better-documented system is cheaper for anyone to maintain.

A 90-Day Starting Plan for Late Movers

You can’t finish a migration in 90 days, but you can make the decisions that set its direction well before SAP ECC end of support arrives. Use this sequence to get from no plan to a funded plan.

1.      Confirm your release and database. Check the enhancement package and database for every production ECC system. These 2 facts decide which dates apply to you.

2.      Run a readiness check. Use SAP’s Readiness Check tool, offered at no extra charge with an SAP support agreement, to see which simplification items apply and how much custom code needs work.

3.      Pick a target and an approach. Decide between private cloud, public cloud, and on-premise, and then choose brownfield, greenfield, or a selective transition.

4.      Choose your bridge. Decide whether you need extended maintenance, the transition option, or third-party SAP support, and mark each opt-in deadline.

5.      Secure your people. Line up an implementation partner and name internal leads before partner capacity tightens further.

6.      Test the plan against 2030. Work backward from December 31, 2030 and check whether your plan finishes with time to spare.

7.      Take it to the board. Show the cost of each bridge next to the cost of the project so the decision gets made at the right level.

By day 90 you should have a target and an approach, along with a budget range the board has approved. You should also know which support contract you’ll be on in January 2028. If any of those are still open, the plan isn’t ready, and the calendar keeps moving either way.

Final Thoughts on a Late SAP ECC Move

SAP ECC end of support leaves late starters with fewer options than early movers had, but the remaining routes are real. Extended maintenance runs through 2030. The private-edition transition option originally ran through 2033, and SAP’s October 2026 update permits some subscriptions through December 31, 2035, with added conditions. Third-party SAP support may cover a slip, though it can’t replace the project. The deadlines that matter most remain the extended-maintenance decision in 2027 and the database conversion cutoff in 2030. Decide your target first, then choose a support bridge based on verified eligibility and enough time to finish.

Frequently Asked Questions

When Does SAP ECC End of Support Happen?

Mainstream maintenance for SAP ERP 6.0 with enhancement packages 6 to 8 ends on December 31, 2027. Optional extended maintenance runs until December 31, 2030. Releases on enhancement package 5 or lower lost mainstream maintenance at the end of 2025, so check your release before planning anything else.

Will ECC Stop Working After 2027?

No. ECC keeps running after SAP ECC end of support, and your data and processes stay where they are. What changes is the level of help SAP provides. Without extended maintenance, you move to customer-specific maintenance, which has no legal changes and no new support packages.

What Is SAP Extended Maintenance?

SAP extended maintenance is a paid option that continues support for ECC with enhancement packages 6 to 8 from 2028 through 2030. SAP describes its scope as similar to mainstream maintenance. It’s meant for customers who need more time to finish their move to S/4HANA.

How Much Does SAP Extended Maintenance Cost?

It adds a premium of 2 percentage points to your existing maintenance basis. For example, an Enterprise Support rate of 22% would become 24%. The premium applies each year from 2028 through 2030.

What Happens If I Don’t Opt In to Extended Maintenance by 2027?

If you haven’t chosen extended maintenance by the end of 2027 and you keep running ECC, SAP moves you automatically to customer-specific maintenance. That model offers far less support, so make the decision well before the deadline.

Can I Keep Running ECC After 2030?

Yes, but SAP’s standard extended maintenance ends in 2030. Customer-specific maintenance continues with limits, while qualifying customers may use the SAP ERP, private edition transition option. Its original term ends in 2033; SAP now says eligible subscriptions may run until December 31, 2035 with extra prerequisites. Systems on third-party databases face separate support and conversion limits after 2030.

Who Qualifies for the Transition Option Through 2035?

The original offer targets large, complex customers. Baseline rules include a move to SAP ERP, private edition on HANA by 2030, a 2 TB system minimum, and the max success plan for 2031 to 2033. SAP’s October 2026 notice says subscriptions may run through 2035, but further prerequisites apply. Ask SAP to confirm your specific eligibility and fees.

Does My Database Matter for the 2030 Deadline?

Yes. SAP says a system conversion from ECC on a third-party database to S/4HANA will only be available until the end of 2030. After that, only new implementations will be possible, so database choice can decide your migration approach.

What Is Customer-Specific Maintenance?

It’s the default support level after mainstream or extended maintenance ends. You keep paying your support fee, but there are no legal changes or new support packages. SAP resolves only problems it already knows about.

Is Third-Party SAP Support a Safe Option?

It can be a sound bridge for keeping ECC stable while you migrate, and analysts such as Gartner see a real role for it. Check what SAP would charge to return later and how a gap would affect your S/4HANA licensing. Also confirm the provider can deliver the tax and legal updates your countries require.

How Long Does an S/4HANA Migration Take?

An S/4HANA migration’s length depends on your landscape and approach, but projects often run longer than planned. A Horváth study of 200 SAP users found an average overrun of 30%, and only 8% of finished projects met their schedule.

Should a Late Starter Choose Brownfield or Greenfield?

Neither approach is always faster. Brownfield may save time when configuration and custom code are manageable. Heavy customization and poor data can slow it down. Greenfield takes more business design work but may be quicker for a focused rebuild. Compare the actual scope and integration needs before deciding.

Do I Have to Use RISE With SAP?

No. On-premise S/4HANA remains an option. SAP’s commitment through 2040 means it will maintain at least 1 S/4HANA release, although each release has its own maintenance period. The SAP ERP, private edition transition option follows SAP’s RISE with SAP path. Its original 2033 term may be extended to 2035 only for qualifying subscriptions with extra prerequisites.

What If My ECC System Is on Enhancement Package 5 or Lower?

Mainstream maintenance for those releases ended on December 31, 2025, and extended maintenance isn’t offered for them. Confirm your current support status with SAP and factor that gap into your plan right away. Treat it as a reason to move faster, since your system already gets less help than an EHP 6 to 8 system does.

What Should I Do First If I Haven’t Started?

Confirm your enhancement package and database, then run SAP Readiness Check on your production system. Those results tell you which SAP ECC end of support deadlines apply and how much work a conversion would take. That gives you a factual basis for every later decision, from the target platform to the bridge you choose.