End-of-life is the start of something new

Inside the EU does not mean outside the Cloud Act

A common assumption is that having a Dutch branch, a local subsidiary, or a data center within the EU provides sufficient guarantee for digital sovereignty. Unfortunately, that is not the case. It is not about where the data is stored, but which legislation the (parent) organization is subject to. If a supplier is American-owned, it falls under the U.S. Cloud Act, regardless of whether the infrastructure runs in the Netherlands or invoices are sent by a Dutch entity. In such cases, authorities can demand data, with or without the customer's knowledge.

This is not a theoretical risk or a political stance; it is a legal reality that must be taken into account when planning new Cloud infrastructure.

Public Cloud is scalable and unpredictable

The Public Cloud almost always solves the scalability issue: the options and possibilities of the Public Cloud are endless. However, it often introduces an additional problem: the costs of scaling in the Public Cloud are also endless. What looks manageable at low volumes quickly adds up as you scale. If your organization grows in the Public Cloud and costs spiral, it is difficult to reverse.

For workloads and specifically business-critical applications, it is smarter, better, and more cost-effective to set up the underlying Cloud infrastructure as a fixed and manageable provision, ensuring continued control over the total cost of ownership so that costs do not increase linearly with growth.

What should you outsource?

Where many replacement projects fail is not the technology, but the available knowledge within the team. New Cloud capabilities often require new skills, and developing those skills within the team rarely aligns with the timeline set for hardware replacement.

Acquiring specialized knowledge in a tight labor market is neither easy nor cheap. Outsourcing everything is the other extreme. The smartest approach is to have a partner by your side who already possesses this knowledge and transfers it while the environment is being migrated. During the migration, your team focuses on what matters to the organization, while the infrastructure is set up by specialists for whom this is a core activity. This way, you can both migrate to a new environment and ensure that the knowledge remains available within your team.

Insight first, action second

An approaching end-of-life date creates pressure to make quick decisions. That pressure is real, but a rushed transition increases the very risks you are trying to mitigate. What does work is a structured first step: mapping out which systems and applications run on the current infrastructure, which of these are business-critical, and which dependencies and compliance requirements influence the chosen route.

This insight will determine whether a phased transition is the right approach or if everything can be migrated at once. That sequence—insight first, action second—determines whether a migration is executed with confidence or leads to surprises later on.

A partner for the next phase

When your hardware and environment reach end-of-life, it’s not just about the technical implementation, but also about who stands by your side. Choose a partner with a clear ownership structure, one that operates within the same jurisdiction and time zone, and one that views knowledge transfer as an integral part of the collaboration.

Fundaments guides this process from assessment to migration with infrastructure delivered in the Netherlands that demonstrably complies with all relevant laws and regulations. Not as a one-off project, but as a partner for the phase that begins after the replacement.

Is your infrastructure reaching the end of its lifespan and do you want to know how to make it smarter, better, and more cost-effective? Get in touch for an initial exploratory conversation.