The path to
SAP S/4HANA
begins before the
technical conversion.
A successful conversion requires more than a scheduled go-live. What matters is how well the existing SAP landscape is prepared – technically, organizationally and with a view to subsequent operations.
From the
system landscape
to the target operating model
SAP S/4HANA is not
a single migration weekend.
The move to SAP S/4HANA affects the technical foundation of core business processes. That is why a conversion does not begin with the technical changeover itself. Before then, it must be clear which prerequisites have been met, which dependencies exist and which measures can be prepared in advance.
SK supports companies from an SAP Basis perspective: from analysis and technical preparation through conversion, testing and go-live to the transition into reliable operations.
The clearer the starting point is
at an early stage, the more manageable
the conversion becomes.
Many tasks on the path to SAP S/4HANA can be prepared before the actual conversion project begins. This helps make technical dependencies visible, plan internal resources more realistically and identify risks before go-live.
Plan
early
Key questions at the outset:
- Which conversion method best fits the current SAP landscape?
- Which systems, interfaces and custom developments are affected?
- Which data sets should be prepared or cleansed?
- Which internal resources will be needed, and when?
- How can ongoing operations remain reliable during the conversion?
- How will the transition to production operations be prepared?
Six steps to a well-prepared
SAP S/4HANA conversion
A conversion becomes more manageable when analysis, preparation, execution, testing and the transition into operations are clearly separated. This keeps tasks, responsibilities and decisions transparent throughout the project.
Approach
Analysis
The analysis creates transparency regarding the existing SAP landscape. This includes the SAP Readiness Check, system analysis, technical prerequisites, data volumes, interfaces, custom developments and potential dependencies.
Result
A reliable assessment of the starting point, the appropriate conversion method and the necessary preparation packages.
Planning
Based on the analysis, a joint roadmap is developed. Technical steps, business continuity, resource planning, budgeting and responsibilities are brought together.
Result
A project plan that translates the conversion into clear phases, tasks and decision criteria.
Preparation
During preparation, the necessary measures are implemented step by step, including updates, data cleansing, custom code analyses, sandbox systems and other technical adjustments.
Result
An SAP landscape that meets the key prerequisites for the conversion and enables initial testing.
Execution
The technical conversion follows a coordinated implementation plan. Test conversions and dry runs help assess time windows, risks and escalation paths more accurately before go-live.
Result
A technically converted SAP S/4HANA system as the basis for testing, acceptance and production launch.
Testing
Testing covers systems, interfaces, authorizations and relevant processes. Deviations are documented, assessed and addressed before go-live.
Ergebnis
A sound go/no-go decision based on documented test results.
Go-live and transition into operations
Go-live marks the start of production operations. During this phase, monitoring, dedicated contacts, fast coordination and documented handovers are particularly important.
Result
A controlled transition into SAP Basis operations with clear responsibilities and structured ongoing support.
Technical
preparation
Many tasks can be
clarified before
the actual conversion begins.
The analysis and SAP Readiness Check result in specific preparation packages. Which packages are relevant depends on the existing system landscape, data sets, custom developments and the desired target operating model.
Potential preparation packages:
Unicode conversion
Reviewing and preparing Unicode capability as a technical prerequisite.
Updates and upgrades
Updating software and database versions to reduce technical dependencies.
Archiving, reorganization and deletion
Reducing data volumes, runtimes and technical baggage before the conversion.
Custom code analysis
Assessing custom developments in terms of usage, relevance and compatibility
Conversion to Business Partner
Preparing existing customer and supplier structures for the Business Partner model.
SAP S/4HANA sandboxing
An early test environment for IT, key users and initial experience with new functions.
SAP Fiori
Technical deployment, authorizations and coordination with relevant user groups.
SAP Smart Forms and other forms
Reviewing existing forms and output procedures before go-live.
SK’s
role
Clearly define
SAP Basis responsibilities.
SK supports S/4HANA projects where the system landscape, technical conversion and subsequent operations converge. The focus is on SAP Basis, hosting, remote operations and the technical preparation of the systems.
Application-specific or process-related consulting can be provided by existing consulting teams, business departments or partners. What matters is that roles, interfaces and responsibilities are clearly defined.
This clarifies:
- which tasks SK handles
- which topics remain with internal IT
- which tasks are supported by functional consultants or partners
- how information flows between everyone involved
- who serves as the point of contact during analysis, conversion, testing and go-live
Operations
after the
conversion
The target architecture
belongs on the project plan
from the outset.
The move to SAP S/4HANA also raises the question of how the future system landscape should be operated. Private cloud, public cloud, hybrid landscapes and dedicated hosting models differ in flexibility, adaptability, cost structure and allocation of responsibilities.
SK supports the technical assessment and combines infrastructure, SAP Basis operations and responsibility in a transparent operating model. What matters is not the label ‘cloud’, but whether the selected environment fits the system landscape, the business processes and the desired allocation of responsibilities.
A conversion
does not end
at go-live.
After go-live, it becomes clear how the new SAP S/4HANA landscape performs under real operating conditions. Performance, interfaces, authorizations, background processes and open issues require continued monitoring and assessment.
A structured transition into operations ensures that project knowledge is retained, responsibilities are clear and the new SAP Basis operations do not begin in a purely reactive mode.
From project
to operations
This includes:
- close monitoring during the ramp-up phase
- assessment of technical anomalies
- dedicated contacts and fast coordination
- documented handover from the project
- transition into the agreed operating modell
The essentials
at a glance
What a well-prepared
SAP S/4HANA conversion
makes possible
- Transparency regarding prerequisites, dependencies and effort
- a realistic roadmap for technology, resources and budget
- phased implementation of the necessary preparation packages
- clearly defined roles during analysis, testing and go-live
- a sound basis for the go/no-go decision
- a controlled transition into future SAP Basis operations
This turns a complex transformation project into a transparent path from the existing system landscape to future operations.
Frequently asked
questions
Questions about the
SAP S/4HANA conversion
What is an
SAP S/4HANA conversion?
An SAP S/4HANA conversion technically transforms an existing SAP ERP system into SAP S/4HANA. This requires reviewing and preparing system prerequisites, data sets, custom developments, interfaces and affected business processes.
What does the
SAP Readiness Check show?
Der SAP Readiness Check liefert eine erste technische The SAP Readiness Check provides an initial technical foundation for preparing an S/4HANA conversion. It identifies relevant preparation topics, potential dependencies and technical areas requiring action, but does not replace a detailed system analysis.
What role does SK play
in an S/4HANA conversion?
SK supports the conversion from an SAP Basis perspective. This includes technical analysis, system preparation, planning, conversion support, testing, go-live support and the transition into SAP Basis operations.
Why does an S/4HANA conversion
not end at go-live?
After go-live, the new system landscape must prove itself in day-to-day operations. Monitoring, performance, interfaces, authorizations and open issues require continued assessment and integration into a structured operating model.
Next
step
SAP S/4HANA
begins with a
clear starting point.
In an initial conversation, we discuss where your system landscape stands today, which preparations have already been completed and which technical questions still need to be clarified. From there, we can determine the next steps that make sense for your project.