Studies show that debating over “how to cloud” can delay cloud migration plans in up to 66% of organizations. This delay in migration, inevitably costs time, money, resources and a likely delay in delivering new services to the customers, who may eventually leave to look out for other providers.
Based on my prior experience, establishing a vision and roadmap for cloud migration with a clear business direction will increase the probability of success 10-fold. While macro factors like market drivers, risk tolerance and preparation must be considered as part of the roadmap development, other considerations such as software quality and readiness of the application portfolio etc., will further define the success and the pace of your cloud journey.
When migrating to the cloud, specifically with Pivotal Cloud Foundry, it is important to set three main priorities: 1.) Understanding how your applications will behave in the cloud through application portfolio analysis, 2.) Setting a plan to reduce software risk through the migration, and 3.) Benchmarking your success against peers.
Do You Know How Your Applications Will Behave in a Cloud Environment?
The benefits of cloud migration may not be fully realized if the application does not perform as intended in the pivotal cloud environment.
Hence, the first key step in beginning your migration to Pivotal is to assess your application portfolio to discover how much re-architecting will be required to facilitate a fast migration, at the same time, ensuring the applications in question will run as predicted in Pivotal’s environment.
Conducting an application portfolio assessment will help you identify the low-hanging fruit. i.e., the applications that can be moved to Pivotal as-is, in addition to applications with high business impact that will require more hands-on re-architecting to improve performance and reduce risks in production.
Can You Reduce Software Risk in Your Cloud Migration?
Once you have a clear understanding of migration boosters and hurdles from the portfolio assessment, it is equally important to assess the inherent software risk, to estimate the minimum amount of work that would be required to address the technical debt and security vulnerabilities during the migration effort. Please click here to know more on technical debts and how to reduce them.
For example, if you have security vulnerabilities on-prem, they may pose an even bigger risk and be more exposed in the cloud.
What Can You Learn from Peer Organizations?
By benchmarking your cloud migration against peer organizations, you will be able to meet the expectations of C-Suite by achieving the desired business objectives and managing risks effectively.
Join my presentation with CAST on September 27 as we go over many of these lessons learned, along with our recommendations for success with relevant case studies.
If you have any specific questions or would like to discuss more on this topic, please reach out to me at Vijay@cognizant.com.
Disclaimer: The views expressed in this article are completely personal and they do not reflect any organization’s view.