Conversion and Update
SAP ECC to S/4HANA
Powered by AI

MIGNOW was created to address a pressing issue. SAP had launched SAP S/4HANA, and by 2025 (later extended to 2027), all 40,000 SAP ECC customers worldwide would need to migrate to this version.

However, there was a shortage of consultants available to handle these projects. To automate the process, we initially developed an RPA-based solution. This led us to discover another major problem in the SAP Ecosystem: the lifecycle of SAP S/4HANA has changed. Each version now has a lifespan of only 5 years, requiring customers to upgrade every 4 years to maintain enterprise support.

That's why we believe MIGNOW should not only assist customers with the conversion to S/4HANA but also facilitate the annual upgrade process.

The main difference between Mignow’s projects and traditional ones is that we utilize an AI tool to accelerate and automate conversion processes. Once we substitute manual executions, we can reduce the project’s time and costs.

Brownfield → We carry all settings, customizations, and transactional data, that is, the whole historic background and migrate them to the new system.

Bluefield/Shell Conversion → We take the settings and all programs involved, except the transactional data. The clients can have a fresh start with SAP. After that, the master data load migration, balance sheet (billing) and open itens are necessary.

MIG conversion is a product, approved by SAP for the automation of Upgrade and Conversion Processes, which uses Artificial Intelligence to make decisions about the conversion processes.

It identifies SAP adjustment points and uses SAP conversion tools, connectivity via API, and SAP best practices and knowledge acquired in the various conversion processes performed by us.

Sizing is estimated by SAP programs, available in SAP notes.

The conversion is performed and then the environment is moved to SAP RISE, depending on the conversion strategy.

If the question is whether the Zs objects are lost, or cease to exist:
Nothing happens with the Zs objects. They continue to exist in the converted environment.

If the question is what do we do with them after the conversion:
There is a possibility that some Z object is dependent on some STANDARD object that becomes obsolete. In this case, it will also become obsolete and may even have errors, but it is due to the standard object. Zs objects may also have obsolete instructions, which will be handled in ATC.

There is no defined methodology. There are “manuals” from SAP itself that indicate how these obsolete instructions can be fixed. We try to follow these documents as much as possible.