Cloud migration involves moving digital assets like applications and databases from a company's on-premise infrastructure to cloud infrastructure. There are several steps to a successful cloud migration including forming a migration team, assessing organizational readiness, choosing a cloud vendor and designing the cloud environment, creating a roadmap, choosing a migration strategy, migrating data, testing, and switching to production. Key risks of cloud migration include cost, loss of control, vendor lock-in, and potential performance issues. People, finances, and legal/compliance issues are also important factors to consider.

2. Cloud Migration
• Cloud migration is defined as the task of moving a company’s digital assets
(applications, databases and other IT resources) to cloud infrastructure either
partially or completely.
• Migration involves transferring these digital assets from a company’s on premise
or old legacy infrastructure to cloud or it can even refer to transferring from one
cloud service provider to another.

3. Why migrate to the cloud?

4. Steps to migrate to the cloud
1. Outline Reason for moving to the cloud
Use an analysis-based approach to determine why you want to move and what objectives you hope to
achieve through the cloud. Build on the reasons for moving to the cloud.
2. Form a cloud Migration Team
Business Analysts, Project managers, IT security specialist, data architect and application specialists
are just some of the people who possess the expertise and skills needed to make informed decisions
as a collective towards cloud solutions.
3. Determine organisational cloud readiness
Conduct a comprehensive business and technical analysis of your current applications, infrastructure
and environment.

5. Follow these steps in your cloud assessments
•Inventory your applications and workloads
•Inventory hardware and infrastructure (servers, databases, and storage)
•Interview application leaders and users to get a sense of how they use the apps
•Draw up dependency maps of your apps and integrations
•Record the technologies used in your application portfolio
•Analyze each app and its relevant components to determine transition plan and place in cloud migration
steps
4. Choose your cloud vendor and design your environment
When designing your cloud environment, your architect should investigate whether a multi-cloud approach
would work for your business.
Also take into consideration:
•Capacity and performance planning right-sized to your needs
•Data classification (Public, Private, Shared)
•Enabling Multi-Factor Authentication (M4A)
•Designing a highly available architecture
•Implementing automation where it makes sense
•Align processes to cloud capabilities
•Set up proper reporting

6. .
5. Create a Cloud Roadmap
Outline which components you want to migrate first based on priority and migration complexity.
Roadmaps help teams stay the course, reduce the chances that elements get missed, and provide a
more accurate timeline as each task is divided into a rough timeframe.
6. Choose a cloud migration strategy
Two common cloud migration strategies usually employed include Rehosting and Refactoring
7. Migrate your Data
Important elements of a data migration plan include auditing data, cleaning up of any identified
concerns, putting controls in place to ensure data quality and ensuring proper governance.
• Data migrations typically involve three basic steps:
1. Extract data
2. Transform data
3. Load data
It is recommended that you back-up your data before starting data migration.

7. 8. Testing and switching to production
Now that your digital assets have been transferred to the cloud its time to run tests before rollout.

8. The six common cloud migration strategies

10. 8. The risks that come with
migration
• If your application stores and retrieves very sensitive data, you might not be
able to maintain it in the cloud. Similarly, compliance requirements could
also limit your choices.
• Cost comparison -Many cloud providers have pricing calculators that can
help you to estimate the real costs you’ll face after a cloud migration vs.
your current costs. The costs may be higher than what you can afford.
• If some of the technology you currently rely on is proprietary, you may not
be legally able to deploy it to the cloud.
• Some operations might suffer from added latency when using cloud
applications over the internet.

11. 8. The risks that come
with migration
• If your hardware is controlled by someone else, you might lose some
transparency and control when debugging performance issues.
• Noisy “neighbours'” can occasionally make themselves “heard” through
shared resources.
• Your particular application design and architecture might not completely
follow distributed cloud architectures, and therefore may require some
amount of modification before moving them to the cloud.
• Cloud platform or vendor lock-in: Once in, it might be difficult to leave or
move between platforms.

12. 9. Who can provide for
your service model?
IaaS: Infrastructure as a Service
• AWS
• Azure
• Google Cloud Platform
• Alibaba Cloud

13. 9. Who can provide for your
service model?
PaaS: Platform as a Service
• AWS Elastic Beanstalk
• Heroku
• Google App Engine
• Engine Yard

14. 9. Who can provide for your
service model?
SaaS: Software as a Service
• Google G Suite
• Office 365
• Salesforce
• NetSuite

15. 10. Factors affecting cloud
migration
• People
People are always a factor, in any project, thus they can be an
issue, or a problem. Cloud migration is no different, it also
depends on people, i.e. the company staff.
Adopting new technologies is always tricky, and you are likely
to deal with this problem if you’re looking to migrate to the
cloud.

16. 10. Factors affecting cloud
migration
• Finance
Cloud adoption is not about large-scale cost savings.
The pay-per-use model of the cloud changes IT spending on
capital investment to operating costs. However, moving to a
PaaS model must be controlled and monitored to prevent
cost overruns.

17. 10. Factors affecting cloud
migration
• Law
Protecting sensitive data is complex, any way you slice it. This
is because firms would rather protect their clients sensitive
data in-house than trusting a cloud service provider. This is
understandable as they have access to their clients sensitive
information.
This protects their interest legally but leaves them wide open
to attack.