IT Tips & Tricks
Published 19 July 2022
Cloud Migration Problems: An Overview of Three Key Barriers
What would G.I. Joe do?
Tech research giant, Gartner, states that 83% of all data migration projects fail and that more than 50% of migrations exceed their budget. Nobody in their right mind wants to be the guy responsible for either of those figures or the side-servings of fuming bosses, downtime, irate end-users, or missing data that frequently accompany a botched migration — Cloud or otherwise. However, in their June 2022 report, Gartner identifies three key problems that infrastructure and operations (I&O) leaders must overcome in order to ensure a successful Cloud migration. Per G.I. Joe, “Knowing is half the battle.” If it’s good enough for Joe, it’s good enough for us, so let’s dive into this overview.
Writing for Gartner, Philip Dawson states, “Cloud migration initiatives for enterprise applications are often thwarted by application size, high levels of customization and insufficient skills. Before migrating applications, I&O leaders must break down the barriers by modernizing infrastructure and applications into Cloudlike configurations.”
The three identified barriers are:
- Application size,
- High levels of customization and
- Insufficient skills.
We’ll expand upon each of these points below.
“Knowing is half the battle.”
— G.I. Joe
While virtual machines (VMs) advancements allow I&O leaders to migrate mid-sized applications (from 2TB to 6TB) to the Cloud, applications larger than 6TB cannot yet be migrated on a single VM. (The key word there is “yet.” Things change fast in the tech world.)
Gartner says that 83% of data migrations fail. Yours doesn’t have to.
Unlike new applications, the bulk of the enterprise application portfolio — about 85% of existing core IT applications — predates the Cloud and was therefore not designed using the principles of Cloud-native architecture. Examples include legacy mainframe and mid-range applications, ERP (enterprise resource planning) applications, and proprietary UNIX-based applications. These applications are often highly customized and large in size, making them incompatible with most Cloud platforms. A lift-and-shift approach for migrating legacy applications to the Cloud is seldom an effective strategy, and the approach to customized apps is discussed below.
The Impact of Customization
I&O leaders are tasked with managing a broad array of customized applications that are not designed to run in the Cloud (or even on Cloud-like on-premises infrastructure). Having identified which applications are suitable for Cloud migration, I&O leaders face another challenge: Many of their existing applications are customized and are not designed to run in the Cloud. This means that IT departments must standardize these applications before the migration can begin.
It logically follows that the path to standardization depends on the level of customization. Most legacy applications have three types of customizations:
- Added or customized screens and reports,
- Added fields or indexes/totals,
- Added processes and custom scripts.
The greater the level of customization, the more difficult and time-consuming it is for I&O leaders to migrate and modernize the application to the Cloud. Therefore it makes sense to kick off a migration with high-value apps that have fewer customizations, as these applications require less time and effort to standardize. The goal is to transform a lightly customized application into a configured application that has:
- Edited text fields within configuration,
- Hidden fields or indexes/totals,
- Standard processes and custom scripts.
Once these issues are addressed, I&O leaders should then be able to migrate the configured application to the Cloud.
“Before migrating applications, I&O leaders must break down the barriers by modernizing infrastructure and applications into Cloudlike configurations.” — Philip Dawson, Gartner
Key Skills: Transitional and Transformational
Cloud providers often focus on providing operational and implementation skills, rather than transitional and transformational skills. In other words, the service level agreement (SLA) from the provider includes “build” and “run” (the vehicle), but not “plan” (the journey). Transitional and transformational skills are often beyond the scope of the contract, but there’s literally no point in creating a vehicle that’ll never travel the journey.
Things don't always go according to plan. But there's a reliable way to make sure that your linked data is always exactly where you want it to be.
To facilitate a smooth migration journey to the Cloud, I&O leaders need to avail themselves of four distinct skill sets:
- Operational skills. This requires the ability to run standardized applications in the Cloud more cost-effectively than on-premises infrastructure. Cloud IaaS (infrastructure as a service) providers excel at providing infrastructure skills, and a provider’s subscription-based model is often cheaper than on-premises, project-based alternatives (at least for the first couple of years of the contract, but this will vary, provider to provider).
- Implementation skills. This is the ability to directly move those standardized applications to the Cloud. Most Cloud providers offer this capability for configured applications. However, highly customized and complex applications could potentially be more expensive when moved to the Cloud (especially in the longer term). This means that standardization could pay for itself over time.
- Transitional skills. This translates to the ability to move a customized app from on-premises to PaaS (platform as a service). Without specialized skills related to the systems, these transitions can be difficult, if not seemingly impossible. Cloud providers typically lack these skills and partner with a system integrator (SI) to provide this capability — at a cost — to you.
- Transformational skills. The ability to move a customized app from on-premises to a new packaged application or SaaS (software as a service). To complete this migration, the application must be standardized, modernized and configured, which requires specialized skills that come at a premium and are generally only available from system integrators and third parties.
While Cloud IaaS providers deliver the underlying infrastructure and shine at offering operational and implementation skills in SLAs, they often rely on external partners for specialized transitional and transformational skills — resulting in an I&O skills gap.
The bulk of the enterprise application portfolio was not designed using the principles of Cloud-native architecture.
The bottom line? You may find it more cost-effective to temporarily contract your own specialist rather than paying your Cloud provider’s fees for this service.
Whether you’re the I&O leader or the IT professional responsible for the success of the migration, what exactly, are you supposed to do about the above points? Gartner suggests the following:
- Classifying applications based on size helps determine the best migration path for each existing application (such as Cloud versus hosting).
- Collaborate with application teams to standardize legacy applications by reconfiguring heavily customized applications (for hosting) and re-platforming lightly customized applications (for Cloud).
- Encourage modernization by complementing traditional I&O teams with transitional and transformational skills from strategic partners or system integrators (SIs).
The Fourth Wall
Complex, customized apps may be more expensive when moved to the Cloud and may therefore need to be standardized and modernized.
We’ve taken a look at three potential barriers to a smooth Cloud migration, but there’s another issue that warrants mention: the fourth wall, as it were.
We’re willing to support your determination, leading up to your migration, to avoid black cats and refrain from walking under ladders. But if you feel like what you need is something that really makes a difference, then here’s a tip that definitely makes a difference and requires no avoidance of cats or ladders.
You’re probably aware that missing data is a frequent side-effect of data migration, and you may also know that a common cause of that missing data is the file links that break during the migration process. Missing data results in a host of things we’d all prefer to avoid, such as downtime, moaning end-users, a storm of open service tickets, grumpy bosses and you being stuck at the office long after others have left.
Want to avoid all of that? Then the smartest thing to do is to avoid the broken links phenomenon in the first place. How? With LinkTek’s LinkFixer Advanced™ software.
LinkFixer Advanced can be used prior to a migration to prepare your file links. After you’ve completed your migration, LinkFixer Advanced will repair any prepared links that broke, thus preventing the usual data loss.
If you’ve already completed a migration and have missing data due to broken file links, think of LinkFixer Advanced as your disaster recovery tool. It can repair broken links after the fact and instantly restore your missing data.
We wish you a successful migration and a scarcity of black cats and ladders.
Feel free to share this article on your social media: