Ryz Labs/Migrations/SAP ECC end of mainstream maintenance
Migrations

SAP ECC End of Mainstream Maintenance: The 2027 Engineering Plan

SAP ERP 6.0 leaves mainstream maintenance on December 31, 2027. Here are SAP's options after that, and the engineering work that sits around any ERP move.

Short answer: SAP mainstream maintenance for SAP ERP 6.0 (ECC) ends on December 31, 2027. SAP offers optional extended maintenance to December 31, 2030 at a two-percentage-point premium, then customer-specific maintenance; plan the move before 2028.

VersionEnd of lifeStatus on November 21, 2026
SAP ECC 6.0December 31, 2027Supported

SAP has set December 31, 2027 as the end of mainstream maintenance for the core applications of SAP Business Suite 7, which include SAP ERP 6.0 (ECC) on "the latest three enhancement packages," according to SAP's maintenance strategy page. Optional extended maintenance then runs from January 1, 2028 to December 31, 2030 at a premium, and SAP's recommended direction is SAP Cloud ERP through RISE with SAP. Whichever option you pick, the deadline forces the same engineering work: get your data out cleanly, rebuild the interfaces, move custom Z-program logic out of the ERP core, and automate the cutover tests.

Key dates

PhaseDatesWhat SAP providesStatus on November 21, 2026
Mainstream maintenanceEnds December 31, 2027Standard maintenance for SAP ERP 6.0, latest three enhancement packagesIn effect
Extended maintenance (optional)January 1, 2028 to December 31, 2030Continued maintenance at a premium of two percentage points on the maintenance basisNot yet started; opt-in
Customer-specific maintenanceFrom 2028 without extended maintenance, from 2031 with it; no end date namedProblem solving for known issuesNot yet started
SAP ERP, private edition, transition option2031 to 2033Time-bound cloud subscription; SAP says it "is not a maintenance prolongation"Requires SAP ERP, private edition on SAP HANA before end of 2030

Dates from the official calendar, checked November 21, 2026: SAP's support portal, the 2020 SAP announcement that set the 2027 and 2030 dates, and an October 2026 SAP update confirming they are unchanged. SAP's public page scopes the 2027 date by enhancement package as "the latest three"; it does not list package numbers, and neither do we.

What end of mainstream maintenance means for your systems

Nothing switches off on January 1, 2028. Your ECC system still posts documents, runs the batch jobs you already scheduled, and answers the RFC calls your other systems make. What changes is the support terms around it, and the planning runway that remains.

Find your exposure

The ECC instance itself is not hard to find. The work is in everything wired to it. Before choosing an option, list the things that will have to move, be rebuilt or be retested, whichever route you take.

Your options after December 31, 2027

SAP publishes several routes. They are not mutually exclusive, and many organizations combine them: extended maintenance to buy time while a cloud ERP program runs, for example. Here is what each one is, in SAP's terms.

Optional extended maintenance to 2030

SAP's support portal says extended maintenance is "available for three years from beginning of 2028 until end of 2030" and "comes with a premium of two percent points on the maintenance basis for all support offerings." It keeps you on SAP ERP 6.0 under maintenance while you prepare a move. It does not change what you have to move.

Customer-specific maintenance

This applies to customers who do not opt into extended maintenance, and to everyone once extended maintenance ends. The 2020 announcement describes it as problem solving for known issues at unchanged fees. SAP's October 2026 update says customers should not treat it as a sustainable long-term model, particularly for systems on third-party databases or Java.

SAP Cloud ERP through RISE with SAP

This is SAP's recommended direction. The October 2026 update says customers "should use the time available to move toward SAP Cloud ERP and the SAP Autonomous Suite," and SAP's 2025 update calls the RISE with SAP journey "the best way to move to the cloud." The functional design of the target system belongs to your SAP team and SAP partner. The engineering around it, covered below, belongs to whoever owns your data and integrations.

SAP ERP, private edition, transition option

For 2031 to 2033, SAP offers a time-bound cloud subscription aimed at its largest and most complex Business Suite 7 customers. SAP is explicit that "this is not a maintenance prolongation of SAP ERP." To qualify, systems must be on SAP ERP, private edition on SAP HANA before the end of 2030, and SAP says the option does not support Java-dependent capabilities. SAP states the pricing as an uplift on the private edition pricing valid at the end of 2030.

Third-party databases and Java

