If you’re on the fence about whether to take your organisation to the cloud, take a moment to consider why you should make the leap. Here are some key reasons why businesses start their migration and the methods they choose.
Reacting to the moment
A compelling event will motivate you to make the move. Circumstances vary by organisation. For instance we have worked with some clients who have compelling events that mean they need to evacuate their on premise data centre quickly and cheaply (e.g. their on-premise datacentre needs urgently upgrading). In this case the simplest and fastest approach means taking the workloads and deploying to public cloud with no modification – the majority of a business’s applications are lifted-and-shifted to the cloud.
Other compelling events for organisation are the significant infrastructure and technical debt that they need to eliminate as a matter of urgency. An example includes old unsupported operating systems. Because the operating systems or other key components are out of date, the workloads platform needs to be uplifted. This is called a re-platforming. In this case the majority of workloads in these migrations need the re-platform treatment as they are migrated to the cloud.
If we don’t do it, they will
Sometimes there is no compelling event but the business recognises that competitive tensions mean they need to be more innovative to quickly adapt to market conditions. This can include developing new products and services that their customers don't even necessarily know they want, such as the competition from Open Banking. In this case, the migration is more about re-architecting and re-factoring the workloads’ increasing agility, which involves changing the way system has been designed and implemented– such as moving from Java Enterprise Edition to implementing a cloud native serverless architecture.
This modernising to innovate on public cloud means organisations can take advantage of additional cloud services that traditional on-premise co-located setups cannot offer. Modernising by re-architecting and re-factoring takes longer and is more expensive to migrate. However, running cloud native applications in a public cloud can greatly increase business agility.
The running cost of on-premise, private data centre or even cloud is another alternative to a compelling event. Organisation may want drive costs out by rightsizing their IT infrastructure, pre-purchasing reserved cloud compute or modernising their application by re-factoring or re-architecting business applications to be more cloud native and therefore cost efficient. Running cloud native applications in a public cloud can be very cost competitive. With all the benefits, the momentum driving organisations to public cloud seems inevitable, it makes sense to spend to the future not sideways to the old ways.
Regardless of the reason, it is the circumstances that determine the treatment an organisation uses to migrate.
What’s the best overall approach then?
Migrations are never one size fits all. Invariably there are elements of each migration treatment - for instance, specialisation and partnering mean that during a migration an organisation might want to outsource or otherwise consume some applications as services. This is commonly known as consuming as ‘Software as a Service’ – often the same business process can be found “as services” in the cloud. A business will identify services and re-purchase as part of a migration, retiring those old, hard to maintain monolithic applications.
Equally one style of migration may follow another. After a lift-and-shift to address a burning platform, it may be time to modernise a core application, nibbling away at a large hard to maintain system and decoupling by creating microservices and adding APIs at the periphery.
At Deloitte we have experience in successful migrations and can save your business time by helping and guiding your business through the one-time decision process. We do that by delivering an outcome and at the same time developing your organisations talent and uplifting technical capability. Find out more here.