Repurchasing can be the simplest, fastest and least-risk method of running applications in the cloud. An organization can eliminate a lot of migration effort and cloud set up by directly consuming applications via the AWS Marketplace. Unfortunately, Repurchasing is often ignored as a migration option by most technical IT staff, creating opportunity cost of the business they work for.
This is the second in a five-part series covering the practical realities of migrating applications to AWS:
In this post we explore the Repurchasing migration method in the same consistent manner as the other three methods using the following outline:
If you want to access the whole series in one sitting, you can go get the Cloudsoft white paper:
Let’s look at some examples of Repurchasing:
Uncovering these opportunities to Repurchase will happen through a Discovery process for the organization’s current application landscape.
For example, it is becoming increasingly unusual for organizations to build and operate their own email systems. As part of the Discovery Assessment, if an email service is found to be run in-house then it is highly likely that a recommendation to Repurchase this as a Software-as-a-Service email offering is the best value.
The Repurchasing method is constantly evolving and is likely to see significant growth from the current 5% of migrations to AWS (source: AWS) because this evolution is opening a myriad of Repurchasing paths.
AWS Marketplace and Service Catalog have always been ways to avoid migrating fragile on-premises applications and instead Repurchase them in the form of an appliance in the AWS Marketplace. This is like an upgrade process where old configurations and data are migrated to the Repurchased platform.
The evolution of AWS Marketplace and Service Catalog means It is now possible to not only rent appliances but also rent SaaS products, bring your own licence and even negotiate complex Private Offers with AWS and the vendor.
There are a couple of important tailwinds behind the cloud computing revolution.
Consumers of technology wish to move to a more consumption-based procurement model, swapping lumpy three-year capital expenditure deals for monthly, no commitment pay-as-a-you-go models that efficiently ties their spend to their own income.
The “Enterprise” in enterprise software is no longer the “gold standard” of technology. With the rise of open source and the rapid pace of innovation in software, “enterprise software” is now perceived as legacy, old, outdated, ugly, difficult to use. Customers want to rotate their software stacks faster to remain competitive.
Repurchasing software through cloud procurement frameworks such as AWS Marketplace is how enterprises can refresh their application stack in a frictionless manner, which is a huge driver for enterprises. It eliminates long, complicated and expensive software procurement cycles like multi-stage RFI and RFP processes.
Trialling software via AWS Marketplace, and turning it off if it isn’t suitable, is a far more efficient method of software procurement.
In terms of application migration to AWS, organizations choose Repurchasing to prune down the applications they self- design, build and operate to eliminate costs and improve bottom line net income.
There are several benefits with Repurchasing.
Replace antiquated systems with modern appliances and SaaS.
Buy appliances, BYOL, SaaS and Private Offers through one procurement mechanism.
The systems purchased are built by specialists you don’t need to hire. SaaS means it is also run by people you don’t need to hire.
The less there is to migrate, the faster, cheaper and less risky the migration program will be.
There are a number of risks when Repurchasing. Failing to consider and manage these can lead to poor migration experience and mismatched outcomes when the new, shiny purchased system simply doesn’t work.
Example: If you replace your on-premises Active Directory system with a cloud version: which clients and applications must you reconfigure to use the new cloud service?
Your Procurement team and procedures may be incompatible with this new way of buying applications. There are four methods they need to learn: Appliance (rented licence), Bring Your Own Licence, SaaS and Private Offer.
Does Finance know how to handle pay-as-you-go, unpredictable future costs?
Can Operations “migrate” to administer the purchased system? Migrations are often as much about people and process as they are about applications and data.
The seven steps below represent a common pattern to approach Repurchasing. Of course, different applications will require modified approaches, but this is a standard approach using AWS Marketplace.
Repurchasing is quite different from Rehosting and Replatforming because you are dropping your current system and shopping for a new system. This reduces the number of actual migration activities to carrying forward configurations and migrating data. Data migrations should be easy on systems that have import features.
The key capabilities you need to make Repurchasing happen are:
There is no standard timeline or budget for Repurchasing, it is highly variable according to the software but – in general – it is the fastest, simplest migration method.
Any migration program that is missing Repurchase has inherent opportunity cost measured in migrating applications via the wrong, more costly, slower, brittle and fragile method. Repurchasing is a huge opportunity to modernize applications and should be considered as the first step in any migration program, but it is rare that it is.
Our advice to everyone considering repurchasing is to get some education on the following resources and choose a partner like Cloudsoft to help you where needed.