5 ways to Migrate to the Cloud

5 ways to Migrate to the Cloud

Understanding your cloud migration options

We set out the pros and cons of each cloud migration model, helping you to make the right choices before you fly.

Microsoft has a neat way of setting out the options for migrating your workloads or applications to the cloud. There are five migration choices, each memorably beginning with an R: rehostrefactorreviserebuild or replace.

Where migration isn’t a viable option, Microsoft suggests retiring those applications or retaining them on-premise. Peter Wilson, our Head of Technology Consulting Services, describes all seven options here, alongside the pros and cons to help you make the right choices.

What is a Rehost Cloud Migration Model?

A lift and shift approach: move your applications straight to the cloud.

The Pros of a Rehost Cloud Migration Model

  • Speed of migration; but you may pay for this later, see cons below.
  • Supports testing: if anything goes wrong in your new cloud environment, your familiarity with your systems allows you to trace the source of the problem more efficiently.

The Cons of a Rehost Cloud Migration Model

  • Potentially high risk, plus increased costs.
  • Disruption to business services is conceivable. Unless your organisation understands the risks and is willing to tolerate them, the reputation of your IT function could be harmed.
  • The potential for early poor user experiences, may prejudice future engagement.
  • Unless your IT team or managed services provider optimises your new environment soon, you’ll probably waste money on storage and computing power you don’t need. Moreover, until your house is in order, you’ll miss out on efficiency and productivity gains.
  • Requires a Plan B; if any of your workloads malfunction in the cloud, you need contingencies. For example, run your legacy systems in parallel for a time, revise your disaster recovery planning and consider increasing the frequency of your backups.

What is a Refactor Cloud Migration Model?

Shift and retrospectively refit your apps. Move them to the cloud, then tune them to function efficiently in their new environment.

The Pros of a Refactor Cloud Migration Model

  • As Rehost

The Cons of a Refactor Cloud Migration Model

  • As Rehost

What is a Revise Cloud Migration Model?

Before migrating your applications, modify and adapt them as necessary to ensure they function as they should once they’re in the cloud.

The Pros of a Revise Cloud Migration Model

  • Avoids the perils of the rehost and refactor migration models.
  • The cloud migration process is less fraught for your IT team.
  • A planned, pre-tested approach results in better user-experiences and reassures your stakeholders.

The Cons of a Revise Cloud Migration Model

  • Not all your applications may be suitable for their new environment. You could burn time trying to identify a workable solution when the better option is to replace or rebuild them.

What is a Rebuild Cloud Migration Model?

Rearchitect your apps before migration, so they’re wholly cloud compatible.

The Pros of a Rebuild Cloud Migration Model

  • Where you’ve invested time and money in developing custom apps, you’ll continue to realise a return on your investment.
  • For the jewels in your IT estate, this is a good option when keeping your intellectual property and USPs is crucial.
  • Presents the opportunity to engage with your users afresh and make your custom apps even better.

The Cons of a Rebuild Cloud Migration Model

  • Rearchitecting your apps demands time, expense and expertise. For apps that are ten a penny, weigh the effort required to rebuild them vs gain.

What is a Replace Cloud Migration Model?

Say goodbye to your legacy apps and replace them with software delivered as a service (SaaS).

The Pros of a Replace Cloud Migration Model

  • SaaS apps are cloud-native, so compatibility is not a consideration.
  • In a highly competitive marketplace, providers spend vast amounts regularly updating and improving their apps.
  • Allows you to shop around and find the apps that best meet the needs of your business. And if you see something better, switching to another app is relatively straightforward.
  • Application updates, improvements and security are taken care of for you.
  • Replacing your apps avoids the burden of the migration options listed above.

The Cons of a Replace Cloud Migration Model

  • Employee engagement; your users may be emotionally attached to your systems, having depended on them for years. Unless you collaborate with your user-base and manage change thoughtfully, you could encounter resistance.
  • There may be life in your custom-built apps, and you’ll lose future ROI.
  • You’ll have limited to no say in future features of the app you choose, or you may not like the changes the provider implements. That said, you can vote with your feet.

Retiring your Apps or Retaining them On-Premises

Following an audit of your IT estate, you may find some of your apps are no longer used and can be retired.

Alternatively, there’s an argument for keeping them on-premise because:

  • They’re unsuitable for the cloud and too valuable to let go.
  • Recent investment doesn’t justify disrupting the status-quo; you want to continue squeezing ROI from them.

The Pros of Retiring your Apps or Retaining them On-Premises

  • This option enables a phased approach to modernising your workplace. Adopt a hybrid cloud model by migrating what you can now, and retaining elements of your legacy estate where it makes sense.
  • Allows you to consolidate your IT estate by identifying apps that can do the same or a better job, and transferring your workloads to them.
  • A staged transition to the cloud minimises disruption for your users. It also avoids stretching your IT team too thinly or diverting too many resources at once.
  • Quick wins in the cloud can support buy-in for your wholesale move further down the line.

The Cons of Retiring Your Apps or Retaining Them On-Premises

  • Operationally, more complex to manage, e.g. visibility of your estate. Demands a broader IT skillset. We can manage your hybrid cloud for you.
  • A hybrid model could introduce more silos and pose challenges around data integration, which may have a knock-on effect on reporting and analytics.
  • Clunky for your users, who may have to use multiple logins to access what they need.
  • Takes longer to realise the benefits of the cloud, such as simpler operating models, enhanced cybersecurity and better user-experiences.

Would you welcome some strategic and technical guidance on your journey  explore our managed cloud services here

Related Content