If ECC runs on a database other than SAP HANA, read the October 2026 update closely. SAP's reselling and support agreements for third-party databases and Java end at the close of 2030, and so does the tooling for a system conversion from such systems to SAP S/4HANA or SAP Cloud ERP. After that, SAP says only new implementations are supported. That makes the database under your ECC system one of the first facts to pin down.

Clean core and side-by-side extensions

SAP describes clean core as a concept for keeping core ERP systems "transparent, flexible" by separating what is standard from what is specific to your business, and it has written about a side-by-side development approach on SAP Business Technology Platform. The engineering idea is older than the term: keep vendor code standard, and put your differentiating logic in services you own, connected through stable APIs. That is where years of Z-programs usually need to go, whichever SAP platform hosts the core.

The engineering plan

This plan covers the software engineering around an ERP move, not the SAP functional configuration. It assumes your SAP team and partner own process design and system setup, and it gives the data, integration and custom-code tracks a clear owner on your side. Ryz is not an SAP partner and does not sell SAP licenses.

Inventory and baseline

Turn the exposure list into a register: every custom object, interface and feed, with its owner, frequency, data volume and a decision (retire, rebuild outside the core, or keep). Capture baselines you will compare against later: record counts and control totals per company code and period, interface message volumes, and run times for critical batch jobs. Retiring unused reports early is the cheapest win in the program.

Data extraction and reconciliation

Write extraction jobs that pull master data and open items into a staging area you control, with every run versioned and repeatable. Build reconciliation as code from day one: row counts, sums of amounts by ledger and period, open-item balances by customer and vendor, and field-level checks on a sample. Every mock load should produce a reconciliation report a finance lead can sign. Data cleansing (duplicates, inactive vendors, orphaned records) happens here, where it is cheap, not during cutover.

Integration and API layer

Point-to-point connections into ECC are what make a move risky, because every consumer has to change on the same night. Put an integration layer between SAP and the rest of your estate: owned services that expose stable APIs to your other systems and translate to whatever the ERP speaks underneath. Consumers move to the new interface while ECC is still live; at cutover only the adapter behind it changes. Automated tests on each interface catch drift before users do.

Rebuild custom logic outside the core

For each Z-program and custom report you keep, extract the business rule, write it down as test cases using real historical inputs and outputs, then rebuild it as an owned service or app beside the ERP rather than inside it. Run old and new side by side on the same inputs and diff the results until they match. The same pattern drives our COBOL to Python runbook: capture behavior first, then rewrite, then prove equivalence.

Test automation and cutover rehearsal

Automate end-to-end tests for the flows that make money and close the books: order to cash, procure to pay, period close, and every interface you rebuilt. Rehearse the cutover more than once, with the data migration scripts, the reconciliation reports and the rollback steps run exactly as they will be on the night. Each rehearsal should end with measured timings and a shorter list of manual steps.

Cutover, hypercare and cleanup

Freeze changes, run the final extraction and load, reconcile, switch the integration layer to the new backend, and keep the old system read-only for lookups. During hypercare, watch interface error queues and reconciliation deltas daily. Afterward, archive the old landscape according to your retention rules, remove temporary adapters, and update runbooks.

PhaseGoalKey techniqueExit criteria
Inventory and baselineEvery custom object, interface and feed known and ownedRegister with retire, rebuild or keep decisions; control totalsRegister signed off by IT and finance leads
Data extraction and reconciliationRepeatable, provable data loadsVersioned extraction jobs, reconciliation as codeMock loads reconcile to zero unexplained differences
Integration and API layerConsumers decoupled from ECCOwned APIs with adapters and interface testsEvery consumer on the new interface while ECC is live
Custom logic rebuildBusiness rules owned outside the ERP coreBehavior captured as tests, parallel runs with diffsOld and new outputs match on historical inputs
Test automation and rehearsalPredictable cutoverAutomated end-to-end suites, timed dress rehearsalsRehearsal meets the blackout window with rollback tested
Cutover and cleanupNew backend live, old landscape retiredAdapter switch, read-only legacy, daily reconciliationHypercare closed, temporary adapters removed

Risk matrix

