Cloud migration involves moving data, applications, and workloads from on-premise infrastructure to cloud services delivered over the internet. There are three major cloud models - SaaS, PaaS, and IaaS - that each provide different levels of control and flexibility. Successful cloud migration requires identifying stakeholders, assessing costs and benefits, addressing legal and security risks, and choosing an appropriate migration approach like rehosting or replatforming applications. Careful planning is needed to ensure a smooth transition to the cloud.

1. CLOUD MIGRATION
An overview of cloud migration

2. WHAT IS CLOUD MIGRATION?
Cloud migration is the process of moving
all or parts of a company’s data,
applications and workloads from on-site
premises to a cloud infrastructure where
the information can be provided over the
internet on an on-demand basis

3. CLOUD MIGRATION CONTINUED…
Migration may involve one or more clouds. Some clouds are public, whereby
services are delivered over the public internet, and some clouds are private,
consisting of secure cloud infrastructure available only to a specific
organization.
Cloud migration has many benefits and companies must ensure that they make
the right choice when choosing their preferred cloud service model. It should
be one that meets their business needs, creates a competitive advantage and
has a good return on investment. There are the 3 major cloud models
companies can choose from; Saas, PaaS and IaaS.

4. SOFTWARE AS A SERVICE
 Also known as Cloud application services or just
SaaS, is the largest cloud market and are still
growing at a fast rate.
 SaaS uses the web to deliver applications that
are managed by a third-party vendor and
whose interfaces is accessed on the clients’
side.
 SaaS applications are delivered and ran directly
from a web browser without any downloads or
installations required (some require plugins)
and are available with a pay-as-you-go pricing
model.

5. SOFTWARE AS A SERVICE
Managed by user
 Not applicable
Managed by vendor
 Hosted applications
 Development and management tools
 Operating system
 Servers and storage
 Networking resources
 Data center
Perfect for end users

6. PLATFORM AS A SERVICE  PaaS refers to cloud platforms that provide runtime
environments for developing, testing, and managing
applications.
 With PaaS solutions, software developers can deploy
applications, from simple to sophisticated, without
needing all the related infrastructure (servers,
databases, operating systems, development tools, etc)
 PaaS vendors supply a complete infrastructure for
application development, while developers are in
charge of the code. Developers, however, manage the
applications.
 Just like SaaS, Platform as a Service solutions are
available with a pay-as-you-go pricing model

7. PLATFORM AS A SERVICE
Managed by user
 Hosted applications
Managed by vendor
 Servers and storage
 Networking resources
 Data center
 Development and management tools
 Operating system
Perfect for software developers

8. INFRASTRUCTURE AS A SERVICE
 Infrastructure as a Service or Cloud infrastructure
services is a cloud service model that provides
basic computing infrastructure.
 They are self-service models and are used to
access, monitor, and manage remote data center
infrastructures such as servers, storage, and
networking services .
 Like SaaS and PaaS, IaaS services are available on a
pay-for-what-you-use model. Instead of
consumers having to purchase hardware outright,
users pay for IaaS based on their consumption,
similar to electricity and other utility billing.

9. INFRASTRUCTURE AS A SERVICE
Managed by user
 Hosted applications
 Development and management tools
 Operating system
Managed by vendor
 Servers and storage
 Networking resources
 Data center
Perfect for IT administrators

10. CLOUD MIGRATION STAKEHOLDERS: INTERNAL
INTERNAL STAKEHOLDERS
• IT Organisation - Defines the scope
• Executive sponsor (CTO/CIO/Head of IT department) – an accessible executive with the vision
to lead a culture shift within the organization. They must have the baseline knowledge of
cloud and it’s benefits.
• Project Manager – provides key performance indicators (KPIs) for areas such as cost
avoidance, operational resilience, and workforce productivity. They must have a solid
understanding of how tech fits into the larger company strategy.
• Solutions architect - An IT pro and engineer who’s a team player with cloud migration
experience, including certifications for architecting or developing solutions with cloud
providers.

