Cloud technologies are at the center of the digital transformation. The cloud has changed more than just the way we implement and manage IT; it’s changing the very fabric of business. It’s a fundamental shift from the way traditional enterprise infrastructure and technology resources are procured, utilized and managed.
While the notion of starting from where you are today, is simplistic, it’s often a significant stumbling block on the journey to the Cloud. It’s surprising how many enterprise customers feel that they have a good understanding and documentation of their IT infrastructure, but really don’t. Technology creep can create a false sense of governance.
Equate it to living in a house for 20 years and getting ready to move. You find things at the top of your closet, in the garage or in the basement that you haven’t seen in years. IT systems which are not top of mind surface in a similar pattern. Projects, teams, or applications that were never used, never fully decommissioned or resulted from mergers or acquisitions must be addressed as part of the cloud journey. The architecture of these systems can play a significant part in understanding how the migration will be executed.
It is essential to start with a true picture of the current environment to develop a clear, realistic and optimized journey map as you design your Cloud migration.
Not all applications, systems and data are equal when it comes to Cloud migration planning. There are some key considerations to what gets migrated, what does not and how they are prioritized. A complete ‘Lift and Shift’ is often the smaller percentage in the end and more often, a hybrid approach must be taken for migration.
Current state mapping kicks off with a discovery stage during which everything in the business and IT environment is evaluated against four critical factors – effort, impact, time and cost. These will help you prioritize your migration plan tasks into required, essential and optional. Mitigating considerations against these are constraints regarding the state of technology, technology tools, resource availability and resource capabilities. This helps determine the appropriate migration approach for your organization.
So now what about your data. Similarly, the data that resides in these applications and systems is sometimes worthwhile to migrate and sometimes not. Data and Estate modernization planning needs to be part of your overall migration and Cloud foundation planning approach and roadmap. Looking at data archival, data accessibility and live data needs will help you formulate your data needs for the Cloud.
The development of Cloud journey maps from current to future state will provide your business with needed visibility and transparency across the Cloud environment to have an efficient and optimum migration.
In the end you can’t know where to go until you understand where you have been and where you are.
Network Engineer & Cloud Architect