Readiness and custom code
Unused code retired, the rest remediated wave by wave.
Mainstream maintenance for SAP ECC 6.0 ends on 31 December 2027. We move your landscape in fixed-price 30-day sprints.

An SAP S/4HANA migration moves you from SAP ECC 6.0 to S/4HANA, SAP's current ERP, by system conversion, new implementation or selective transition.
SAP has committed to maintaining S/4HANA until the end of 2040.
Status is calculated from today's date in Australian Eastern time.
Sources: SAP maintenance strategy, SAP News (February 2020), SAP Learning: NetWeaver 7.5 maintenance. SAP has also announced a paid transition option that can extend support for some customers to the end of 2033. It is a cloud subscription, and it requires the relevant systems to be on SAP HANA by the end of 2030.
Each workstream is one or more fixed-price sprints. Illustrative examples.
Unused code retired, the rest remediated wave by wave.
Master data converted to business partners and reconciled.
Interfaces rebuilt before PI/PO 7.5 leaves maintenance.
Reports moved and reconciled to today's figures.
Customisations moved into documented extensions. See API wrappers.
Every ECC customer faces the same date, so specialist capacity is likely to tighten as 2027 approaches.
The 2033 transition option needs your systems on SAP HANA by the end of 2030.
From 2028 you pay more for the same software.
S/4HANA needs HANA and Unicode, so older systems have steps to take first.
Work done in sprints now makes the conversion weekend smaller and safer.
Every sprint ends with sign-off and your go or no-go call.
Not on SAP HANA yet? Start with SAP HANA migration
Five business days to sequence your SAP landscape, from A$9,500, credited in full if you go ahead within 60 days. Each sprint is fixed-price from A$50,000.
from A$50,000 per sprint
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, a cloud subscription that requires the relevant systems to be on SAP HANA by the end of 2030, that can run to the end of 2033 for some customers. It is not an extension of on-premise maintenance.
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.
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.
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.