11. CLOUD MIGRATION STAKEHOLDERS: INTERNAL CONTINUED…
INTERNAL STAKEHOLDERS
• System administrator - An IT pro with strong knowledge of virtual machines and cloud
networking – as well as development and deployment on IaaS and PaaS. They must
understand cloud fundamentals and be able to recognize the pitfalls of mismanaging cloud
resources.
• Cloud security manager - A cloud practitioner certified in cloud security management who
understands the division of responsibility for designing and maintaining a secure cloud
environment. They must have a strong communication skills and knowledgeable about
potential vulnerabilities of virtual machines.
• Compliance specialist - A privacy professional certified in cloud security management who
can help internal teams develop privacy-respecting policies and processes.

12. CLOUD MIGRATION STAKEHOLDERS: EXTERNAL
EXTERNAL STAKEHOLDERS
• Cloud Service Provider - Ensures service consistency and that the project is executed such
that the cloud services delivered to the organisation are highly available, consistently reliable,
resilient and recoverable.
• Systems Integrators and Consultancy - Shares expert perspective and guidance. They draw
on experience across the cloud services landscape to identify the tools, processes, people
and practices that are most appropriate to the organisation’s objectives.
• Systems and Software Vendors - Ensures technology. They ensure that the technologies
provided for the project are appropriate to the organisation’s requirements and that issues
with those technologies are resolved completely.

13. FINANCES: COSTS
• Costs
Calculating costs is one of the most
challenging aspects of cloud migration. There
is a tendency of underestimating the
expenses incurred by the full process which
often leads to project failure.
Financial planning is critical to successful
cloud migration. When setting a budget, it's
important to factor in current costs
associated with the workloads being moved
as well as the post-migration costs of running
them in the cloud.
Proper budget planning helps create clearly
defined project goals and with setting a
realistic timeline for migration.

14. FINANCE: COSTS CONTINUED 1…
PRE-MIGRATION COSTS
Audit current IT infrastructure
Direct costs: these are found on the balance sheet and include software and hardware.
e.g. physical servers, software licenses, maintenance contracts, warranties, supplies, material, spare
parts
• Cost of labour for maintenance of your servers, databases and other technology.
• Cost to maintain the facilities that house IT hardware, such as real estate, staffing, and other
facilities-related costs.
• Cost of connectivity to the internet and other network costs.
Indirect costs: these costs are not easy to estimate but it is important to consider them
e.g. the loss of productivity suffered by your employees and customers if your IT infrastructure goes
down.

15. FINANCE: COSTS CONTINUED 2…
MIGRATION COSTS
Migration costs are the costs involved in executing the migration of your IT operations to the cloud.
#1. Moving data to the cloud
This accounts for fees charged by Cloud providers for transferring data to their systems. It also includes
costs of labour involved in ensuring that the data of a company is synchronized properly when it is moved
from the legacy system t o the cloud.
#2. Integration and testing of apps
Sometimes some applications are just not ready for the cloud. It could be something like a large system
with features and functionality that depends on on-premise servers. This then adds to the costs of
integrating and testing these apps after moving them to the cloud.
#3. Consultations
Companies may not have all the skills and resources necessary to execute a cloud migration on your own. They
may need outside expertise and experience t o assist. An outsider ’s point of view can be helpful on a number of
fronts.
Consultation costs can include; mapping a strategic approach, developing a cloud architecture, executing the
migration process etc.

16. FINANCE: COSTS CONTINUED 3…
POST-MIGRATION COSTS
This accounts for all the costs that arise after the migration process.
Costs such as continued integration and testing of apps, training, labour, security and
compliance, administration etc.

