Pete Nieminen, Head of SAP on Public Cloud, can count ca 50 unique benefits for utilizing Public Cloud as SAP platform.
At the Nordic level, we were standing behind. Maybe the reason was our very early adaptations of the Public Cloud, which were mostly lift and shift-projects to the early, very different from now cloud services. Back then, most benefits were left unclaimed and unreachable, decision makes were disappointed. Lack of knowledge or unwillingness to listen to the experts was the most common reason for failure.
Even Gartner found out, re-visiting their research for Public Cloud infrastructure, that cost-efficiency if achievable usually in two years, but even in properly made transformation can still come up as negative ROI.
For me, this just emphasizes that cost savings cannot be the only or even the primary reason for entirely new infrastructure.
During the past ten years, Public Cloud has evolved exponentially. Terms like infinite scale, could native, always-up-to-date, Cloud DevOps and Cloud FinOps and many more hypes raised, but the actual business benefits were also within reach. I call this the second coming of the Public Cloud. This time, supporting the business is the key.
Scalable IT infrastructure is nice, but achieving a truly scalable business is excellence.
The technical, financial and business advantages are substantial. Unpredictable costs and huge capital expenses can now be transformed into operating expenses. First time ever, you can actually downscale and not only upscale your ERP costs during the long contract period. Even SAP itself predicts that more than 3/4 of its customers will choose Public Cloud as the next platform.
So why should you: "hold your horses"? Is there something wrong with the concept? No, and not because this is a big decision. There are over 5.000 organizations that have already made it. Most of them fully successful and getting full benefits. I am worried about those who are NOT getting the full benefits.
Now when most of the enterprises have realized, that utilizing the Public Cloud as an SAP platform is an excellent idea for both business and IT, the organizations started rushing in. The future or present requirement for S/4 HANA is also accelerating the need for platform change.
It is true that so many have done the migration to Public Cloud already, that probably no deep discovery and project planning phase is needed (note that I am talking about the BASIS migration now, not SAP applications) since the migration process is quite straightforward for those with enough experience on it.
There are the skills, tools and experience, so what am I worrying about? The rush. Previously I mentioned that the old "ways" do not apply anymore. Many of the organizations planning for the migration do not realize that they want the RFI's, RFP's and whatever answered in a week or two. Why? Because that's the way it has always been done.
If you want everything to be done 1:1 it still does not work that way. Even with experience, automation and straightforward processes, you cannot do SAP on Public Cloud as a 1:1 migration. If you could, you would lose all possible benefits and pay too much from the beginning with never getting to any kind of break-even in costs - and you can't do even that, since most of the principles are not the same. You need to plan the strategy, start the journey with migration and establish a roadmap for controlled and measured business transformation.
Learn more on on the subject of SAP on Public Cloud here.
Pete Nieminen works as a Lead Advisor and Head of SAP on Public Cloud at TietoEVRY, combining Cloud, Cybersecurity, and SAP together as one future-proof ecosystem for enterprise businesses. He has more than 20 years of experience in digital business development, technology solutions, and operating as a trusted advisor and CIO. During his career, he has been selected 11 times as TOP 100 ICT-influencer and he has published more than 100 magazine articles. Pete describes him as a businessperson with a deep passion for technology.