Data Migration Strategies in Cloud Computing

Authors:
Aditi Rathi
Saumya Dixit

Affiliation:
IT DEPARTMENT,
Shri Govindram Seksaria Institute of Technology and Science,
Indore, Madhya Pradesh, India.
Contact Email: [email protected]
: [email protected]

Abstract

Introduction
History of the Rs for Cloud Migration
Gartner’s 5 Rs Model
The 5 Rs model, introduced by Gartner, helped organizations navigate the
early challenges of cloud migration. When businesses were starting to
consider moving their legacy applications and data to the cloud, the 5 Rs
provided a clear framework to evaluate different migration strategies.
Over time, this model has been widely embraced and has become a key
tool for planning and executing cloud migration projects. As cloud
technology has advanced, the strategies for migrating workloads have
also evolved, leading to the expanded version known as the "7 Rs." This
evolution reflects the growing complexity and opportunities in cloud
computing, helping organizations choose the best approach for their
needs.
AWS 6 Rs Model
Recognizing the need for a more comprehensive migration framework,
AWS expanded on Gartner's 5 Rs model by adding the sixth R, Retire. This
additional strategy highlights the importance of evaluating the ongoing
value of existing applications and identifying opportunities to
decommission or replace legacy systems with more efficient cloud-based
alternatives.
The 6 Rs model has been embraced by many organizations as a more
complete and flexible approach to cloud migration. It acknowledges that
not all applications are equal and that different strategies may be
appropriate for different workloads and business requirements.
AWS 7 Rs Model
As cloud computing has continued to mature, and organizations have
become more sophisticated in their approach to migration, AWS
introduced the 7 Rs model. This latest iteration of the migration
framework adds the Retain strategy, which recognizes that not all
applications and data can or should be moved to the cloud.
By including the option to retain workloads on-premises, the 7 Rs model
provides organizations with even greater flexibility in their migration
planning. This allows businesses to balance the benefits of cloud
computing with the need to maintain control over critical systems and
comply with regulatory requirements.

Rehost (“Lift and Shift”)

Move applications to the cloud as-is, keeping their structure intact. This
quick approach is ideal for organizations without cloud expertise.
Relocate (“Hypervisor-Level Lift and Shift”)
Migrate server environments to the cloud without changing applications or
hardware. This minimizes downtime and maintains operations seamlessly.

Replatform (“Lift and Reshape”)

Transfer applications to the cloud with some optimizations, enhancing
flexibility without major rewrites or retraining.

Refactor (“Re-architect”)
Redesign applications to fully leverage cloud capabilities. Though
resource-intensive, this strategy future-proofs apps for advanced features.

Repurchase (“Drop and Shop”)

Replace legacy systems with third-party managed services in a SaaS
model, reducing operational overhead and simplifying migration.

Retire
Phase out applications that are no longer needed, paving the way for
more effective cloud solutions.

Retain (“Revisit”)
Keep applications in their current environment when migration isn't
necessary, often due to dependencies or lack of immediate benefit.

When to Use Each Migration Model

Migration Use-case Pros Cons
Strategy

Retire Considered suitable for Requires the least Premature or

redundant workloads investment in unplanned retiring
and legacy cost, time, and of workloads may
applications that are no effort result in
longer in use incompatibility with
Eliminates IT
interconnected
spend on idle
stacks
resources

Retain Best for organizations Helps identify Acts as a deterrence

looking to exercise workloads that to adopt modern,
control over their need immediate cost-effective,
resources and those migration or can secure, and efficient
considering a hybrid be retained and services available in
cloud migration. Also migrated in the the cloud.
suitable for future
applications that are
Reduces cloud
required to run on
wastage by
local data centers for
retaining on-
compliance or security.
prem
inefficiencies in-
house
Helps evaluate
recently
upgraded
services

Relocate Mainly suitable for Quickest Limits the number

applications running migration of cloud-native
on VMware servers strategy capabilities
and local Kubernetes
Requires no PaaS services can be
distributions
change in expensive
operational
Almost impossible
processes for
to scale down
migrated
instances for cost-
savings
 workloads
Reduces data
center
operational costs
Requires minimal
staff training

Rehost For organizations Increased Introduces

looking to expedite reliability and operational and
cloud migration at a resilience without technical
fraction of the cost, costly upgrades incompatibilities,
while looking to affecting user
Enables complete
eventually add further experience
transfer of legacy
changes
workloads Limited number of
cloud-native
Requires minimal
capabilities
risk and
disruption

Replatform For organizations Offers the ability Changes are costly

considering a move to to choose and time-consuming
the cloud but are specific features
May lead to reduced
concerned about the for maximum
application
risks involved in ROI
availability during
comprehensive
No extensive the migration phase
migration of legacy
training required
apps in one go
Enables IT teams
to proactively
monitor the
effectiveness of
cloud-native
capabilities
before migrating
additional
workloads

Repurchase Organizations looking Quick adoption Highly expensive

to leverage cloud- of cloud-native for low-usability
native capabilities capabilities applications due to
 without having to Flexible pay-as- high baseline costs
design systems from you-go model
Updates and
scratch
Provides feature releases are
set upgrades for performed at the
cost benefits vendor’s cadence

Refactor Best for complex Enables Requires thorough

applications with high- organizations to planning, budgeting,
usability and a strong achieve end-to- and execution
business case for end cloud-native
Relies on extensive
performance capabilities of the
staff training and
optimization. Also, well-architected
cloud expertise
suitable for framework
applications that need Requires continuous
Ensures business
refactoring due to monitoring for cost
continuity
changing regulatory optimization
compliance or threat Offers
landscape. Complex to manage
personalized
levels of Not recommended
automation, for migrating a large
scaling, and high number of
availability applications at a
single instance
Conclusion
Cloud migration is a complex process that involves carefully analyzing
current challenges and aligning them with necessary changes to achieve
business goals. The choice of migration strategy depends on factors like
the complexity of the workloads, costs involved, and potential disruptions
to existing systems. Although a successful migration can bring many
benefits, organizations need to consider the risks and ongoing
maintenance efforts required post-migration.