How to Think Through the Costs Associated with a Cloud Migration
The federal government’s shift to the cloud over the past decade has resulted in significant benefits, such as the deployment of modern digital services and the ability to scale up computing resources to meet mission needs. The cloud has enabled many agencies to rapidly expand the use of collaboration tools to support remote workers during the coronavirus pandemic.
Despite the benefits of cloud, there are still many costs associated with migrations that IT leaders may be overlooking. There may be confusion over different cloud models, what resources are actually going to be needed to support different applications and how much they expect the use of cloud services to grow over the medium to long term. Additionally, security and compliance costs and considerations need to be taken into account.
That is why it is critically important for IT leaders and those involved in cloud migration to conduct thorough cost analyses of such migrations. Without performing such work, agencies could wind up misjudging how much and what kind of cloud resources they need, which can lead to higher costs and lost time.
There are clear guidelines IT leaders should follow when approaching cloud migration costs. First, however, they need to know what they may be overlooking.
READ MORE: Find out how to effectively plan for a hybrid cloud environment.
The Overlooked Costs of Cloud Migrations
One of the biggest issues is that some IT leaders still do not fully understand the fundamental differences between Software as a Service, Infrastructure as a Service and Platform as a Service.
There are also differences in pay-as-you-go and reserve models of Compute as a Service. In a reserve model, an agency would not save money by scaling up or scaling down computing resources.
Cloud can be cheaper for agencies if there are services that can be run in a shared cloud environment as opposed to an on-premises data center. However, the more secure applications or data need to be, the more costly running a cloud service can become. Agencies need to comply with standards set out by the National Institute of Standards and Technology, or from the Defense Department and other governing bodies.
It’s important to remember that a cloud service provider will provide a foundational level of security for its cloud environment, but the vast majority of cloud security falls on the agencies. IT leaders need secure their own apps and data.
Even adopting managed services does not obviate all of the costs associated with a cloud migration, since agencies would still need to pay for a cloud service-level agreement, which can lead to other costs in the long term.
There are other costs to consider as well. Does your agency need redundancy capabilities? How much caching will be needed? How many load balancers? Critically, IT leaders need to think about how much their use of cloud services will grow over the next five years. Leaders need to plan for that growth, since under provisioning at the start of a migration may end up costing the more in the end.
MORE FROM FEDTECH: Find out how the SBA, CBP and USTDA turn to the cloud to keep work flowing.
How Cloud Migration Costs Can Be Analyzed
To get a better estimate of cloud migration costs, IT leaders need to draw out a proper picture or storyboard of their cloud growth, either internally or with trusted partners.
The storyboarding needs to focus on an agency’s current cloud needs as well as the expected growth in cloud services. Typically, agencies upgrade most of their IT every three to five years, so IT leaders may be inclined to think about cloud costs being fixed during that three- to five-year window. However, cloud models do not work that way,
Cloud is constantly changing. Software insurance costs may go up. New spikes in demand may come, as was the case when agencies shifted to massive telework deployments this spring.
Digging into that scenario, let’s say agencies are deploying virtual desktop infrastructure for their users via the cloud. Should they deploy that VDI setup for eight or nine hours per day to avoid paying for 24 hours of costs? They can, but they will need to get users into the mindset that they do not have physical desktops that can be accessed at any time of day. Do they need the entire infrastructure or just access to one application?
So, agencies need to define what they are going to do and how they are going to do it. Agencies also need to analyze the compliance costs associated with the mandates they need to meet and the risks they are willing to accept.
If agencies do not accurately estimate their cloud costs and what they will need in terms of cloud resources, they will wind up sizing incorrectly and using the wrong capabilities. That could end up costing agencies two to three times what they might have paid for cloud services.
Accurately determining cloud migration costs and the costs of maintaining a data center will help IT leaders persuade CIOs, CTOs and CFOs of the need for a cloud migration.
The shift to remote work and the ability to increasingly access sensitive information via the cloud shows how quickly cloud environments can change. That’s why it is critical for cloud migration costs to be accurately estimated before a migration gets underway.
This article is part of FedTech’s CapITal blog series. Please join the discussion on Twitter by using the #FedIT hashtag.