Cloud-to-cloud migrations are not feasible for enterprise organizations.
Strongly agree3%
Agree41%
Neutral23%
Disagree23%
Strongly disagree7%
Other (please specify)
Sort by:
I strongly disagree, but find myself completely surprised by the results!
Does no one remember, before SOA, before Java, before the internet when we were locked into hardware cards and one enterprise application implementation would lock you in to the vendor and their supply chain forever? And when a serial controller rev number could bring it all down?
Cloud brings portability and flexibility to new levels.... if (IF) you are using cloud natively and not as yet-another-data-centre with GOLF development practice.
Organise the capabilities, the competencies and the development right and migration from cloud to cloud (be it IAAS or SAAS) is a dream, usually less than the cost of moving vendor (cost is what drove you to think about it right?). Pro-tip: PAAS on the other hand is going to lock you in, the exact same way IBM or Microsoft locked you in to their IDEs if you used their extensions and frameworks as shortcuts.
It's 2025, we are deploying robots to space. Of course that cloud-to-cloud migration is possible. More than that, it is an imperative to have the capability.
Cloud to cloud migration depends on your dependency with your cloud provider.
it depends. Some companies' "cloud native" migrations are performed while relying on a single cloud vendor's proprietary services, resulting in cloud vendor lock-in.
It depends how one controls one's supply chain, or even if one has made the business architecture shift away from supply chain and toward exchange of value and value-add contributions within an ecosystem. By adopting a straight forward simplification and leaning of business process, by ensuring configuration and adoption of the public cloud standards, and by carefully documenting process and configuration and avoiding all customisation and bolt-ons we can shift from one saas to another with minimal business case disruption. And we have done so twice already, jumping from one saas to another within the subscription year. vendor lock-in is a symptom, not a phenomenon, imho. It is a symptom of customer-disengagement more than it is the natural result of single-vendor-platforming.<br><br>
Paul - I agree completely that hyperscaler-independent processes are achievable. And there are definitely IT leaders who were not fully cognizant of the vendor lock-in consequences of their IAAS, PAAS and SAAS implementation policies. Some organizations have actually made conscious choices for single-cloud policies, often in the name of security, or to satisfy consumption commitments in connection with volume discounts. Inevitably unexpectedly high costs, or another SaaS or hyperscaler vendor's unique capabilities lead to second thoughts. That said, your organization's discipline for maintaining agility is exemplary.<br>
As a follow-up to my prior post, I’d like to add a strategic corollary:
If your enterprise is struggling with a cloud migration for corporate apps, that’s a strong indicator it’s time to act—and urgently. Think of it as the HR principle: “Anyone deemed irreplaceable must be immediately replaced.” Along the same lines, any system too complex or rigid to migrate should be evaluated for replacement or re-engineering -- immediately!
There are two strategic paths forward:
1. Re-engineer the Enterprise for SaaS ecosystem webs: Shift your business model and systems architecture to fully embrace modern SaaS solutions. This approach leverages scalability, innovation, and efficiency inherent in cloud-native architectures. It’s faster and significantly less expensive, but it requires organizational alignment and leadership buy-in to adapt business processes.
2. Rewrite Your Own Stack as a Web of Business Services: Maintain control by building custom, service-based architectures. While this may feel more familiar to your IT department, it risks perpetuating old habits, higher costs, and longer implementation timelines. This option sacrifices the agility that SaaS ecosystems offer. Option 2 is very very expensive, but comfort is as comfort does.
The strategic imperative is clear: enterprises must embrace portability and agility. Organizations clinging to legacy systems or custom-built architectures often find themselves unable to adapt to market demands. The cost of inaction is higher than the cost of migration. Choose wisely and boldly, my peers. And Happy New Year!