A successful cloud migration enhances the business by enabling agility; organisations can become more responsive to varying needs, and innovation bottlenecks are removed. A recent SAP business that we have migrated to Microsoft Azure is a great example of what can be achieved, offering the company the following benefits:
For supply chain and operationally intense businesses, these benefits can play an even greater part; creating resilience against the unique landscape performance demands of these types of environments, such as:
Getting this right will ensure that your supply chain and operations can perform consistently, continue to meet customer service levels, and protect the profitability of your business.
In this blog, you will learn how we achieve this for the SAP landscape and the advantages a cloud-based SAP landscape can provide to your business.
Rocket Technical Services: Building and running high-performance SAP environments for supply chain and operationally intensive businesses
Having established some of the essential benefits of moving to the cloud, for many businesses, the critical question is not why, but when.
When to move to the Cloud?
For new SAP landscapes, there will be a compelling case for going straight onto the cloud, avoiding large capital expenditures (CAPEX) in favour of a balance sheet friendly Operating Expenditure (OPEX).
So why invest in moving existing landscapes? Reducing the costs of running and maintaining an on-premises system is the biggest driver for many migrations.
Where your existing on-premises or hosted hardware estate is performing well and meeting your needs, it can be harder to build a business case for moving to the cloud despite the benefits. However, tying the move in with other pivotal events quickly helps the budget stack up favourably.
Of course, the move to the cloud does not need to be an all-or-nothing approach. An incremental hybrid approach can work well alongside existing infrastructure and systems. Introduction of new decentralised platforms in the cloud, working with existing on-premises systems, for example, many businesses are running SAP Business Suite (SAP ECC) and introducing new digital supply chain platforms such as SAP S/4 EWM and SAP S/4 TM on the cloud, often in advance of a move to SAP S/4HANA.
Regardless of the reason for a migration to the cloud or, indeed, any business system project, a crucial consideration is the cutover window available; that is, the period the business can plan to be without their business systems to allow the changes to the landscape to be implemented into the production environment.
Migrations are incredibly challenging for all parties involved and require careful planning to ensure all the necessary steps and processes are accounted for and can be completed within the time-sensitive cutover window.
Key points to consider:
Once the duration of the cutover window is established, assessing what can or can’t be performed in the available time or how different approaches to activities could utilise the available time is essential. A short versus a long cutover window will require differing approaches.
When dealing with a short time window for a migration, we recommend using a technique that allows shorter cutover times.
A homogeneous system copy method can be used in this instance; a ‘like for like’ copy that means all components (Operating System, DB etc.) are the same in the new system as the source system. This allows other time-saving techniques to be used to prepare and align the current and new landscape in advance of the cutover; for example, we can ship the logs from the old database to the new database and apply them each day leading up to the cutover.
Where virtual machines are already in use, additional tools are available to speed up and automate aspects of the cutover, again saving crucial time.
Where a long cutover window is available, more complex migrations can be accommodated, resulting in a change to the landscape in a heterogenous cutover.
This approach combines migration or modernisation steps, reducing overall effort but adding more potential risk to the project that must be offset with corresponding regression testing.
Designing and building your SAP cloud landscape, whether for a new SAP S/4HANA landscape or a migration of an existing landscape, requires a structured approach and a broad range of experts from your IT and business team.
We deploy the Launch SAP Cloud with Rocket methodology, an overview of which is provided below to help you plan and execute a cloud build of your SAP S/4HANA landscape or the move of your existing SAP landscape.
Preparation is essential!
Involving the business users and data experts in the process is the single biggest factor behind a successful migration. Assessment workshops can be used to clearly define the needs and carry out a comprehensive assessment of the available resources to describe a clear direction to achieve the business and IT goals across the full range of topics that should be addressed, including:
After the assessment workshops, the team must determine the hardware and software available to the migration project; these specific activities would include:
Having the right resources available for the migration is critical to the project’s success; we would expect these key roles/personnel.
Only once this is established can we start to think about the migration. The planning for each migration may take a different path but will use the same methodology. The most important aspect of any migration is repeatability; without this, you cannot be certain the migration will be a success. Completing a dry run of the migration will always bring confidence to the stakeholders that the process is working and is repeatable.
What does this mean for my partner selection?
Building high-performance landscapes in the cloud to support the demands of the intelligent enterprise with SAP S/4 or the unique needs of supply chain and digital operations necessitates a holistic architecture design across:
When selecting a partner to work with on your move to the cloud, ensure they can bring together in-house expertise and the necessary certifications across these skill sets.
SAP system migrations are notoriously challenging due to the potential impact that must be mitigated and the cutover window constraints. There are often multiple systems and many interfaces to other internal and external systems, so coordination and communication are essential.
In a recent system landscape transformation, we migrated 7 SAP systems in one single weekend, with users arriving back at their workstations on Monday oblivious to the relocation of the SAP landscape.
If you are considering embarking on an infrastructure change or just modernising your IT landscape, contact Rocket. We will be happy to help you plan and migrate your landscape successfully.
< Back to all Partner news
Our latest insights and thoughts