We support organisations converting from SAP ECC to SAP S/4HANA using a brownfield, greenfield or selective data transition approach. We also help assess whether RISE with SAP, GROW with SAP, Private Cloud or an on-premise model is the right fit.
Mainstream maintenance for SAP ECC ends on 31.12.2027. For most organisations, the realistic moment to start preparing for conversion falls in 2026.
A conversion to SAP S/4HANA typically takes 12-18 months. In larger and more complex SAP environments, the project may require a longer schedule. Starting too late carries the risk of limited integrator availability, rising costs, and time pressure ahead of the end of mainstream maintenance.
We compare on-premise, RISE with SAP, GROW with SAP and Private Cloud based on the client's financial and operational data. The analysis can include NPV, IRR and a 10-year horizon, so the decision is grounded in numbers rather than vendor claims alone.
A custom ABAP code audit before conversion helps identify, ahead of time, elements that could complicate migration or increase project cost. The earlier dependencies, modifications and unused objects are identified, the easier it is to manage risk during conversion.
Before conversion, we analyse process criticality and regression testing scope. Process mining can help identify which business paths matter most, where deviations occur, and which processes require particular control before go-live.
We assess the organisation's readiness for conversion: system landscape, custom code, data, integrations, authorisations and technical constraints. The assessment results in a recommended path: brownfield, greenfield or selective data transition.
We compare on-premise, RISE with SAP, GROW with SAP and Private Cloud models. We prepare a cost, risk and operational-impact analysis that can support a decision by the board, the CFO and the teams responsible for SAP.
We analyse custom ABAP code, identifying objects that require migration, refactoring or retirement. We support a Clean Core approach, including limiting modifications to the standard and moving selected extensions outside the core, for example to SAP BTP.
We prepare and carry out the technical conversion using SAP Software Update Manager and the Database Migration Option. Scope covers sandbox, DEV, QA and PROD, a service-window plan, and measures to limit downtime.
We prepare a test strategy based on process criticality, process mining data and business risk. Scope can include a Test Plan, Test Strategy and Test Completion Report in line with ISTQB good practice.
After go-live, we provide intensive support during the stabilisation period. Hypercare covers incident handling, error analysis, performance optimisation, and support for business and technical teams after conversion.
The project begins with a workshop for the board and key stakeholders. We discuss strategic goals, time and budget constraints, the desired level of change, and the preferred target model: on-premise, RISE, GROW or Private Cloud.
We then carry out the S/4HANA Readiness Assessment, analysing the system landscape, custom code, integrations, data, authorisations and dependencies that could affect project scope and schedule.
On this basis we recommend a conversion path and prepare the project plan, Clean Core scope, an approach to extensions on SAP BTP, and a regression testing and UAT strategy.
We carry out the conversion in line with the SAP Activate methodology, with an emphasis on practical regression testing, downtime control, and preparing the organisation for go-live.
After go-live, we support system stabilisation during hypercare, resolving incidents quickly, tuning performance, and reducing the risk of disruption to business processes.
Technology stack
Partnerships backed by our team's certifications. Full authorisation for delivery and support.
Industrial manufacturer
Brownfield conversion from ECC to S/4HANA on-premise. The project took 14 months, with production downtime limited to under 36 hours.
Retail sector company
Selective data transition from ECC to S/4HANA RISE. The project included a 60% reduction in custom code and preparation of the target environment for cloud operation.
Corporate group
A TCO analysis for the board and CFO. The project compared RISE with SAP against the on-premise model as the basis for a strategic decision.
It depends on the state of the current system, technical debt, data quality, custom code and business strategy. Brownfield is typically faster and less costly, but carries forward some historical constraints. Greenfield gives a cleaner start but requires greater organisational change. Selective data transition can be a compromise between the two approaches.
It depends on the organisation's profile. RISE can simplify operations and increase cost predictability, but over the long term it may be less cost-effective for large, stable SAP landscapes. On-premise offers greater control but requires maintaining SAP BASIS skills and infrastructure. A TCO analysis allows the two models to be compared for a specific organisation.
A brownfield conversion for a medium-sized SAP landscape typically takes 12-18 months. For larger organisations, multiple systems, extensive integrations or a large volume of custom code, the project may take 18-30 months.
Mainstream maintenance for SAP ECC ends on this date. This means the loss of standard support for new functionality and fixes provided under basic maintenance. Extended Maintenance until 2030 may be available, but comes with additional costs.
