Some systems are born for moving to cloud, like certain customer relationship management (CRM) or project management tools. Other software and processes, however, are too demanding to move to the cloud. That doesn’t mean an organisation should abandon moving to cloud. Some organisations have found good reason to elect a hybrid cloud set-up where some workloads are moved to the cloud and others are managed in-house.
Good systems are already in place
When the infrastructure to host vast amounts of operational data — sometimes sensitive operational data — is already live, keeping that information and technology in-house is advantageous. If you already have the expertise and the processes that work, it might not justify moving to cloud. Some organisations, for example, may find solutions in the cloud that can analyse and access that in-house data.
There’s the ability to mix-and-match
Your infrastructure may not be able to handle a new or expanding need within your organisation. Because that technology is a sunk cost, in many instances, it makes the most sense to augment, not abandon, existing infrastructure. You can justify moving to cloud for some applications and not others. Cloud services providers like Datacom can guide organisations in which applications to keep on premises and which would be suitable in a private cloud environment.
Moving to the cloud might result in non-compliance
Some data, whether by Australian law or various accreditation boards, can’t be stored in the cloud. In certain instances, meeting compliance requirements in moving to cloud is so arduous the already-compliant in-house solution is worth maintaining. And as compliance standards inevitably change, being able to adjust technologies and processes in-house with your expert staff may trump the advantages of the cloud.
As you contemplate moving to cloud, consider these questions:
Is your staff qualified to design and support the solution? If the experts are in-house, keeping everything within your four walls may be your best bet over moving to the cloud. On the other hand, if the architecture or system is out of their purview, you can forego extensive training and continuing education by letting them handle the aspects within their realms and turning to the cloud for the remainder.
What is your current architecture? When it comes to the systems in place, does your project demand more than your current in-house capabilities such as demand variability, high availability, response times and security requirements? Just because a new project exceeds current architecture doesn’t make the case for moving everything to the cloud. Keeping current processes in-house while moving a new process to the cloud might be the optimal solution.
What integration challenges accompany moving to cloud? Will moving to cloud lead to onerous integration issues? Ultimately, you’ll need to conduct a thorough cost-benefit analysis to see if this point is a make or break between moving everything to the cloud or leaving a portion in-house.
Moving to cloud should be justified with a full business case. Working with a qualified IT provider concerned with the best solution can provide great insight. And always remember the priority is what’s best for your business, even if it means not moving to the cloud.