Cloud Migration Paths
Oliver Richardson
![Oliver Richardson]()
Oliver Richardson
Public Service | Helping our clients reinvent in the era of AI | Executive at Avanade
This article does a good job outlining the different choices in migrating to the cloud. Do you lift and shift, do minor upgrades as you move, or completely redesign apps. It makes clear that your business case needs to account for the migration approach up front to calculate the overall business value.
For you're most critical apps you'll get the most savings, and cloud feature benefits, by rebuilding in the cloud. You need to be careful however to make sure you know what you're doing. How long is that modernization going to take? Do you have the right skills and\or partner? If it takes too long and costs too much your business value is going out the window.
Global Chief Architect & U.S. CTO | Microsoft Technology Services Practice at Deloitte Consulting
6 年Reality is overall it is the same approach that has been used many times over the years from mainframe, Client/Server, Lotus Notes, Desktop, etc as a new technology emerges and evolves.? It definitely is ultimately about the business value driven by each decision, however the biggest shift in Cloud Development is in making a choice to step back and thinking through your entire portfolio stack and strategic goals.? Then deciding where and when to decouple to start shifting to a new landscape that provides greater ability and whether you include legacy apps as part of that transformation.? This gives it an entirely new lens by which to evaluate & shift your portfolio as it is no longer broken up in a legacy "app" by "app".