Phase 1: Migration Preparation and Business Planning:
Here you determine the right objectives and begin to get an idea of the types of benefits you will see. It starts with some foundational experience and developing a preliminary business case for a migration. This requires taking your objectives into account, along with the age and architecture of your existing applications, and their constraints.
Phase 2: Portfolio Discovery and Planning:
Next, you need to understand your IT portfolio, the dependencies between applications, and begin to consider what types of migration strategies you will need to employ to meet your business case objectives. With the portfolio discovery and migration approach, you are in a good position to build a full business case. If you need help with understanding your IT portfolio, you can work with MPITCloud and use MRADAR Suite platform.
Phase 3 & Phase 4: Designing, Migrating, and Validating Application:
Here the focus moves from the portfolio level to the individual application level and you design, migrate, and validate each application. Each application is designed, migrated, and validated according to one of the six common application strategies. Once you have some foundational experience from migrating a few apps and a plan in place that the organization can get behind - it’s time to accelerate the migration and achieve scale. MPITCloud team depends on MRADAR Suite help accelerate your migration.
1. Rehost (“lift and shift”)
In a large legacy migration scenario where the organization is looking to quickly implement its migration and scale to meet a business case, we find that the majority of applications are rehosted. Most rehosting can be automated with tools such as AWS SMS although you may prefer to do this manually as you learn how to apply your legacy systems to the cloud.
You may also find that applications are easier to re-architect once they are already running in the cloud. This happens partly because your organization will have developed better skills to do so and partly because the hard part - migrating the application, data, and traffic - has already been accomplished.
2. Replatform (“lift, tinker and shift”)
This entails making a few cloud optimizations in order to achieve some tangible benefit without changing the core architecture of the application. For example, you may be looking to reduce the amount of time you spend managing database instances by migrating to a managed relational database service such as Amazon Relational Database Service (RDS), or migrating your application to a fully managed platform like AWS Elastic Beanstalk.
3. Repurchase (“drop and shop”)
This is a decision to move to a different product and likely means your organization is willing to change the existing licensing model you have been using. For workloads that can easily be upgraded to newer versions, this strategy might allow a feature set upgrade and smoother implementation.
4. Refactor / Re-architect
Typically, this is driven by a strong business need to add features, scale, or performance that would otherwise be difficult to achieve in the application’s existing environment. If your organization is looking to boost agility or improve business continuity by moving to a service-oriented architecture (SOA) this strategy may be worth pursuing - even though it is often the most expensive solution.
Identifying IT assets that are no longer useful and can be turned off will help boost your business case and direct your attention towards maintaining the resources that are widely used.
You may want to retain portions of your IT portfolio because there are some applications that you are not ready to migrate and feel more comfortable keeping them on-premises, or you are not ready to prioritize an application that was recently upgraded and then make changes to it again.
Phase 5: Operate:
As applications are migrated, you iterate on your new foundation, turn off old systems, and constantly iterate toward a modern operating model. Your operating model becomes an evergreen set of people, process, and technology that constantly improves as you migrate more applications. We use products like MRADAR Suite, AppDynamics, NewRelic, and Dynatrace that can help you continue to iterate on your operating model as you move more to the cloud.