Blog

A concrete cloud exit strategy: "Have it ready, tested, and waiting on the shelf"

The cloud environment is getting turbulent. The pleasant blue sky with its soft horizon has given way to a harsh American wind and dark clouds gathering over Europe.

18 Nov 26
5
min read

This means it is crucial for companies to scrutinise their cloud strategy. My advice: make sure you have a concrete exit strategy ready on the shelf, thoroughly tested and all.

Potential price hikes and data access by the US government

There are two key reasons why the cloud is currently under pressure. First, we are seeing protectionist policies under Trump, which are already sparking trade conflicts and higher import tariffs. This could significantly drive up the costs of American cloud services in Europe. Companies are concerned about the financial stability and reliability of these providers, particularly given the unpredictable direction of the US government.

Furthermore, there is concern that the US government could gain access to the data of European companies using American cloud services. This could jeopardise the confidentiality and integrity of corporate data. For organisations handling sensitive information or state secrets, this is a serious concern.

And in extreme cases, there are also fears of services being shut down by the US government. In principle, they could halt all our processes and data at the push of a button. It may be unlikely, but theoretically, it is possible.

Time to bring on that exit scenario

What does this mean in practice? It certainly does not mean you should panic and pull your data from everywhere. However, it is essential that your organisation constantly has an exit scenario ready to go. That way, you can switch quickly to an alternative cloud provider whenever necessary.

An exit scenario is much more than just a document; it needs to be tested and workable. With an exit scenario, you are prepared for unexpected shifts in costs, availability, or the integrity of cloud services. A well-thought-out and rigorously tested plan allows you to guarantee continuity and keep risks manageable.

Such a scenario shouldn't actually be anything new. In sectors like financial services, it is already standard practice for cloud migrations. This has also been a topic of discussion within the Dutch government for some time, but it is now receiving renewed attention: the risks of hosting certain services with American cloud providers are being re-evaluated.

The roadmap for a solid cloud exit strategy

1. Identifying risks

Start by mapping out the components of your environment and the potential risks your organisation faces with US cloud providers. Think about technical, financial, and legal risks.

Examples of risks:

  • Cost increases due to new import tariffs and protectionist measures.
  • Data sovereignty: Under the Cloud Act, the US government can demand access to data belonging to European companies and citizens. This impacts data privacy and confidentiality.
  • Service availability: The US government can compel cloud providers to restrict certain services. This happened previously with the Amsterdam Trade Bank, a Dutch subsidiary of a Russian bank. Due to US sanctions, Microsoft blocked access to essential software systems, which ultimately led to the bank's bankruptcy. In that case, there was a valid reason, but what if there isn't?

2. Evaluating probability and impact

The next phase of your risk analysis consists of two parts: you assess the likelihood of a risk occurring and the impact it would have on your business operations. For each risk, you determine the best approach: avoid, mitigate, transfer, or accept.

  • Avoid: You structure your processes so that the risk no longer applies. For example, by not using American cloud services and opting for a European or local provider instead. Note: this is not always feasible, as there isn't a full-fledged alternative for every service. Moreover, you trade known risks for new ones, such as potentially reduced functionality.
  • Mitigate: You reduce the impact or the probability of a risk. Think of storing data partially in the American cloud, making long-term price agreements to limit cost increases, or applying extra encryption to ensure data sovereignty. But there are risks here too: encryption can be error-prone, for instance—what if you lose the key?
  • Transfer: You shift the risk, for example, by purchasing your cloud services through a local Managed Services Provider (MSP). This MSP can make agreements regarding price hikes and data sovereignty. If problems then arise with the underlying cloud provider, the MSP is responsible for managing those risks.
  • Accept: Sometimes avoiding or mitigating is not an option and you have to accept the risks. This means being prepared for the consequences, for example by maintaining financial reserves for a price increase or having an alternative ready in case of an outage.

A well-developed risk assessment helps your organization determine which measures to take to manage risk, and which risks require the most attention and resources.

3. Exploring alternatives

Look into alternative cloud providers and assess them on functionality, reliability, cost, and compliance. With IaaS, migration is relatively straightforward. But with PaaS and SaaS, you are more likely to encounter vendor lock-in due to your dependence on the provider's proprietary technologies. This makes switching far more complex.

Therefore, map out your dependencies in advance and test exit strategies to avoid unpleasant surprises.

There are many good European alternatives. But to find the best match, thorough research is required. Few companies offer complete service packages like the ones we are accustomed to from Microsoft, AWS, and Google.

For now, the focus is on finding suitable partial solutions for specific tasks and business processes. At BBTG, we conduct extensive research into this and test various options together with our clients.

                                                               
CategorieAlternatievenOpmerkingen
Europese cloudprovidersOVH Cloud (Frankrijk), Uniserver (Nederland), Deutsche Telekom (Duitsland), Scaleway (Frankrijk), UpCloud (Finland), Hetzner (Duitsland), StackIT (Duitsland)Lokale alternatieven voor AWS, Azure en Google Cloud, wisselend in professionaliteit en flexibiliteit
Europese cloudinitiatievenGaia-X, PublicStack, Open Webconcept, European AlternativesGericht op digitale soevereiniteit en open-source IT, alternatieven vaak versnipperd
Hybride en multicloudCombinatie van meerdere providers, lokale datacenters, cloud-agnostische architectuurVermindert afhankelijkheid van één leverancier, vaak complex in beheer

