SAP S/4HANA migration

SAP ECC to S/4HANA migration, planned and assured independently

SAP's mainstream maintenance for ECC ends in December 2027. We help you choose between conversion, new implementation and selective data transition, weigh RISE with SAP against on premise, select an S/4HANA migration partner with no conflict of interest, and hold the programme to its promises through go live.

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
22m+assets in the National Grid separation

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

Where SAP's maintenance dates stand in November 2026

SAP's maintenance page is unambiguous. Mainstream maintenance for the core applications of SAP Business Suite 7, which covers SAP ERP 6.0 on its latest three enhancement packages, runs until the end of 2027. Optional extended maintenance is available for three years, from the beginning of 2028 to the end of 2030, at a premium of two percentage points on the maintenance basis. After that, customers fall into customer specific maintenance. At the other end of the timeline, SAP has committed that at least one S/4HANA release will be in maintenance until the end of 2040, with a new release every two years since S/4HANA 2023 and seven years of mainstream maintenance for each.

The complication is the SAP ERP, private edition, transition option, which SAP introduced for its largest and most complex customers. The conditions are specific. The system must be running on SAP ERP, private edition on SAP HANA before 31 December 2030, it must be at least 2 TB, and the option is only available with SAP's max success plan. It was designed to provide business continuity from 2031 to 2033, and SAP's update of 13 October 2026 states that subscriptions may now run until 31 December 2035, subject to further prerequisites. Price depends on when you committed: customers who subscribed by the end of 2025 move across without uplift, those signing in 2026 carry a standard 20 per cent uplift when they switch in 2031, and for 2027 onwards the uplift has not been disclosed.

Our reading is that the option is a managed way to buy time inside a RISE contract, not a way to avoid the move. For most UK organisations the question is no longer whether to run an SAP ECC to S/4HANA migration but which path, which commercial model and which partner. The alternatives, including leaving SAP, are set out in our guide to the SAP ECC 2027 options.

Greenfield, brownfield or selective data transition

SAP describes three transition paths, and the labels matter less than the decision behind them.

  • New implementation (greenfield). A brand new system. SAP provisions a fresh instance and activates its Best Practices content, and legacy data is loaded through the SAP S/4HANA Migration Cockpit. You get a clean process design and a clean data set, at the price of redesigning everything and carrying over only the history you choose to load.
  • System conversion (brownfield). A guided technical 1:1 conversion of the existing ECC system using the Software Update Manager, whose Database Migration Option combines the database migration, the software update and the data conversion into a single procedure. Your configuration, custom code and full history come with you, including the parts you wish would not.
  • Selective data transition. A tool based approach to selectively migrate and transform configuration, master data and transactions. It suits groups consolidating several instances, and anyone who wants a redesign in some areas while keeping years of history in others.

The choice turns on a handful of facts we gather early: the volume and usage of custom code, the quality of master data, the appetite for process change, the number of instances and company codes, the downtime the business can tolerate, and how much history finance and audit genuinely need. A conversion carries a decade of workarounds forward over a weekend; a new implementation asks the business to take every design decision again. If an existing system is heading for SAP S/4HANA Cloud Private Edition, SAP recommends a one step conversion rather than converting first and moving later, which doubles the projects, the downtime and the cost.

Whichever path you take, data sets the timeline. Our data migration consultancy and the article ERP data migration: what goes wrong explain why.

RISE with SAP or on premise, and a business case that stands up

RISE with SAP is a subscription that bundles SAP S/4HANA Cloud Private Edition with infrastructure from a hyperscaler (Microsoft Azure, Amazon Web Services, Google Cloud or Alibaba Cloud), technical operations and SAP Business Technology Platform credits under one contract with SAP. Private edition is single tenant, carries the same functional scope as on premise S/4HANA, allows changes to SAP source code, and lets you agree upgrade timing with SAP. The public edition is multi tenant, finance led in scope, extended only through Fiori apps and BTP, and upgraded on SAP's timetable. On premise means you keep perpetual licences, run the system on your own or hosted infrastructure, and pick your release within the maintenance rules.

The commercial decision is rarely about technology. Converting perpetual licences into a subscription, the term, the renewal uplift cap, what happens to your data at exit, and the line between what SAP operates and what your application management team still has to do are the terms that decide the ten year cost. We negotiate them with you, with no arrangement with SAP or any partner that would colour the advice.

The business case has to survive without the 2027 date doing the work. We build it from the costs people forget: internal time, dual running, the hyperscaler or hardware bill, partner fees, custom code remediation, and licence exposure such as SAP's Digital Access model, under which indirect access is charged on the number of documents across nine document types while direct human access stays per user. SAP offers a free evaluation service to estimate those document counts; ask for it before you negotiate. Benefits need named executive owners: a faster close, fewer manual postings, stock accuracy, working capital released. Our guide to SAP S/4HANA cost in the UK covers the numbers, and our SAP consultancy page the wider service.

