Current state and readiness
We review the system, the custom code and the data quality, and show what should be cleaned up before the conversion.
From the roadmap through the business blueprint to stable operation. We guide companies through the move to SAP S/4HANA without bringing daily business to a halt.
Maintenance for SAP ECC is running out, which puts the question of when and how to move to SAP S/4HANA on the table. The technical conversion is rarely the hard part. It gets demanding when processes that have grown over the years, hundreds of custom developments and a daily business that cannot stand still all have to be handled at once.
We start by looking at where you are. Which processes run on the standard, which custom developments are still in use at all, which data has to come along? Out of that comes a roadmap you can put in front of your management, with effort, sequence and risks.
Individual building blocks or continuous support, depending on the project phase.
We review the system, the custom code and the data quality, and show what should be cleaned up before the conversion.
Sequence, effort and benefit in a form that is also understood outside the IT department.
We assess both routes against your processes rather than a rule of thumb, and explain the recommendation.
Target processes in logistics, production and procurement, agreed with the departments and documented for implementation.
Migration concept, mapping rules and test migrations, so that no surprises turn up on the go-live weekend.
Cut-over planning, test coordination, key user training and support during the critical first weeks.
You get effort estimates based on objects counted in your system, not on experience from someone else's project.
We bring production, purchasing and logistics in early. People who helped shape a process will also carry it later.
You talk to the person who is also in the project, not to an account manager.
It depends on how well your current processes fit the standard and how much legacy sits in the system. For heavily customised systems with a lot of unused custom code, a rebuild often pays off. Where processes are clean, conversion is faster and cheaper. We assess both against your system before making a recommendation.
For a mid-sized company, typical projects run between nine and eighteen months. The decisive factors are the number of sites, the state of the master data and how many custom developments have to come along.
Often yes, if someone with project experience takes the lead and the departments really get the time. In that case we take on project management or architecture, and the knowledge stays in the house.
Tell us where you stand. A first conversation costs you nothing but an hour of your time.
Discuss your project