Migrating to SAP S/4HANA:
11 recommended requirements
for preparation and pilot stage

Global-S4HANA-WP-MOCK-UP

Download white paper:
Discover 11 recommendations when moving to SAP S/4HANA, including SDT

Any conversion or migration to SAP S/4HANA® – whether focused more towards the IT or business end of the project spectrum – must consider data, business processes and transformation as part of the journey.

Unlike the R/2 to R/3 conversions of the 1990s and early 2000s, clients now have a significant weight of data, long historical processes, and lots of custom code. Businesses now also have to contend with greater cyber threats and tighter regulation of private data. We recommend that any early stage analytics, design and piloting of SAP S/4HANA considers these concerns.

These recommendations are for any SAP client on SAP R/3 who:

  • is in the early stages of assessing SAP S/4HANA
  • has a reasonable weight of data and history in the existing system
  • is considering a Selective Data Transition (SDT) approach to any kind of S/4 implementation – whether taking a brownfield, greenfield or hybrid approach.

Our recommended requirements make SDT an integral consideration in early requirements, so that this approach can be proven or disproven as the appropriate approach.

About the author

Jamie Neilan

Jamie is the Head of EPI-USE Labs’ Transformation Services Community, with 24 years of experience in the IT services industry, primarily with businesses using SAP. Jamie’s career started as an SAP Technical Consultant and Enterprise Applications Developer around an R2 to R3 SAP project; he then went on to specialise in SAP Data Projects, Basis, RunSAP and Solution Architecture. He has a variety of SAP certifications, and his background includes programming, databases and SAP S/4HANA SDT, Payroll, Privacy and Test data projects with EPI-USE Labs. Jamie has oad experience of SAP clients from every industry, and is excited about leveraging SAP and EPI-USE Labs’ technology to ing value to our clients.