User-friendliness of European providers

The major American cloud providers are known for their user-friendliness. Many people wonder if that also applies to European providers.

My impression: In many cases, the user-friendliness is at least sufficient. And humans are flexible beings: when necessary, we adapt to new interfaces and operating systems over time. Just as we do now with Windows, Mac, Linux, and all kinds of new software.

Moreover, the user-friendliness of European alternatives will develop rapidly, especially as more investments are made in the European cloud market. What is important, however, is a well-thought-out adoption plan to guide employees through the new way of working.

Pro tip: check out a list of 100% European cloud providers here.

4. Testing alternatives

Selecting an alternative provider is not enough; you also need to test whether it meets your requirements.

Such a test involves running a pilot for a specific business unit or process to see if it actually works as "advertised in the brochure." This begins with an analysis of the following components:

  • Cost analysis: Is the switch financially viable?
  • Contractual evaluation: What are the legal and financial consequences of switching?
  • Functional testing: Do all necessary applications and services work?
  • Technical integration: Are databases and applications compatible?
  • Continuity and availability: Is the new provider as reliable as the current one?

A pilot or Proof-of-Concept (PoC) is necessary to see if the new solution actually works as expected in practice. A controlled pilot keeps the scope small and manageable. If it doesn't meet requirements, no harm is done. You can easily adjust or choose an alternative approach without major consequences for the organization.

5. Assessing the impact on business processes

Once an initial test has been successful, it is time to examine how the new cloud environment impacts business processes.

Key points of attention include:

  • Identifying critical applications and services: Which systems must remain available at all times?
  • Testing performance and compatibility: Do applications run just as fast and stably?
  • Compliance and security: Does the new provider meet GDPR, NIS2 and other regulations?
  • Scalability and flexibility: Can the provider grow with the organization?

6. Developing an exit scenario

Based on the test results, you draw up a detailed exit plan.

This varies by organization and type of migration, but a number of basic components are always required:

  • what steps are needed for a smooth migration;
  • how to transfer data and applications;
  • what downtime or disruptions might occur.

With a solid exit scenario, you won't have to scramble if things actually change.

7. Testing the exit scenario

A plan on paper is not enough; it must also be tested in practice. The functionality of cloud and SaaS providers evolves continuously, which means that the scenario you devised and tested last year might no longer work completely today.

  • Test a (portion of the) switch to another cloud provider.
  • Practice with the infrastructure and application teams so everyone knows what to do when switching to another cloud provider.
  • Do this together with a small group of your users, so you don't burden the entire organization.

In practice, this doesn't mean performing a full cloud exit every year; it's about ensuring the exit strategy remains genuinely feasible and executable by testing it periodically.

8. Continuous monitoring and updating

An exit strategy is therefore not a one-off document, but a living plan that you regularly evaluate and update.

  • Keep following market developments: New providers and technologies may offer better alternatives, and the offerings of current providers are constantly evolving.
  • Account for changing legislation: Compliance requirements are constantly changing, partly due to (geo)political developments. This process normally takes years before a European regulation is transposed into national law and takes effect, but this has accelerated significantly recently due to increased urgency.
  • Conduct periodic risk analyses and tests: Ensure it is a living plan that has been recently tested and remains current. A major pitfall is the illusion of security: thinking that once an exit plan is drawn up, it never needs to be updated. So, keep the plan up to date and test it regularly.

An opportunity for innovation and renewal in the European IT market

Ignoring the clouds above our heads is no longer an option: you must have that exit strategy. But let's not be pessimistic. The current geopolitical situation also offers an opportunity for innovation and renewal in the European IT market.

This will bring forth new players and startups to develop innovative products and services. I believe this dynamic will ultimately lead to a broader range of cloud solutions, which promotes competition and improves the quality of service.

The exit formula: how to future-proof your cloud strategy

Developing an exit strategy is not just about mitigating risks; it is also about being prepared for the future. By carefully identifying risks, exploring alternatives, and establishing a thoroughly tested exit scenario, you ensure that your organisation always stays agile.

This blog was previously published on ogd.nl

‍

Featured posts

We don't do off-the-shelf job openings. We create your ultimate role based on your personal ambitions and expertise.

Blog

Enterprise AI and the organization of tomorrow

After a period of experimentation, it is time to scale up. With Agentic AI, AI is increasingly performing work itself. CTO Marco Boele discusses Enterprise AI and what it means for the surrounding organization.

Blog

The art of reducing complexity in software

Software development is often about adding new functionality. But as a solution grows, a different challenge arises: how do you ensure it remains understandable, maintainable, and extensible? The biggest obstacles to successful software projects are often not new features or technologies, but the complexity that builds up over time.

Blog

Shifting left on security while having fun

Shift-Left-on-Security is not only essential for preventing expensive and time-consuming problems later in the Software Development Lifecycle, but it can also be made attractive and motivating for developers. This whitepaper discusses how to make the transition a success.