It is critical to understand your business’ strategic business and financial drivers before purchasing any cloud service, in order to define the appropriate deployment and sourcing model.
What are your IT and business goals? What are the associated enterprise architecture guidelines and preferred commercial models? Have you considered your capital expenditure (CapEx) versus operating expenditure (OpEx) needs?
(Read more about the benefits of shifting your IT spending from CapEx to OpEx here)
It is important to note that, while the ability to reduce upfront investment by shifting IT spending to monthly fees is a draw card of moving to the cloud, it shouldn’t be the only business driver. The true business value of the OpEx model is more about agility and utilisation than cost consideration. You need to ensure you can scale your IT resources up and down according to the business’ needs.
Step 1 – Setting a migration timeline
Setting a cloud migration timeline depends largely on the maturity of your current IT operations.
Sometimes businesses with a mature in-house IT department wait until IT infrastructure is due for updating as the trigger to engage in a large cloud migration project. However, smaller businesses without complex on-premises IT infrastructure could benefit from a more immediate migration.
“If you don’t have a large IT department, it doesn’t make sense to try to hire a guy who knows storage, a guy who knows network and so on,” Peoples says. “Trying to run it all on-premises is not as cost effective as migrating to a managed private cloud.”
Step 2 – Assess the suitability of applications
Conduct a thorough inventory of your existing application portfolio. This will identify any potential constraints and establish the right deployment model across private, hybrid, or public cloud.
Your IT team should assess each application or workload on a case-by-case basis to determine the best fit, based on cost and performance requirements. While newer software applications tend to experience few compatibility issues, some of your older legacy applications may not migrate as easily, and you may need to reconfigure them to connect to your new cloud infrastructure services.
Step 3 – An opportune time to rethink business processes