RiskLikelihoodImpactMitigationEarly warning
Undocumented business rules live only in Z-programsHighHighCapture behavior as tests from historical runs before any rewriteParallel-run diffs no one can explain
Migrated balances do not reconcileMediumHighReconciliation as code on every mock load, signed by financeUnexplained differences that persist across mock loads
A forgotten interface breaks at cutoverMediumHighInterface register, traffic monitoring, consumers moved to owned APIs earlyUnregistered connections in network or middleware logs
Third-party database closes conversion optionsMediumHighConfirm the database early and plan against SAP's end-2030 cutoffDatabase question still open after the inventory phase
Reporting feeds go stale after table changesHighMediumRebuild extracts against the integration layer, not raw tablesDashboard owners missing from the register
Cutover overruns the blackout windowMediumHighTimed rehearsals, scripted loads, fewer manual steps each roundRehearsal timings not shrinking
Engineering tracks lag the functional programMediumMediumSeparate owners for data, integration and custom-code tracks with shared milestonesIntegration work scheduled after functional design freeze

Typical team shape

To be clear about scope: Ryz does not do SAP functional configuration, does not resell SAP, and is not an SAP partner. Your SAP partner or in-house SAP team designs and configures the target system. Ryz engineers take the software engineering tracks next to that work: data extraction and reconciliation, the integration and API layer, rebuilding custom reports and Z-program logic as owned services, data migration scripts, and cutover test automation.

A common shape is a tech lead who owns the interface register and the cutover plan, a data engineer or two for extraction, staging and reconciliation, a backend engineer for the APIs and rebuilt services (see our API development work), and a QA automation engineer for end-to-end and regression suites (see test automation). Many teams begin with a pod of 3 to 5 senior engineers (a tech lead plus engineers), and a full pod is about seven.

If the board is weighing whether to rebuild custom logic as owned software or keep paying for it in a packaged product, the SaaS renewal vs custom TCO calculator compares the two over several years and exports a build-vs-buy memo for the board. Ryz engineers work on your team, reporting to your leads. Ryz engineers on your team start from $7,000 per month (our published range is $7,000–$15,000 per engineer per month, mostly mid-level to senior), quoted per team. Once you say go, engineers can typically start in under two weeks. Tell us which track is short of people and scope your team.

Related

FAQ

Is SAP ECC still safe to run after December 31, 2027?

The system keeps working, and SAP offers optional extended maintenance through December 31, 2030 for a premium. Without it, or after it ends, you move to customer-specific maintenance, which SAP describes as problem solving for known issues and does not regard as a sustainable long-term model. Treat 2028 to 2030 as runway for a planned move, not a resting point.

Which target should we plan for?

SAP's recommended direction is SAP Cloud ERP through RISE with SAP, and SAP says customers should plan to complete that move by the end of 2030. The largest customers can also look at the 2031 to 2033 transition option, which SAP says is a cloud subscription and not a maintenance extension. The functional choice is yours and your SAP partner's; the data, integration and custom-code work is needed on every route.

How long does the move take?

It depends on the number of custom programs you keep, how many interfaces connect directly to ECC, data volume and quality, whether the system runs on SAP HANA or a third-party database, the number of company codes and countries, and how many cutover rehearsals you need before the timings are predictable. A thorough inventory is the only honest way to size it.

Can we pay for extended maintenance?

Yes. SAP offers optional extended maintenance from January 1, 2028 to December 31, 2030 at a premium of two percentage points on the maintenance basis for all support offerings. Confirm the exact terms for your agreement with SAP before you budget it.

What does it cost to bring in engineers?

Multiply the number of engineers by the months you need them, then by a monthly rate between $7,000 and $15,000 per engineer depending on seniority. We quote the team as a whole, and you see the plan and the named people before anyone starts.

Questions we didn't answer? Email info@ryzlabs.com.

Thanks — your message has been sent. We’ll get back to you soon.

Something went wrong while sending your message. Please try again or email info@ryzlabs.com.

Explore Ryz Labs

Software development servicesAI development companyIndustriesStaff augmentationAI pod teamsNearshore software developmentHire engineers by roleEngineer ratesGuidesBuyer guidesCase studiesHow we vet engineers

Ryz Labs

Senior engineers on your team. AI pod teams that ship.

Tell us what you're building. You get a scoped plan, a price and the names of the people who would do the work.

  • Only the top 1% of tens of thousands interviewed make it
  • On US business hours, including New York hours
  • Trusted by Fortune 500 engineering teams

Tell us who you need

A Ryz partner replies with a scoped team plan.

Start a conversation →

Prefer to talk? Book a 15-min call →