- To ensure an effective and successful migration
to the cloud, you need to create a detailed plan.
The time you invest in working up a plan
and defining needed resources will provide savings
in the latter portions of the project.
And know that you will learn as you go.
For most, this will be the first time navigating
a cloud migration, so don't be afraid to make mistakes
and forgive those who do as well.
These seven steps are a great guide to planning steps
to your migration.
Replace, means that we're replacing the software
with a software as a service system or solution.
Reuse, means that we're dividing up the application
as sets of services and then leveraging those services
for one or another application.
Refactoring means that we're altering the application
to be more cloud native and thus more efficient.
Replatform, means that we're placing the application
on a different cloud platform
than the traditional system of origin.
Rehost, means that we're lifting and shifting
which means that we're moving the application to the cloud
without modification.
Retain, means that we're not moving the application.
Retire means that we remove the application
completely from service.
Estimated application migration resource levels
can be difficult to measure at first.
This means that you need to understand how much is going
into migration relative to the value
that cloud computing may bring.
You need to consider the cost of people, resources,
and the time it will take to migrate your applications
to the cloud.
However, you must consider the value over time
relative to the resources expended.
It's an imperative that the value exceed
the investment over time else it does not make sense
for you to move to the cloud.
Determined business drivers is part of the process
of moving to the cloud and it should always be an objective
to have those drivers in mind as you plan the project.
A few helpful hints include, understand data, services,
business processes and system integration points,
they need to be a part of this process as well,
and if they are neglected
you won't have a complete solution.
This is where the majority of work comes in.
Determine an integration strategy for internal
and external systems or how the data will be shared.
It's often overlooked and has to be redone.
Keep in mind that these are much more difficult to deploy
without planning.
Outline a migration path for legacy systems
to the new architecture.
Some may move some may not.
You need to add the ones that move to the plan
as well as determine the value.
You follow the steps outlined here,
you'll get cloud migration right the very first time.