Moving to the cloud


Make a time to discuss

Yay!  It's time to migrate to the cloud.

Following meticulous planning and risk assessment, migration day (or week) finally arrives.

Each earlier stage of the process has been working toward this day: thinking about the platform that your cloud computing solution will operate on; the comprehensive assessment; the painstaking design; the careful consideration that goes into each individual component and service that will move to the cloud.

Making IT Easy

The entire process is geared toward ensuring implementation is carried out with as much ease and as little interruption to business as possible.

Downtime isn't always inevitable, although it is certainly a challenge to avoid any outage to service when migrating to the cloud.

Our approach is to minimise the impact as much as feasibly possible, although there is a greater focus on ensuring migration works right first time and results in zero data loss or compromise, as these goals tend to be of greater importance to clients.


During the assessment and design stages of the ‘moving to the cloud’ work-flow, we will often have identified multiple business solutions that we recommend could or should be moved to the cloud in order to realise real, concrete business benefits.

It would be foolish to try to move each component to the cloud at once: from not only a logistics perspective but also a risk management standpoint.  Slow and steady wins the race.

Instead, cloud migration usually entails:

  1. Configuration, testing and enabling a client’s cloud architecture or environment (where a custom cloud environment is to be delivered)
  2. Implementing a staged migration of each individual service or functionality, using a controlled, procedure-driven methodology that encompasses thorough acceptance testing and rollback opportunities


Email is possibly the most common service we will move to the cloud for our clients on migration day.

Office 365 offers dramatic scalability and cost benefits to many businesses still using traditional on-site email servers, meaning we’ve become past masters at migrating to Microsoft’s flagship cloud email service (in addition to other cloud email providers), from a range of legacy mail solutions.

Our method for migrating email to the cloud might differ in small ways from client to client but fundamentally, the high-level process we follow is along the following lines:

  1. Firstly, we implement the designated email solution in our client’s new cloud architecture
  2. Next, we commence synchronisation of all mail (plus any calendar and contact functionality) from the pre-existing on-site email server to the new cloud email system
  3. We then make a live switch, so that all incoming mail routes via the new cloud email platform, meaning users will slowly start to use the new solution to collect and send their mail.  This will not happen for all users instantaneously, as it takes time for DNS records to propagate throughout the internet. Remote users, for example, may continue to use the old email server via their traditional means
  4. The synchronisation from an old email server to the new cloud email servers continues indefinitely, so any mail received/sent via the legacy solution is replicated over to the new cloud email servers (ensuring no mail goes missing during the process).  We keep this synchronisation running for several days after migration, to be on the safe side
  5. Only when we’re confident that mail has ceased to arrive or send via the legacy email solution do we turn off and decommission the legacy email server

The migration process for moving email delivery to a cloud solution is actually remarkably similar to how a change to a traditional mail delivery route might have been handled, 100 years ago or more.

Consider a new railway track, built to facilitate a new post house for receiving mail.

While the railway line and post-house itself is under construction, mail continues to be delivered via the existing rail infrastructure.  Once the new post-house is open for business (receiving mail), the new railway siding is opened up for delivery by rail.

However, not all the train drivers have been debriefed, and some continue to use the old route, in the short-term.

Any mail delivered to the old post-house needs to be ported manually over to the new post-house, for a short while, to ensure delivery is not impacted.  After a week, it becomes clear that mail is no longer arriving at the old location, so the old post-house no longer needs to be staffed, and can close down.


Following each stage of a client’s migration to the cloud, stringent acceptance testing is carried out to assess the expected functionality is fully serviceable.

Our migration consultants then remain on-site to ensure that your workforce is given comprehensive user training in how to use any new or replacement software that has been introduced.

Similarly, staff are made aware of any required changes to their workflow that might be necessary due to version updates or differences in how a particular program operates following migration to the cloud.

1-to-1 training sessions can be provided for specialist personnel and employees with learning difficulties, to aid the transition.

We recognise that technology improvements are useless if you feel lost or out of your depth using the tools at your disposal, and are happy to take the time to thoroughly train users and answer any questions they may have.