SAP ECC leaves mainstream maintenance on 31 December 2027, and every module you run moves to S/4HANA with people who know both sides. We staff that move module by module: an 18-profile framework won on a public tender at PGE Systemy, German-speaking teams in DACH automotive, first CVs in 48 hours.
SAP Business Suite 7 leaves mainstream maintenance on 31 December 2027. Extended maintenance runs to 31 December 2030 at two percentage points more on the maintenance base. Here is what that means for each module you run, and who the move needs.
SAP ERP, private edition, transition option: a paid subscription for business continuity from 2031 to 2033, and since SAP's update of 13 October 2026 up to 31 December 2035 with further prerequisites. It applies to systems moved to ERP private edition on SAP HANA before 31 December 2030, at least 2 TB, with the max success plan. It is not a maintenance extension.
From 2031 the system runs on customer-specific maintenance: it keeps working, but new legal changes and support packages stop arriving.
In the DSAG Investment Report 2026 (198 member companies), 54% still run ECC or older Business Suite, down from 68% in 2024. Of those still investing in ECC, 37% plan to switch by the end of 2027 and almost half by the end of 2030. Skills shortages and parallel projects are delaying schedules.
Sources: SAP, transition option (update 13 Oct 2026) · SAPinsider, 28 Sep 2026 · SAP NetWeaver maintenance strategy · DSAG Investment Report 2026 · LeverX on SAP HCM, 6 Oct 2026. Checked 6 November 2026.
Every path to S/4HANA lands on the same work: HANA, clean custom code, new integration and migrated data. Each part needs its own specialists, often at the same time.
A system conversion keeps your configuration and history; a new implementation starts clean; a selective data transition moves only what you choose. The path decides how many functional, ABAP and data people you need, and when.
S/4HANA runs only on SAP HANA. Basis teams convert with the Software Update Manager and its database migration option, then tune the system for HANA.
SAP grades custom code on four clean-core levels, A to D. Level A is ABAP Cloud, SAP's model for every new extension, and the ABAP test cockpit checks each object against the levels.
Years of Z-programs, user exits and RICEFW objects have to be checked, rewritten or retired before go-live. That is ABAP work, module by module.
PI/PO 7.5 leaves mainstream maintenance at the end of 2027 too. Interfaces move to SAP Integration Suite on BTP, one by one, and each one is tested again.
Master and transaction data move through the S/4HANA Migration Cockpit, with a reconciliation after every load.
Joule for developers explains legacy ABAP, writes unit tests and suggests fixes for S/4HANA findings in the test cockpit. It speeds the work up; a developer who knows the old code still signs it off.
Since 2023 S/4HANA ships a release every two years, each with seven years of maintenance, and SAP commits to S/4HANA until at least 2040. The move lands on a platform with its own upgrade rhythm.
Sources: SAP Community, ABAP platform in S/4HANA 2025 · Eursap on S/4HANA release maintenance · Gambit on IS-U and S/4HANA Utilities.
Every SAP buyer knows it: a generic "SAP consultant" is a red flag, and a Billing architect is not an HCM consultant. An S/4HANA move multiplies that: each module needs someone who knows the old system and the new one. So we don't sell SAP — we sell the module, with the delivery history to match.
Briefs are matched at module level — IS-U Billing is not CRM, and neither is FI-CA. The shortlist reflects that.
IS-U, CRM & Billing for utilities — the module family where Polish energy runs, and where our framework lives.
SAP consultants with verified German for DACH programmes — delivered as teams, not lone contractors. See the 15-consultant Mercedes-Benz case →
The exact profile set under our PGE Systemy framework agreement, grouped the way the tender grouped them. Each maps to its S/4HANA successor: IS-U to S/4HANA Utilities, ECC to S/4HANA, HCM to H4S4 or SuccessFactors. The tender in numbers is in the PGE Systemy case.
Automotive modules for DACH teams — JIT/JIS, LO-VC, SD-EDI, VMS, DBM, TM — are on the automotive page.
Runs an active framework agreement across all 18 profiles above for one of Poland's largest energy groups — supplier selected in a competitive public tender.
Hires Data Scientists and AI Architects through NDS — body leasing and permanent — as the energy sector's data programmes grow alongside its SAP core.
German-speaking, multi-module SAP teams delivered for Mercedes-Benz through our partner abat Plus — automotive-specific modules included.
The specialists an S/4HANA move needs are the ones every integrator is calling. Five answers at the brief decide whether the right one stays in your process.
We confirm the system and the target first. An ABAP developer for ECC maintenance is a different search from one rewriting custom code for S/4HANA.
Module, RICEFW objects, Fiori/UI5 or not. A precise scope keeps the technical interview from rejecting a good candidate for the wrong reason.
Remote work opens the search to the whole of Poland. We confirm what your project allows before the first approach.
Most SAP specialists work on contract and weigh how long the work runs. We state the horizon and the extension options in the first message.
SAP specialists hear from several firms at once. We book the next interview within days of the first, so the person you want is still available.
What every SAP brief gets from us, whichever module it names.
Name the module, the system (ECC or S/4HANA) and the seniority. First anonymized profiles within 48 hours — matched at module level, because in SAP nothing else counts.
Get SAP CVs in 48hMainstream maintenance for SAP ERP 6.0 and the other Business Suite 7 applications ends on 31 December 2027. Extended maintenance runs to 31 December 2030 at two percentage points more on the maintenance base. After that, SAP offers a paid transition option for large systems already moved to ERP private edition on HANA, and other systems fall back to customer-specific maintenance.
IS-U leaves mainstream maintenance with ECC at the end of 2027, with extended maintenance to the end of 2030. Its successor is S/4HANA Utilities, where SAP adds its new utilities functions. We staff the move with IS-U and S/4HANA Utilities billing, FI-CA, device and meter-data specialists.
SAP Integration Suite on the Business Technology Platform. PI/PO 7.5 leaves mainstream maintenance at the end of 2027, with extended maintenance to 2030, so interfaces have to move in the same window as the ERP. We supply integration developers who know both.
HCM on ECC follows the ECC dates: mainstream to the end of 2027, extended to 2030. The successors are SAP HCM for S/4HANA (H4S4) on-premise, SuccessFactors in the cloud, or a mix of the two. We staff payroll, time, PA/OM and ABAP HCM specialists for either route.
Yes, module by module, inside your team or your integrator's: functional consultants for each module, ABAP developers for custom-code remediation, Basis for the HANA conversion, integration and data-migration specialists, and a delivery manager. First CVs within 48 hours.
Yes. Our German-speaking team for Mercedes-Benz was placed through our partner abat Plus: 15 SAP consultants in 8 weeks, working as one unit inside the partner's programme. The same model works for any integrator running a utility or manufacturing move. Read the Mercedes-Benz case.
The 18-profile set under our framework: CRM & Billing, IS-U (utilities billing), FI-CA, ECC finance and logistics, asset management, ABAP development, Basis, and the HCM family (PY, PA/OM, PT, ESS/MSS, ABAP HCM). Automotive-specific module teams are delivered through our partner abat Plus. Other modules — ask; the answer is a market read, not a yes-to-everything.
Because that's where the delivery is: an active framework with PGE Systemy centred on IS-U and CRM & Billing — the module family Polish utilities actually run on — plus Tauron hiring data and AI profiles through us as energy's digital programmes expand. Both are written up: the PGE Systemy case and the Tauron case.
Yes — SAP delivery for the DACH market runs through German-speaking consultants, delivered as coherent teams rather than single contractors, including via our automotive partner abat Plus. They work remotely from Poland, in your time zone.
First CVs within 48 hours for framework-covered modules. Genuinely rare combinations — senior IS-U architects, ABAP HCM — get an honest market read at the brief, with a committed date instead of a guess.
Updated 6 November 2026
Put a slot in a calendar, or send the brief and we will come back to you. Either way you are talking to a partner, not a queue.
Thirty minutes, no deck. Pick the one who handles your side — he takes the call himself.
Roles, platform, headcount, timeline. A link to a brief is even better.
