Cloud exitRepatriationEU jurisdiction

Cloud exit: repatriating from the public cloud

A cloud exit is the controlled move of applications, data and workloads out of the US public cloud to a Dutch or European environment, or to your own infrastructure. Appfront carries out that exit: in phases, application by application, and always with a fallback option. We handle the application and data migration ourselves; for data centres, IaaS and colocation we work with specialised Dutch infrastructure partners. Still unsure what exactly needs to move? Then start with the sovereignty assessment.

What is a cloud exit?

A cloud exit, also known as repatriation, is the planned move of applications, data and workloads out of a US hyperscaler's public cloud and into an environment you choose yourself: a Dutch or European cloud provider, a private cloud or your own infrastructure. What sets it apart from an ordinary migration is the direction and the reason: you are leaving deliberately and want the exit to be controlled, with no disruption to your services and no data loss.

The trigger is often legal. US cloud providers fall under the US CLOUD Act and FISA, even when their servers are in the EU: jurisdiction follows the parent company, not the server location. For organisations with sensitive or regulated data, that is increasingly hard to justify under the GDPR, NIS2 (the Dutch Cybersecurity Act enters into force on 15 August 2026) and sector standards such as NEN 7510 in healthcare and the BIO in government.

Cost control and obligations also play a part. Public cloud costs grow with usage and are hard to predict; for stable workloads, your own or a European environment often gives you more control over the cost profile. And increasingly, a prepared exit is simply mandatory: the revised Dutch central government cloud policy of 3 July 2026 requires government organisations to store and process data within the EEA, carry out a mandatory risk assessment and maintain an annually reviewed exit plan, and DORA requires financial institutions to have exit strategies for critical ICT services. If you have such a plan, you also want to be able to execute it. This service is about that execution; for the analysis beforehand, there is the sovereignty assessment.

How we approach this

1
Making the exit plan concrete
We start from your exit plan or assessment: which applications and data are moving, in what order, and where they will land. If that picture is missing, start with the sovereignty assessment.
2
Design per application
For each application we choose the strategy: lift and shift unchanged, adapt, or rebuild. We plan the data egress in detail and set up the landing environment together with Dutch partners.
3
Controlled migration
Where possible we run in parallel, synchronise data and switch over application by application in a controlled way. The old environment remains available as a fallback until everything has proven itself.
4
Wrap-up and management
We close down the old environment properly: data demonstrably deleted, contracts terminated, documentation in order. After that we handle management and further development on the new environment.

What we build and deliver

Application migration
We move applications out of AWS, Azure or Google Cloud: from lifting them over unchanged to targeted rebuilding where cloud-native services make that necessary.
Data migration and egress planning
We plan the data egress carefully: volumes, bandwidth, sequence and integrity checks, so that data arrives complete and verifiable.
Replacing cloud-native services
We replace managed services such as queues, functions and databases with open alternatives that run on any environment.
Cutover runbook and fallback option
For each application, a runbook for the switchover, including a rollback scenario, acceptance criteria and a go/no-go moment.
Integrations
We rebuild the integrations with your existing systems and test the entire chain before making the final switch.
Management and further development
After the exit we provide monitoring, maintenance, security updates and further development on the new environment.

Who it's for

Government and public sector

The revised Dutch central government cloud policy requires storage and processing within the EEA, advises against public cloud for email and document management, and demands an exit plan that is tested annually. We carry out that exit plan.

Healthcare

Organisations that process medical data under NEN 7510 and no longer want to host it with a US hyperscaler.

Financial sector

DORA has applied since 17 January 2025 and requires exit strategies for critical ICT services. We make that strategy executable and carry it out.

Organisations with rising cloud costs

Companies with stable workloads for which the flexibility of the hyperscaler adds little, but whose bills keep growing with usage.

Technology and approach

We repatriate to open, portable technology. We replace cloud-native building blocks with open alternatives, so your applications run on any environment and a future move no longer requires a rebuild. For the landing infrastructure we work with specialised Dutch partners; we retain control of architecture, migration and applications.

Kubernetes / containers
Infrastructure as Code
PostgreSQL and open databases
S3-compatible object storage
Encryption in transit and at rest
Dutch data centres via partners
Monitoring and logging
Open standards

Why Appfront

Appfront is an independent software and app agency. We do not sell hosting ourselves and have no interest in where your workloads end up, so our advice on the landing environment is unbiased. We combine migration experience with the engineering capacity to adapt or rebuild applications where the exit requires it.

  • Phased approach with a fallback option per application
  • Application and data migration in our own hands, infrastructure via Dutch partners
  • Experience replacing cloud-native services with open alternatives
  • Management and further development after the exit

Related services

Start with the sovereignty assessment if you do not yet have an exit plan. Also see migrating applications to a sovereign cloud, migrating from AWS to a sovereign cloud and building a sovereign cloud.

If your exit also raises the question of who is entitled to the data your systems and equipment produce, that touches on the European Data Act: it obliges providers to make switching possible without unnecessary barriers and gives users the right to their own product data.

Frequently asked questions

What exactly is a cloud exit or repatriation?
A cloud exit, or repatriation, is the controlled migration of applications, data and workloads out of the public cloud to an environment of your choice: a Dutch or European cloud provider or your own infrastructure. It is the execution of an exit plan, with a migration approach per application and a fallback option during the transition.
Do we need to do an assessment before we can migrate?
We recommend it if you do not yet have a clear picture of what needs to move. Our sovereignty assessment maps applications, data flows and dependencies and delivers a prioritised plan. If you already have an exit plan or migration plan, we start on execution straight away.
Where will our applications and data end up after the exit?
That depends on your requirements: a Dutch or European cloud provider, a private cloud or your own infrastructure. Appfront handles the application and data migration; for data centres, IaaS and colocation we work with specialist Dutch infrastructure partners.
What happens if a migration goes wrong during the transition?
We carry out every migration with a fallback option: the old environment stays available until the new one has proven itself in production. Where possible we run in parallel, synchronise data and only switch over permanently after acceptance. If something goes wrong, we switch back without data loss.
Do you migrate everything in one go?
No. We migrate in phases, per application or per group of related applications. This keeps your services running and the risk per step small. We determine the order based on dependencies, risk and the sensitivity of the data.
Do you also handle management after the exit?
Yes. After the exit we handle monitoring, maintenance, security updates and further development of your applications in the new environment. This keeps the solution up to date and lets you demonstrably meet requirements such as a working, tested exit plan.

Get started with your cloud exit

Do you have an exit plan that needs to be executed, or do you want to know what repatriation would look like for your applications? We're happy to think along with you, independently, about a controlled route out of the public cloud.

Edit content