Why is Cloud Assessment important?
In my previous blog, I had elaborated on the four important pillars of SAP Cloud services.
- Assessment : This helps customers define their ability to move to the cloud, the sequencing of the migration and the execution
- Migration : Cloud migrations need care and attention to detail; without a solid foundation in SAP and cloud, you risk your migration
- CloudOps : Running Application Management Services on Cloud is not the same as on-premise: The team needs to understand how to operate in a SAP landscape with the dynamicity of cloud environments
- Accelerators : Tools which can help customers accelerate their cloud migration journey
In this blog, I am going to touch upon the most important aspect of the SAP on Cloud migration strategy, which is Cloud Assessment.
This blog will help you to find answers to these questions.
Data speaks for itself: Here is an eye-popping fact where Wasted cloud spend is a significant issue, becoming more critical as cloud cost continues to rise.
Cloud assessment is a systematic process that ensures an organization’s readiness to move its on-premise landscape to cloud. This covers in-depth analysis of the existing applications to highlight a roadmap between existing and to-be architecture. A gap analysis provides customers a list of applications that can be migrated to the cloud smoothly as per SAP’s best practices and with a futuristic roadmap.
Cloud assessment approach
- Objective of the cloud migration -: An organization needs to combine the business context of each application with the technology components. Therefore, it’s very important to set the following expectations at the beginning for the migration.
- Current Application, Servers, Databases and Storage List : Managing the application portfolio of the current overall landscape is quite important so that we can list down the dependencies before migrating to cloud.
- Alignment with Business/ Application stakeholders : The key for any business is always to make sure that BAU runs smoothly. The most important part is alignment and discussion with the application stakeholders to define and refine the future roadmap.
- 1:1 1:many mapping of Applications : Based on the information collected from the business and the technology sources, categorize each application for one of the following: Re-Host, Re-Platform or Re-Architecture. This decision should be in alignment with SAP best practices and future road map.
- Like for Like SAP migration to Azure
- Candidate systems deemed to stay on a specific platform
- SAP Homogeneous System Copy
- Windows to Windows
- Hana to HANA
- MAXDB to MAXDB
- SQL to SQL
- OS and/or database porting (changing OS or database type - Cross- Platform)
- Minimal or No SAP Upgrades
- SAP Heterogeneous System Copy
- Any DB to HANA or ASE
- Oracle to Oracle as OS will change from Suse Linux to Oracle Linux
- Application architecture changes
- Multiple pre-requisites and transformations
- Single or multiple phased
- Complex downtime minimized tool usage
- Hybrid methods and techniques
- Split JAVA stack
- Unicode Conversion
- EHP Upgrades
- Near Zero Downtime Migrations
- Group applications together : The key output of the whole exercise is to group all the applications with respect to their dependencies, business criticalities etc. before moving them to cloud, as this will give us the opportunity to consolidate the applications, if any, based on SAP best practices.
Here, I end this part of my blog. I hope you find it informative. Until the next blog, keep learning and shining.