fbpx

Our top 10 tips for migrating to the cloud without the pain

Thinking of moving to the Cloud? Already moved to the Cloud and wish you hadn’t? Here are our top 10 tips for migrating to the cloud without the pain…

  1. Know What ‘The Cloud’ Is

Sounds simple right?  Well, there are a lot of cloud solutions out there, including on-premises Enterprise Cloud, hosted cloud providers, and hyperscale providers such as Microsoft and Amazon.  We see a lot of hosted cloud providers simply providing a co-location hosting server wrapped in a monthly finance package.  Here’s a quick check list to help you to identify an ‘actual’ cloud provider (hint: if you answer ‘No’ to any then you’re probably not looking at a genuine cloud solution):

  • Can I add a single user or virtual instance when I need to scale up?
  • Can I scale down as well as up on a monthly basis?
  • Can I scale up for short periods in response to business demand?
  • Am I actually paying for what I use, with no binding long-term commitment?
  • Can I easily change cloud provider?
  1. Know What You’re Moving

Like any journey, it’s important to know your starting position – it’s the same with a cloud migration journey.  Before considering the financial and operational impacts of moving to the Cloud; you need to fully understand the environment you are looking to migrate.  There can be a lot of ‘gotchas’, such as legacy applications that are unsuitable for the target cloud environment (more on this in number 4 below), or high CPU & GPU load applications that could prove expensive to cloud host.

  1. Consider Hybrid

The term Hybrid Cloud is often used to explain away why an organisation hasn’t fully adopted the Cloud.  To us, it’s a way of describing a phased, managed approach to cloud adoption.

A hybrid approach allows us to provide a solution to our clients that delivers the benefits of cloud computing, where it can by achieved; whilst leveraging on-premises (or co-located) technologies for those elements of an IT infrastructure that, for operational or financial reasons, aren’t quite ready for the cloud.

  1. Remember Your Legacy Apps

Love them or hate them, they’re key to the running of your organisation, and a cloud-based alternative may be too costly, or several years way.

Legacy applications are the single biggest reason that complete cloud adoption cannot be achieved by our clients.  So what do we do about them?  Simple, where possible we’ll move them onto the Microsoft Azure platform, and then publish them back to client devices.  If that doesn’t work due to operating system restrictions, then we can always fall back on on-premises servers (preferably hyper-converged) to deliver them.

  1. Map Your Use Cases

Not all users are created equal, and understanding their specific requirements is the key to building a business case for cloud adoption.  It’s also the key for ensuring that you don’t become the target for a lot of frustrated users if things go wrong.

By mapping out the different categories of users, and their particular IT requirements; we can more accurately predict the correct blend of technologies required, and their associated operational costs.

Finally, and this one is rather important: pilot the chosen technologies to confirm that your business case, and the user experience, is as expected, before committing to a major migration.

  1. Consider The User Experience

Speaking of ‘user experience’ … let’s face it, your users don’t care about scalability, resilience, and cost benefits.  They just want IT to be what we call a “quite enabler”, and they’re going to judge your shiny new cloud solution with their own set of criteria, for example:

  • Is the new environment consistently fast (note the word ‘consistently – it’s an important measure)?
  • ‘Consistent’ should also be applied to the method of accessing the IT environment. They should be able to use the same credentials, in the same way, regardless of how they are accessing the service
  • Can they access all of the applications and data they need, from each location where they are expected to work from?
  • How ‘joined up’ is the overall IT environment? Are there multiple products required to achieve simple tasks, or does it feel sort of ‘joined up’ and ‘effortless’
  • Do they feel that they are ‘fighting’ the cyber security and compliance technologies that you’ve put in place?

We work with clients to start the solution design process with the above list at its heart, not as an afterthought when things don’t go right.

  1. Connectivity is King (get resilient)

Whilst your cloud provider is taking care of the infrastructure resilience (hopefully!); you still need to be able to connect to it to be able to work.

Under investing in broadband connectivity, or not ensuring that the connection is resilient, is the number one cause of outages following a cloud migration.  Good connectivity is cheap (and getting cheaper by the day): please don’t scrimp on this key area – you will regret it.

  1. Automate for a Good Migration Experience

Don’t make your users’ first experience of the new Cloud solution a bad one.  The first time they should realise that they have moved to a new environment is when they are introduced to the cool new features available to them.

Extensive use of migration automation technologies mean that we are able to move clients from their on-premises infrastructure, to the Cloud, with little to no interruption to service; and little o no action required on the users’ parts.

  1. Manage Your Costs

Cost Creep – it’s very easy.  We have just won a new client who is paying for 150 Microsoft 365 licences for their 105 users.  They are also entitled to utilise Academic licences for over half of their users and hadn’t been told of this fact by their incumbent.

Their reason for choosing us as a partner is that they are looking to grow from 105 users, to over 500 users in the next three years.  They want to do so with a partner that is as concerned about their monthly billing, as they are.  A true partner should be working on your behalf to find the optimum licensing and virtual infrastructure instances on a monthly basis.

  1. Innovation Should be BAU

I would describe Microsoft as something of an Innovation Factory.  Although I’m sure many of you would have your own way of describing Microsoft; I’m comfortable with my choice.  According to Microsoft, in 2020 they spent over $17 billion in research and development, and that shows in the both the constant stream of innovations delivered in the last 12 months.

Keeping our partners appraised of Microsoft’s developments has become a full time job for us.  If you’re not constantly being advised of new ways of innovating with your investment in Microsoft, then you might want to consider another Microsoft partner.

We hope that our top 10 tips for migrating to the cloud have provided you with some help and guidance when thinking about your business. If you’d like to speak to a member of our team regarding cloud migration simply fill out the form below and we’ll get in touch as soon as possible.

Want to arrange a call?