Choosing an S/4HANA migration partner and keeping the programme honest

Every S/4HANA migration partner will show you a method, a factory and a slide of logos. We run the selection on your facts instead: the partner's record on the path you have chosen, with similar custom code volume and data quality; the named people who will actually turn up, not the bid team; a fixed price for the discovery phase; acceptance criteria tied to the findings of SAP Readiness Check; measured downtime commitments; and a remediation plan for custom code. On that last point the tools are good. The ABAP test cockpit and the Custom Code Migration app classify custom objects as Used, Referenced or Not Used, and the Not Used pile is where decommissioning starts. A proposal to carry everything across deserves a question about why.

PEF has no alliance with SAP or with any systems integrator, so the recommendation is ours alone. Christopher Fagan was Project Director on the National Grid separation, where the software procurement he ran included an Oracle to SAP S/4HANA migration taken through to implementation, so he has sat on the buying side of exactly this decision.

Once the partner is chosen, assurance is about evidence rather than status reports. We expect to see repeated mock conversions with measured downtime, a reconciliation of general ledger balances, open items and stock between ECC and S/4HANA after every mock, interface testing at production volumes, and a go or no go decision made against criteria agreed months earlier. Where a programme has already slipped, we step in to recover it. Energy and water companies on SAP's utilities solution face a further set of questions, covered in our SAP S/4HANA utilities migration service, and the ERP integration page covers the interfaces that usually break first. Our fees are published openly on the pricing page.

What we have delivered

  • Ran the procurement of every software provider on the National Grid separation, more than 22 million assets, through to implementation including Oracle to SAP S/4HANA.
  • Delivered the Oracle to Microsoft Dynamics migration at BP Pulse 39 days ahead of forecast, with a £25m saving, the largest on a programme where PEF held the main contract.
  • Delivered the £9bn Energy Bills Support Scheme for Ofgem, BEIS and HMRC.
  • Implemented and delivered most major finance systems over 19 years: Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access.
  • A suite of consultants who have led and analysed pre, mid and post migration decisions and implementations across ERP and CRM platforms, independent of every vendor.

Questions we are asked

When does SAP support for ECC end?

SAP's mainstream maintenance for the core applications of SAP Business Suite 7, including SAP ERP 6.0 on its latest three enhancement packages, ends at the end of 2027. Optional extended maintenance runs from the start of 2028 to the end of 2030 at a premium of two percentage points on the maintenance basis. After that, customers receive customer specific maintenance only, unless they qualify for SAP's private edition transition option.

What is the SAP ERP private edition transition option?

It is a subscription offer for SAP's largest and most complex customers who cannot complete the move to S/4HANA by the end of 2030. The system must be migrated to SAP ERP, private edition on SAP HANA before 31 December 2030, be at least 2 TB and take SAP's max success plan. It was designed to cover 2031 to 2033, and SAP's update of 13 October 2026 says subscriptions may run until 31 December 2035, subject to further prerequisites.

Should we choose greenfield or brownfield for our S/4HANA migration?

Brownfield, a system conversion, keeps your configuration, custom code and history and is quicker where the current system is sound. Greenfield, a new implementation, suits organisations whose processes or data need a reset, or whose custom code has become unmanageable. Selective data transition sits between the two and suits consolidations. The honest answer comes from the custom code analysis, the data quality and the appetite for process change, not from a partner's preferred factory.

Do we have to move to RISE with SAP?

No. RISE with SAP is SAP's subscription bundle of S/4HANA Cloud Private Edition, hyperscaler infrastructure, technical operations and Business Technology Platform credits under one contract. On premise S/4HANA with perpetual licences remains a route, as does the public cloud edition for simpler organisations. The right answer depends on your appetite for running infrastructure, the licence conversion terms on offer, your exit position and how much the business needs to modify standard SAP code.

How do we choose an S/4HANA migration partner?

Select on evidence for your chosen path, not on brand. Ask for named people, their record on conversions or new implementations of similar size, a fixed price for discovery, acceptance criteria tied to SAP Readiness Check findings, downtime commitments and a custom code remediation approach that decommissions unused objects. Run scripted demonstrations on your scenarios and make your own reference calls. An independent adviser with no alliance to SAP or any partner should run the process.

Is 2027 driving your plan, or are you driving it?

Tell us where your SAP estate stands and we will give you an independent view on the path, the commercial model and the partner question.

Book a conversation