On the path to S4 HANA - full or partial data migration?

21-03-18 | Blog

Congratulations. You just received the sign off for the move to the new SAP S4 HANA system.

What's next?

Will you be taking ALL of the data in your current system to the new one (greenfield approach)?
Are they really ALL needed in-memory?

The best first thing is to inform all business departments of this move and how this will impact their routine and one demand access to SAP data in applications or in the system.

At the same time, start to identify data that can be archived vs data that needs to be migrated over (conversion roadmap). For two reasons:
 1. Keep a lean new SAP S4 HANA system running with only the data that are required for daily access.
 2. Comply with legal retention requirements for specific data groups.

Next, set an archiving strategy to ensure that the archived data will be:
 - Securely and easily accessible for business continuation
 - Future-proof and audit-ready for tax audit requirements (i.e. one-off tax audit review, country SAF-T compliance, etc.).
At TJC, these are precisely two of our objectives for any SAP archiving project. You can read more about our TJC archiving expertise here.

Finally, partially migrate your data to the new system.

However, you are then left with a SAP legacy system that you still need to maintain and run which can become costly due to the hardware and human resource required. This cost also extends to the vulnerability to security issues that your SAP legacy system may face. 

Read the next post on how you can minimize the costs.