“I would say, holistically, the SAP Readiness Check gave us a few things.
One of them was, what programs do we need to fix? …. It’s kind of holistically packaged up what we needed to know to get SAP S/4HANA implemented and done successfully.”
SAP manager, chemicals industry
“It’s beneficial to better understand the system, and to better understand
what the pain points could be if we migrate to SAP S/4HANA, and to find
things that can be fixed right now. No need to wait until the migration to fix
that. We get a lot of insights out of these reports for our daily work.”
Head of SAP financials, retail industry
“SAP Readiness Check was most instrumental for the sizing that we needed, and then what customization we were going to have to address.”
“The pre-SAP S4/HANA activities that were brought out in the SAP Readiness Check that we need to get fixed, if it wasn’t for that[report], we would not be doing it.”
“[Without completing preparation steps,] it would have been a risk, which means now our nine-month implementation goes to 12 or 14 months. It would have extended the implementation time. . . . I would say we’ve eliminated 90% of the risk.”
“Let me tell you from the SAP Readiness Check session, we have already started implementing changes, so when we do the SAP S/4HANA migration, the time will be a little bit reduced because we already started in the current development environment.”
“It increased the confidence that our system is really well prepared and that we have an up-to -date system that’s technically in good shape. That was also the feedback from SAP. We really got the confidence that if we want to go on the SAP S/4HANA journey and want to migrate, from the technical perspective, there shouldn’t be a problem.”
“This helps the organizations avoid up to three months of unexpected design and implementation time and cost, and it increases confidence in the migration roadmap.”
–Forrester Consulting
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
2 | |
2 | |
2 |