Fact or Fallacy: 7 Tips for Cloud Migration at State and Local Agencies

Fallacy: Cloud Storage Is Inexpensive

A common misconception is that cloud storage is more economical than traditional ways of storing data. When agencies start retroactively preparing all of their data for migration and storage in the cloud, they can run into higher-than-expected costs. Many agencies experience sticker shock after migrating data. It also makes it harder for agencies to budget as they try to keep pace with growing storage demands. By tiering data, agencies can significantly reduce costs, paying more for data that needs to be accessed daily and paying less for data that can be stored away for regulatory or compliance purposes. But while tiering data can cut costs, managing data across multiple clouds is a challenge that comes with this approach.

RELATED: What are the main options for migrating off of a legacy mainframe?

Fact: Vendor Lock-In Can Be Avoided

Another big concern is being tied to the same vendor once all systems have moved to the cloud, especially if the vendor’s prices increase. Agencies that implement a multicloud solution can avoid dependence on one specific vendor. By using several cloud platforms, agencies have the flexibility to move between service providers. However, a multicloud architecture must be interoperable to avoid problems. PwC recommends using decoupled microservices with containers. Decoupling development and deployment will ensure continuous integration, while the use of containers will ensure interoperability.

Fallacy: Cloud Is Fundamentally Insecure

Many organizations view security as a leading challenge to cloud adoption. A recent StateTech Twitter poll reflected this view: 44 percent cited cybersecurity as the top roadblock for IT decision-makers. In reality, cloud service providers – including Microsoft, Amazon and Google – invest more in cloud security than most agencies. In fact, migrating to the cloud can improve security. Agencies can start small by moving a few workloads to the cloud and evaluating the results. Third-party assurance reports can also give agencies a glimpse into how cloud providers handle their data. Agencies can also choose a hybrid approach, where some data is stored in the public cloud while more sensitive data remains in private data centers.

Once agencies become comfortable moving their workloads to the cloud securely, they can transition fully from a hybrid cloud model to the public cloud. To avoid breaches, agencies must recognize that public cloud providers are not responsible for all aspects of cloud security. Agencies must manage security controls for their apps and user accounts.

DIVE DEEPER: Find out how three states have moved on from their mainframes.

Fact: Cloud Isn’t a One-Size-Fits-All Solution

A single, comprehensive cloud model doesn’t exist. Every cloud implementation looks different for every organization because every organization has different needs. Agencies can choose from a range of models, such as Software as a Service for cloud-hosted applications; Infrastructure as a Service for cloud-based data storage, servers, and networking; or Platform as a Service for integrated cloud-based infrastructure, among others. Several factors can influence which cloud model an agency chooses, including the agency’s size, existing legacy systems, budgetary restraints and whether it wants to migrate its data gradually or all at once. Ultimately, the model an agency decides to implement should be well suited for specific apps or use cases.

Click the banner below to get access to customized cloud content by becoming an Insider.

Leave a Comment