Readiness and custom code
Custom code checked against SAP's S/4HANA simplification items, unused code retired, and what remains remediated wave by wave, so the conversion itself is short and predictable.
SAP migration
SAP ECC to S/4HANA, before the 2027 deadline.
Mainstream maintenance for SAP ECC 6.0 ends on 31 December 2027. We move your landscape in fixed-price 30-day sprints, so progress is visible, funded and signed off one piece at a time.
What is an SAP S/4HANA migration?
An SAP S/4HANA migration moves an organisation from SAP ECC 6.0 (SAP Business Suite 7) to SAP S/4HANA, SAP's current ERP, which runs only on the SAP HANA database. There are three common paths: a system conversion (brownfield) that keeps your configuration and history, a new implementation (greenfield) that redesigns processes, and selective data transition, which moves chosen company codes, processes or years.
Whichever path you choose, the work splits into the same workstreams: custom code remediation, data cleansing and migration, interfaces, analytics, testing and cutover. SAP has committed to maintaining S/4HANA until the end of 2040.
The SAP dates that matter
Status is calculated from today's date in Sydney.
- 31 Dec 2027SAP ECC 6.0 (SAP Business Suite 7)Mainstream maintenance ends for EHP 6, 7 and 8Upcoming
- 31 Dec 2027SAP NetWeaver 7.5, including BW 7.5 and PI/PO 7.5Mainstream maintenance endsUpcoming
- 31 Dec 2030SAP ECC 6.0 and NetWeaver 7.5Optional extended maintenance ends (at a premium)Later
- 31 Dec 2040SAP S/4HANASAP's maintenance commitment runs to the end of 2040Later
Sources: SAP maintenance strategy, SAP News (February 2020), SAP Learning: NetWeaver 7.5 maintenance. SAP has also announced a paid transition option, tied to a move to its cloud ERP, that can extend support for some customers to the end of 2033.
Your SAP move as 30-day workstreams
Each workstream runs as one or more fixed-price sprints, each with its own sign-off. Illustrative examples; your sequence is set in the Migration Blueprint.
Data cleansing and migration
Customer and vendor master data converted to business partners, quality issues fixed at the source, and load cycles reconciled against ECC.
Interfaces off PI/PO
Interfaces inventoried, retired or rebuilt on SAP Integration Suite before SAP Process Orchestration 7.5 leaves mainstream maintenance.
Analytics after BW 7.5
Reports and data flows moved to BW/4HANA, SAP Datasphere or a modern lakehouse, with figures reconciled to today's reports.
A clean core
Customisations moved out of the ERP into documented extensions and APIs, so future upgrades stay simple. See API wrappers and integration.
Why start now
- Every ECC customer faces the same date, so specialist capacity will tighten as 2027 approaches
- Extended maintenance from 2028 costs more for the same software
- S/4HANA needs HANA and Unicode, so older systems have prerequisite steps that take time
- Work done in sprints now means the final conversion weekend is smaller and safer
- Every sprint ends with reconciliation signed off by your data owners, a rehearsed rollback and a go or no-go decision that stays with you
Not on SAP HANA yet? Start with SAP HANA migration
A Migration Blueprint, then fixed-price sprints
Five business days to assess your SAP landscape and sequence the workstreams, from A$9,500 and credited in full against your first sprint if you go ahead within 60 days. Each 30-day sprint is then fixed-price from A$50,000.
from A$50,000 per sprint
When does SAP ECC support end?
Mainstream maintenance for SAP ECC 6.0 (SAP Business Suite 7) on enhancement packages 6, 7 or 8 ends on 31 December 2027; older enhancement packages need an upgrade to be covered. SAP offers optional extended maintenance from 2028 to the end of 2030 at a premium of two percentage points on the maintenance basis. SAP has also announced a paid transition option, tied to a move to its cloud ERP, that can run to the end of 2033 for some customers.
Can you move all of SAP ECC to S/4HANA in 30 days?
Not for most landscapes, and any promise that you can deserves scrutiny. A full move is a series of workstreams: custom code, data, interfaces, analytics, testing and cutover. We deliver them as fixed-price 30-day sprints, so you see progress, control spend and can pause between sprints.
Should we choose brownfield or greenfield?
A brownfield system conversion keeps your configuration and history and is usually faster. A greenfield implementation lets you redesign processes but costs more. Selective data transition sits between the two. The Migration Blueprint compares the options for your landscape and recommends one in writing.
Do we need RISE with SAP?
No. SAP S/4HANA can run on-premise, in a private or public cloud you control, or under a RISE with SAP subscription. We are independent and do not resell SAP, so we help you compare the options on cost, control and risk.
What about SAP BW and SAP PI/PO?
SAP BW 7.5 and SAP Process Orchestration 7.5 run on SAP NetWeaver 7.5, which also leaves mainstream maintenance at the end of 2027, with optional extended maintenance to 2030. They are often the quickest wins and fit well into single sprints.