.svg){kind=logo}
Why a shadow environment can be a better first step towards digital sovereignty than a disruptive migration.
For many organisations, becoming digitally sovereign starts with an overwhelming question: “How do we move away from the platform(s) that help run our business?”
When it comes to office productivity, Big Tech platforms such as Microsoft 365 and Google Workspace have become the default for a reason. They make it easy for teams to work and collaborate, giving them a single place for email, calendars, files, meetings, and chat. Everything is connected. Everything is familiar.
That is what makes leaving feel difficult. The more work, data and day-to-day processes an organisation builds within one ecosystem, the harder it becomes to separate them without disrupting the way people work. What began as a practical set of tools gradually becomes something the organisation relies on to communicate, share information, manage access and keep work moving.
And at the centre of that is email.
Email is not just another productivity tool. It is the communication backbone behind daily work. Password resets arrive there. Verification links and security notifications arrive there. Customer questions, invoices, contracts, supplier updates and service alerts arrive there. When email is unavailable, the impact rarely stays inside the inbox. Access becomes harder to recover. Customer communication slows down. Important notifications can be missed. Teams lose one of the main channels that keep the organisation connected both internally and externally.
That is why moving away is not simple. It means untangling shared folders, access rights, calendars, meeting links, automated workflows, connected applications and years of habits built around one platform.
That is vendor lock-in in practice.
Once a single ecosystem carries so much of the organisation’s day-to-day work, the provider’s decisions start to shape its choices. Pricing and packaging can change. Product roadmaps shift. New features can be introduced on the provider’s terms. And now, AI-powered capabilities can become part of everyday tools before an organisation has fully decided whether it wants them, what information they should access or how they should be governed.
That matters because AI can widen the reach of information across the workplace, expose old permission gaps and make sensitive content easier to surface in ways the organisation did not plan for.
But AI is only one part of the wider issue.
When critical communication, data, workflows and access sit inside one ecosystem that it doesn’t fully control, the organisation has less room to decide how it works, how it responds to change and how it moves on.
That is why digital sovereignty matters.
It is not about rejecting every tool an organisation already uses, forcing a dramatic move away from them overnight, or trying to build and maintain a fully sovereign digital environment from scratch on their own.
It is about reducing dependency before circumstances force a change, with the right expertise and infrastructure already in place. Because the real risk is not simply that a provider changes its price, product roadmap or AI strategy. It is that the organisation has no practical alternative when it does. And when a critical platform is disrupted, access is affected, or the rules suddenly change, that lack of choice can quickly become a business continuity issue.
A mirror, not a migration
That is where a shadow environment comes into play.
Instead of treating digital sovereignty as one large switch-over project, you build an independent environment alongside the platform you already use.
Your teams can keep working in the tools they know. Behind the scenes, the services and data your organisation cannot afford to lose are synchronised into a separate, sovereign environment that is kept current and ready when needed.
It is a mirror, not a migration.
This is not the same as keeping an occasional backup somewhere in the background. A real shadow environment is separate from the primary ecosystem and designed to be usable if that primary environment is disrupted, unavailable or no longer the right fit for your organisation. The scope can grow over time.
For some organisations, it makes sense to start with email: the communication layer that supports customer contact, access recovery, security notifications and everyday operations. For others, the longer-term goal may include calendars, contacts, files and collaboration as well.
The important part is that you do not need to replace everything before you begin.
You create an independent route alongside the environment you already use. Your critical data starts landing in a place that is open, portable and outside the ecosystem you are trying to become less dependent on.
That makes a future move more manageable. You are no longer trying to untangle years of work under pressure, during an outage or after a change you did not choose.
You have already built the route out.
Nothing needs to be forced. Nothing needs to break first.
What makes a shadow environment a real Plan B?
A backup is important. But a backup alone is not the same as a Plan B.
A backup gives you a copy of your data. A shadow environment gives you a live, independently operated fallback that is ready to support continuity when you need it.
For that to work, it needs to be more than a one-off export or a script someone runs when they remember.
It needs to be:
Independent: It cannot sit inside the same provider or environment you are trying to become less dependent on.
Current: It needs to stay synchronised, so the information you rely on is there when you need it, not weeks or months out of date.
Automated: A process that depends on one person remembering to run it is not reliable infrastructure. It needs to run in the background, on a schedule, without manual intervention.
Verifiable: You need to know the data has arrived, is complete and can be used. Not “it should be there”, but checked and tested.
Recoverable: The shadow environment needs its own backup and recovery process. A copy without snapshots, restore testing or a separate recovery route is simply another point of failure.
Operational: It needs to be ready before something goes wrong, with clear ownership and a documented process for what happens when it is needed.
In practice, that means your existing environment can remain in place while critical services and data are synchronised into a separate sovereign environment. Email, calendars, contacts and files can be kept current in parallel, using open standards such as IMAP, CalDAV, CardDAV and WebDAV.
The goal is not to create a second copy that sits untouched until disaster strikes. It is to maintain an independent layer that is usable, monitored and ready to support continuity whenever your day-to-day setup is unavailable, disrupted or no longer the right fit. That is the difference between a backup that stores yesterday’s data and a continuity layer that helps ensure work can continue, regardless of what happens to the primary environment.
This model has already been tested in practice.
Nextcloud and Microsoft 365 consultant Rik Dekker recently ran an experiment to see what it takes to build a shadow environment that stays live while an existing Microsoft 365 setup keeps running.
The process was simple in principle:
Take the data from the existing Microsoft 365 environment. Rik used Microsoft Graph as the source for mail, calendars, contacts and files.
Create a separate sovereign environment. In Rik’s setup, a fully functioning sovereign EU environment ran in parallel: email with Soverin, and calendars, contacts and files in Nextcloud.
Run the sync on a server. Rik ran the process in the background on the server, rather than depending on someone’s laptop being switched on or someone remembering to press a button.
Make it safe to stop and restart. The sync could be paused and resumed without creating duplicate data.
Back up the shadow environment itself. Rik also created a separate backup chain for the data, configurations and databases using snapshots, separate copies and regular checks to verify that everything had arrived as expected.
That is what turns a shadow environment into a process an IT team can run, monitor and maintain over time, rather than a personal project that depends on one person.
In translation, Rik put it this way:
“What surprised me: the hardest part wasn't the technology. It was letting go of the idea that switching has to be one big, scary project. It isn't. It's building a mirror while everything just keeps running, and then, at a moment you choose, flipping a few DNS records.
And that is the real benefit of sovereignty: not that you run away, but that you have the choice.”
The choice is becoming a requirement
Rik’s point about having a choice is no longer just a personal philosophy.
On July 3rd, 2026, the Dutch government adopted a strengthened cloud policy for central government organisations. One of its clearest changes is the requirement for a more detailed exit plan for important cloud services.
That plan must cover more than a planned switch to another provider. It must also show what happens if a cloud service suddenly becomes unavailable or has already failed, and whether the organisation can continue operating during a disruption in its digital chain.
For email and document services, the policy goes further. Government workplace services are treated as being of national importance, and public-cloud use is no longer the default. Where public cloud remains necessary, organisations must be able to justify the choice, assess the risks and maintain a tested exit plan.
The policy allows time for change. Existing cloud use that does not meet the new requirements can have a transition period of up to four years, or longer where existing contracts or major migration risks apply. But the message is not “wait four years.”
It is: start building your options now.
That matters beyond government. Because even though at the moment, the policy may apply directly to central government, the questions behind it apply to every organisation that relies on cloud services to communicate, serve customers and keep work moving:
What happens if a critical service is suddenly unavailable?
How quickly can we continue operating?
Can we move our data and communication without starting from zero?
Do we have an exit plan that works in practice, not just on paper?
This is where a shadow environment becomes more than a technical safeguard.
It is business continuity by design, with a practical exit route built in.
An independent, live environment that is already running while the day-to-day setup continues as normal. Not a rushed migration once something breaks, but a route out that exists before you need it.
And the market is beginning to organise around that same principle. The Open Cloud Alliance argues that Dutch and European cloud platforms built on open standards, open-source software and open architecture can give organisations more freedom to switch providers and reduce dependency without waiting for a perfect one-size-fits-all replacement.
That is the opportunity.
Not to tear everything out tomorrow.
To make sure you are never trapped inside what you use today.
The direction of travel is clear
The Dutch government is not the only one rethinking cloud dependency.
Across Europe, digital sovereignty is moving from a policy discussion to a practical requirement. Different countries are taking different routes, but the themes are increasingly the same: stronger control over critical services, more open and interoperable infrastructure, less dependence on a single foreign provider and clearer options when something needs to change.
France is accelerating its use of European sovereign cloud services for government, including initiatives such as the “cloud de confiance” framework, which promotes trusted cloud providers that meet strict security and sovereignty requirements. Germany is building a shared public-administration cloud around open standards and interoperability. Denmark is reviewing public-sector technology choices to reduce vendor dependence and increase awareness of alternatives, including its 2022 digital strategy, which explicitly highlights the need to avoid lock-in and strengthen digital sovereignty.
At EU level, the direction is becoming more concrete too. The European Commission has introduced a Cloud Sovereignty Framework, procured sovereign cloud services for EU institutions and proposed a wider framework for assessing cloud and AI sovereignty in critical sectors.
The details may differ from country to country. But the message is consistent: Organisations should not wait until a service fails, a contract changes or a dependency becomes a crisis before they start asking how they would keep working without it.
That is why a Plan B matters.
Not as a dramatic break from the tools you use today, but as a practical way to build options while everything is still working.
Build your route to sovereignty with Soverin
At Soverin, we help organisations build more control and continuity without forcing a disruptive migration.
We can help you start wherever it makes the most sense for your organisation: take control of your mailflow, add a live fallback/shadow mailbox, move towards sovereign identity, or shift towards a full digital sovereign workspace.
You do not have to start at the beginning or commit to replacing everything at once. You can address the risk that matters most today, while keeping your future options open.
At Soverin, the path to sovereignty is based on more than a product roadmap. It rests on privacy-first email expertise, self-owned Dutch infrastructure under EU jurisdiction, and a steward-owned model that puts business continuity and stakeholder interests ahead of short-term investor pressure. Our ISO 27001, ISO 9001 and ISO 14001 certifications reinforce that foundation, helping ensure security, quality and sustainability are managed as part of the service from day one.
To us, the goal has been simple since 2014: a practical Plan B today, and a clearer path to independence tomorrow.
Want to see which step makes sense for your organisation? Contact us today: sales@soverin.com