checklist for cloud migration

1. checklist
A few mission-critical insights for
you to avoid common mistakes
and maximize your chances of
a successful cloud migration process
A step-by-step
cloud migration

2. To provide the foundation
for a successful move, you need
to assign a responsible figure
whose areas of responsibility
will include technical decisions,
planning, and execution.
1. Establish the migration
architect role

3. There are two ways you can go about
migrating your application — a “lift
and shift” level with no (or limited)
changes to the servers, or a deeper
integration, where you reconfigure
and modify your application to
leverage the benefits of the cloud.
2. Define the suitable level
of cloud integration

4. Splitting your application(s) across
multiple clouds gives you more flexible
business leverage in terms of pricing
and configurations on one side, but can
also complicate the app development
and validation process with so many
provider capabilities to cover.
3. Choose between a single
cloud provider and multi-cloud

5. Cloud-related KPIs should focus on possible
migration issues and the status
of the migration. Key metrics to consider are
user experience, performance per component,
application infrastructure, and business
engagement. Baselining means defining
KPIs for each of the metrics when the post-
migration performance is acceptable.
4. Establish cloud KPIs
and their baselines

6. Depending on your resource allocation and
deadlines, you can migrate your application to
the cloud on a component-by-component basis
or migrate everything simultaneously. You can
start with the outside services — those that are
closest to your end-users — and move inwards.
Or you can start with the internal services.
5. Prioritize components
to be migrated

7. There are a few reasons why refactoring
matters for cloud migration:
to allow for dynamic scaling, it will positively impact
your future cloud service costs.
to take your resource allocation capabilities to the next
level, ensuring flexibility on demand.
refactoring helps if your solution architecture needs
to be service-oriented.
6. Refactor your application

8. You can use a bidirectional approach to sync
data between your on-premises and cloud
databases. Then, once you’ve moved all
consumers of the data to the cloud, you can
remove the on-premises database. Or you can
switch between the databases when the time is
right. Alternatively, you can opt for a dedicated
cloud data migration service.
7. Come up with a data
migration plan

9. The more complex it is, the slower you
should move. You can either switch
all traffic to the cloud once the entire
application has been transferred and
validated, or test the waters with a small
group of real end-users first.
8. Switch over
the production system

10. A fundamental purpose of moving
to the cloud is to enable dynamic
resource allocation for your enterprise.
Otherwise, the whole migration effort
won’t be cost-effective. With such scaling
in mind, you’ll always be able to handle
any resource demand at short notice.
9. Review application
resource allocation

11. Contact us for more information!
contact@fortegrp.com