In SAP terms, a brownfield migration implies upgrading your existing SAP ECC system to SAP S/4HANA without the need to start from scratch all over again. You can keep your current setup — such as data, custom developments and business processes — and convert them to the new platform. However, a brownfield migration requires proper preparation and a clear timeline. The earlier you start, the better you can manage risks, seize opportunities and stay on track with your goals. Factors like system complexity, data volume, process changes and business involvement will all play a role in shaping your timeline.
This blog will walk you through eight practical steps you can start taking today to turn your move to SAP S/4HANA into a smooth and controlled journey.
1. Data preparation
Data preparation is crucial for a successful migration. Develop a data cleansing strategy and eliminate outdated, inconsistent or duplicate data. This proactive approach minimises issues during and after the migration as ALL your data in the SAP ECC system are converted.
The data cleansing exercise can focus on both master data and transactional data. Analysis and actions should also be performed on data tables both from a disk requirement and memory requirements perspective. Cleansing will positively affect your sizing requirements and future costs.
2. Business partners
In an SAP S/4HANA system, business partners are used as the leading master data object and single-entry point to maintain, including both customers and vendors. Customer vendor integration (CVI) is the process which ensures the synchronisation between customer/vendor on one side and the business partner on the other, and vice versa.
Performing the CVI conversion is a prerequisite for moving to SAP S/4HANA with the brownfield migration approach. You can already execute this preparation and synchronisation (of C/V to BP) in your SAP ECC system without risking any business impact.
3. Custom/ABAP code
Even if you have decided to keep what you have and convert it to SAP S/4HANA, not all of your custom/ABAP code may be SAP S/4HANA compatible. On top of that, the clean core strategy (to limit custom code in the core ERP) is now fully embedded in the brownfield project SAP activate methodology. To reduce the effort spent on custom code during the project, you can already begin the following activities now:
- Start collecting usage data for your custom code with the ABAP call monitor
- Delete any unused or outdated custom/ABAP code
- Challenge the build on new custom code in the current SAP ECC system
4. System architecture and integrations
Naturally, you want your converted SAP S/4HANA system to be integrated seamlessly into your total system architecture as before! As the set-up and testing of integrations is one of the key risk factors of conversion projects, proper and detailed preparation is the way to go! This is why we strongly advise to perform the following three steps:
- Create a clear overview of your system landscape. List all the systems that connect to your SAP ECC system and describe how they interact. For each integration, include their technical setup (how the systems communicate), the reason why the connection exists (business purpose) and the type of data or information that is being exchanged.
- Identify technical and functional owners and documentation for each integration.
- Based on the readiness check, start preparing for the add-ons that will not be SAP S/4HANA compatible anymore. Pro-actively engage where needed to launch any required actions on satellite systems.
5. Launch an SAP Signavio initiative
SAP S/4HANA offers numerous best practices and advanced functionalities. While the migration strategy may still be discussed, installing SAP Signavio on your current SAP ECC system can give your organisation a first insight into optimisation options across all business processes.
And while you are at it, why not make the migration a joint success for both business and IT? If you engage with the business well in advance – empowered by SAP Signavio – you can evaluate together where improvements can be made before, during and after the brownfield migration.
6. Identify (business) pre-projects
Depending on the set-up of your current SAP ECC system and your relevant business processes, it may be possible that certain topics, ‘pre-projects’, can be launched well ahead. Launching and executing these pre-projects before the brownfield migration diminishes the additional elapse time, effort and complexity of the SAP S/4HANA project.
Examples of pre-projects are the implementation of New RAR (revenue account recognition), the set-up of New GL (for parallel accounting) or the set-up of MRP areas (for planning of materials in plants).
7. Set clear objectives for the brownfield project
If you have the chance, embrace enhancing your business processes and kickstarting digital transformation. No matter the approach selected for the brownfield migration, define clear project objectives, determine how SAP S/4HANA can strategically benefit your organisation and ensure executive sponsorship from the earliest stages and throughout the project.
8. Establish a realistic roadmap in line with objectives
A realistic timeline prevents unnecessary pressure and increases your chances of success. Allocate sufficient time for at least one Sandbox conversion and the UAT business testing, including end-to-end integration testing. Depending on the degree of process improvements and new functionalities included in your brownfield approach, do attribute sufficient focus and time on change management and training.
With the right preparation, your brownfield migration can be a smooth and strategic step towards a more powerful and future-ready SAP landscape. Interested? Get in touch with our SAP experts!
Chris is here to listen.
Get in touch with him.
Chris is based in Croatia.
