Cloud migration has long held the promise of more agility, scalability, and cost efficiency for IT leaders. But if the IT environment is to meet today’s business demands and truly prepare for digital transformation, it must also provide long-term relevancy, resiliency and recovery.
But getting there isn’t always a smooth process. Cloud migrations often take too long, cost too much, run into trouble with compliance requirements, or simply fail to deliver the benefits you were counting on. As with any major initiative, it’s crucial to have a well-designed process in place before you begin.
To confront the challenges and make decisions about what will be migrated to the cloud, when and how, you have to first gain a thorough understanding of your workload attributes by asking the following questions:
Next, it’s important to consider the cumulative impact of these attributes on your workload placement decisions. And that means gathering data to assess your current environment, analyzing options, deciding which applications will require enhancements to ensure they will continue to meet inevitable technology changes without disruption.
To do this right requires more than simply taking inventory. You must not only discover many or most of your assets but capture their business context as well, so you can understand how they support specific business services, and how ready the assets are for migration. Given the rapid rate of change in today’s dynamic digital environments, even the information that does get collected is liable to become out-of-date and quickly become unreliable.
Consider if a new regulation or security measure is rolled out that impacts your industry, how will you know which data and applications need to updated? Can you immediately make changes and have confidence that no application will be missed or that they won’t cause an outage?
Armed with the essential workload data that is linked to building a resilient environment, applications can now be more comprehensively assessed and organized in a number of different ways, and we find these six cloud application migration approaches (first outlined by Gartner back in 2011 and then expanded by Stephen Orban, Head of Enterprise Strategy at AWS) to be the most effective:
|Rehost||Otherwise known as “lift-and-shift”|
|Replatform||Sometimes called “lift-tinker-and-shift”|
|Repurchase||Migrate to a different product/license, often SaaS|
|Refactor||Re-architect or re-imagine leveraging cloud-native capabilities|
|Retire||Get rid of|
And last point, for your cloud migration to yield long-term value for your IT organization, make sure your discovery process captures all of this in an actionable platform. Such a platform not only informs the migration process but serves your need for a new IT environment that is agile enough to withstand changes. Done right, you’ll be able to visualize the complexities of your application relationships and easily identify gaps in resiliency targets and abilities.
IT teams should always be prepared to respond and restore service with accurate and actionable data at their fingertips. From full-fledged disaster recovery plans to addressing other major outages, on-the-fly runbooks can ensure the human and automated tasks enable it all to return to a steady state. The results will enable IT operations to assure their business team counter-parts that they have created an environment that will respond to any changes thrown their way while maintaining long-term relevancy, resiliency and recovery.
A resilient IT environment goes beyond having a disaster recovery plan. Here are 9 tips for improving your IT resiliency.
Read this featured article in IT Briefcase, written by Dave Baker, Managing Consultant at TDS: "As businesses strive to become more agile and implement digital strategies to drive customer engagement and growth, the pace of change–and the associated pressure–has increased.
Happy State Bank in Texas, launched a major initiative to consolidate different databases, refresh their infrastructure and build a resilient IT environment, able to execute a failover plan without risk of disrupting services to customers.
Over the past few years, vendors from across IT have introduced “observability” tools or platforms. But what’s it really mean? And is it enough?
As IT environments continue to come increasingly complex, it is harder for teams to identify all interdependent assets and services that must be moved together to ensure business systems are not disrupted. This post will examine how TransitionManager helps teams get more value from tools they already have by integrating them to work together as a toolchain, and how leveraging automation to accelerate execution so teams can more quickly realize the benefits of cloud by migrating to AWS faster.
As many businesses rush to adopt cloud computing processes, it is not an easy initiative, it can be expensive and the migration process can be a drain on critical IT resources. But companies can keep costs low and make sure their team is working efficiently by implementing some key strategies.