110 Mistakes to Avoid When Migrating Data Centers to the Cloud
2Lack of a Strong Business Case
When considering a migration to the cloud, initiatives stem from two compelling reasons: You have to go or you want to go. Each requires a different level of commitment across the organization, driven by timelines and senses of urgency. What will the cost benefit be? Will you gain greater skills? These are questions that contribute to an organization’s cloud business case.
3Failing to Get Buy-In from an Organization’s Top Leaders
If there is a clear business case for migrating to the cloud, your CEO and board will find it easier to agree with your proposition, but if there is not, you likely will have to fight harder for their buy-in. So you need to be clear on why and how the company will make the migration and determine who are the “cloud champions”—the leaders in the organization who realize the benefits of operating in the cloud and will fight for the change.
4Failing to Prepare the Organization’s Culture for the Move
An organization’s CIO is not the only person affected by a migration to the cloud. Failure to prepare the entire company can result in hesitations from various teams and departments. Operating in the cloud—whether with Amazon Web Services, Microsoft Azure Cloud or others—requires some study and thoughtful preparation by employees across the entire organization.
5Failure to Include App Owners at an Early Stage
App owners need to be prepared for a cloud migration project. Even if organizations are using tools for discovery, the picture isn’t complete without a human touch. App owners need to be consulted during initial planning and discovery, and they need to be prepared for their part in the project, including user acceptance testing and downtime. App owners must provide the migration teams with other important data, such as Service Level Agreements and regular maintenance-window schedules.
6Not Exploring All of Your Options
Whether you are rebuilding or rehosting your data during a cloud migration, both routes have their advantages, and there is no right or wrong answer. Once a thorough discovery is complete, some applications may require only a “lift and shift” while others will need to be rewritten entirely. Don’t discount either path to the cloud and do your research.
7Waiting to Move Individual Applications
While your team is coordinating a plan to move heavier applications to the cloud, there is no reason to delay moving smaller, less sensitive ones. Some applications require more planning and resources, so the time it takes to transition those is longer. But that shouldn’t mean your entire cloud migration should be delayed. Don’t hesitate on the applications you can move to the cloud first.
8Failing to Include Security Precautions in Your Planning
9Not Training Your Staff Correctly to Do Their Job in the Cloud
Skills shortages are a major roadblock for many organizations that are deciding whether to move to the cloud. To properly train IT employees, start by giving them projects that show the business benefit of being in the cloud and giving them time to learn. There also are training programs offered through providers such as AWS. Providing hands-on experience will help in exciting employees about the migration.
10Not Monitoring Costs Post Migration
11Making the Assumption That Cloud Will Be Cheaper
When debating a migration to the cloud, don’t fool yourself into thinking you are going to save tons of money. Storing data on-premises can be less expensive, but when you factor in time to implementation, tax implications, overall flexibility, ongoing costs, reliability and security, cloud is a clear winner.