17. FINANCE: BENEFITS
BENEFITS
A key benefit of cloud computing is the realization of hard cost savings, but these softer benefits
are also strong reason to consider a move to the cloud.
Examples of cost cutting benefits:
• Data center termination or reduction (environmental costs)
• Reduction in power consumed (environmental costs)
• Rack termination (physical asset recovery)
• Hardware refresh avoidance (cost avoidance)
• Software renewal avoidance (operational cost reduction or cost a voidance)
• Vendor consolidation (operational cost reduction and potential soft-cost reduction)

18. LEGAL AND RISK ISSUES
Moving to the cloud may seem like a no-brainer for most business owners. Cost cuts on
infrastructures like servers and IT specialists services may sound great but there are several legal
and risk issues that need t o be considered before moving to the cloud.
#1 Customers have reduced control and visibility.
When migrating data to cloud platforms, organizations lose some control and visibility over their
data/assets. When utilizing external cloud ser vices, the responsibility for some of the policies
and infrastructure belongs to the cloud ser vice provider

19. LEGAL AND RISK ISSUES CONTINUED 1…
#2 Incomplete deletion of data.
Threats linked with the deletion of data exist because the consumer has r educed visibility int o where their data
is physically stored in the cloud and a r educed ability to verify the secure deletion of their data.
#3 Stolen Credentials (privacy)
If an attacker gets access to the credentials of a cloud user, then they can also get access to the cloud ser vice
provider’s services to provision additional resources (if credentials allowed access to provisioning), as well as
target the organization's data for malicious intent.
#4 Vendor Lock-In as a barrier to Moving to other cloud service providers
Vendor lock-in can become an issue if customers intend on moving its data from one cloud service provider to
another. The risk is high when there isn't a full understanding and agreement of termination rights and
termination assistance.
#5 Increased Complexity for IT professionals
Migrating to the cloud can introduce complexity int o IT operations. Managing, integrating, and operating in the
cloud may require that the organization's existing IT staff learn a new model.

20. LEGAL AND RISK ISSUES CONTINUED 2…
#6 Insiders Abuse Authorized Access (privacy)
Insiders, such as staff and administrators for both organizations and cloud ser vice provider's, who abuse their
authorized access to the organization's or cloud service provider's networks, systems, and data are uniquely
positioned to cause damage or exfiltrate information.
#7 Loss of stored data (security warranties)
Data stored in the cloud can be lost for reasons other than malicious attacks. Accidental deletion of data b y the
cloud service provider or a physical catastrophe, such as a fire or earthquake, can lead to the permanent loss of
customer data.
#8 Insufficient Due Diligence Increases Cybersecurity Risk
Organizations migrating to the cloud tend t o make the mistake of not performing sufficient due diligence. Data
is moved to the cloud without fully understanding the risks of doing so. Organizations don't consider the security
measures used by the cloud service provider, and their own responsibility to provide security measures.
Other issues include: ownership of data, uptime, service availability, performance levels, data security and breach
notification requirements, remedies for breach of the contract

21. MIGRATION APPROACHES
Approaches
The 6 most common application migration strategies:
#1 Rehosting
Also known as a “lift and shift” approach. This means you are redeploying your existing
application to an IaaS environment.
#2 Replatforming
Involves upgrading an application from its existing platform and get it to run on the cloud, while
preserving existing functionality.
#3 Repurchasing
This is a move from on-premises solution to a SaaS platform. It runs outside of your
infrastructure and is maintained by a third party. It eliminates the need for maintenance or
updates.

22. MIGRATION APPROACHES CONTINUED…
#4 Refactoring/ Rearchitecting
Refactoring means rebuilding your applications from scratch. This is usually driven by a business
need to leverage cloud capabilities that are not available in their existing environment.
#5 Retiring
Once you have assessed your application portfolio for cloud readiness, you might find some
applications are no longer useful and need to be turned off. This then directs the team’s cloud
migration strategy to areas that are most critical to the business.
#6 Retaining
In some instances, cloud adoption does not y et make sense. Or maybe some applications
cannot be integrated to the cloud just yet. In such cases, organizations should only migrate
what makes sense for your business and what' s suited for the cloud.
.