EN
Service

Your path to SAP S/4HANA, decided by the state of your data.

We recommend the path based on your data and lead your SAP S/4HANA migration from the readiness assessment and decision through to stable operations. We are not tied to any software vendor and do not sell licenses.

Key deadlines
  • ECC on EHP 6 or higher: mainstream maintenance until December 31, 2027
  • Extended maintenance for an additional fee until the end of 2030
  • Migration: one to two years from project start

Typical situations

End of maintenance is getting closer, and the path is still open.

Brownfield or greenfield has not been decided, and no one in-house has time to prepare the question properly. Every month without a decision shortens the time left for the project.

A partner is already working on the implementation.

Independent leadership on your side keeps plan, quality, and budget in view and keeps the decisions with you.

The project is running, but it is slipping.

Test migrations (mock migrations) fail and milestones move. Your executive team needs a clear picture of where things stand.

What we take on

We work on your side of the table, either advising your team or leading the project.

  • Readiness assessment of system landscape, custom code, data, and interfaces
  • Interpretation of the SAP Readiness Check results
  • Decision paper on brownfield, greenfield, or selective data transition
  • High-level plan with milestones, budget range, and risks
  • Requirements and evaluation criteria for partner selection
  • Project management with a steering committee and quality assurance of partner deliverables
  • Test management with test strategy, integration testing, and user acceptance testing
  • Key user concept and training
  • Cutover planning, hypercare, and handover to operations

Three paths to SAP S/4HANA

The readiness assessment shows which path fits. The paths differ mainly in what happens to configuration, custom code, and history.

PathWhat happensFits whenWatch out for
Brownfield
System conversion
Your existing ECC system is converted to S/4HANA, including configuration, custom code, and history. Your current processes work, and you want to keep the full history.Legacy issues carry over. Check custom code and data quality first.
Greenfield
New implementation
S/4HANA is set up from scratch. Master data and transactional data are migrated selectively. You want to change processes fundamentally, or the legacy system is heavily customized.More effort for process design and migration. History stays in the legacy system or an archive.
Selective data transitionA new system based on the old one, with selected organizational units, time periods, or data. You want to redesign some areas and carry others over unchanged, for example in consolidations.Requires specialized tools and partners. Plan for them early.

Experience from S/4HANA projects

We have led ERP implementations through go-live, most recently with SAP S/4HANA.

Industrial company

Overall responsibility for an S/4HANA implementation

We led the overall project on an interim basis and reported to the executive board. We were also responsible for test management, including integration and acceptance testing, and for cutover management. Around 70,000 fixed assets and 7,000 material masters were migrated to the new system.

Our role: Overall project leadership, test and cutover management

Plant maintenance

SAP S/4HANA and custom software

We set up the agile framework and managed the development of the custom software that replaced the previous plant maintenance module (PM). We aligned processes, data ownership, and interfaces to S/4HANA in step with development.

Our role: Agile framework, development management, and interfaces to SAP

More project examples

Step by step

From the readiness report to the handover to your operations team.

  1. Readiness assessment

    Review of landscape, data, and processes. Result: readiness report and recommendation.

  2. Decision and planning

    Together with your executive team: path, high-level plan, budget, and partner selection.

  3. Managing the implementation

    Design, build, testing, and test migrations, with milestones and agreed leeway for schedule and budget.

  4. Cutover and hypercare

    Cutover according to the runbook, support through the first weeks, and handover to your team.

Starting point

Readiness assessment

If your path to S/4HANA is still open, the readiness assessment gives your executive team the basis for its decision. We agree on the scope in the initial call.

What you get
A readiness report with the risks and a decision paper on the transition path, including key dates and the maintenance you will need.
What we look at
System landscape, custom code, data, processes, and interfaces, plus the quality of your master data from a business perspective. We interpret the results of the SAP Readiness Check.
What we need from you
Read access to the ECC system or data extracts, a contact in IT, and interviews with the business teams, from purchasing to asset accounting.
How it works
At the kickoff, we agree with you on goals, contacts, and dates. Then we analyze the system and talk to IT and the business teams. The report sets out brownfield, greenfield, and selective data transition with their consequences for your company. We discuss our recommendation with your executive team.

What you take away

  • Executive team and CFOYou decide on the path and budget range, based on a paper with the consequences for schedule, budget, and risk. You set the go/no-go criteria before the cutover weekend begins.
  • IT leadershipThe readiness report shows you what the system landscape, custom code, and interfaces mean for the migration. We review the partner's deliverables for you, and testing follows a test strategy with integration and acceptance testing.
  • Project managementYou run the project according to a high-level plan with milestones and roles and give the steering committee a one-page status report. For the cutover weekend, you have a cutover runbook with owners and checkpoints.
  • Business teamsIn purchasing, the warehouse, materials planning, and asset accounting, you cleanse your data according to agreed rules, with owners per data area. After every run, you check quantities and values in the reconciliation report, and your key users are trained before go-live.

Questions about this service

Do we need the SAP Readiness Check?

It is a good starting point. SAP provides the tool. It checks your ECC system for technical prerequisites, custom code, and affected functionality, and gives initial pointers on processes and financial data.

It does not assess whether your master data is clean from a business perspective or whether your organization fits the target design. We add that in the readiness assessment.

How are you different from our implementation partner?

We review designs and tests, keep your interests in view, and present decisions with their consequences to the steering committee. We sell neither licenses nor partner services, so our recommendations stay independent.

Cloud or our own data center?

SAP offers SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, and SAP S/4HANA on-premise. Which option fits depends on your customizations, your IT strategy, and your contracts. We put the options side by side, with their consequences for operations, customizations, and cost.

What does an S/4HANA migration cost a mid-sized company?

The main cost drivers are company codes and plants, custom code and interfaces, the volume and quality of your data, and the target date. A reliable figure is possible once the starting situation is known. The readiness assessment provides the basis for it before a large budget is committed.

How long does an S/4HANA migration take?

Depending on scope, one to two years from project start to go-live, plus the decision and partner selection. That is enough for a first estimate; the readiness assessment provides the basis for your schedule. Starting today, a go-live by the end of 2027 is realistic only in exceptional cases.

For most companies, this means budgeting for extended maintenance and starting now.

Often combined with

Related articles

Initial call: 30 minutes, free of charge.

Tell us about your system landscape and timeline. We will tell you where we see risks and whether we are the right fit.

Initial call Call