Sovereignty & Microsoft-Exit

Independent advice on whether and how to leave M365. Separate from doing the migration. Given the EU climate, it's a question worth answering deliberately before you move.

When you need this

Sound familiar?

  • Every M365 renewal makes the dependence feel heavier.
  • A client or regulator asked where your data is processed, and the honest answer is complicated.
  • The US cloud debate has reached your management, and someone has to answer it properly.
  • You want to know what leaving would actually cost, without a vendor doing the math.

Why it matters

Leaving M365 is a big, expensive decision that vendors are happy to make for you. Independent advice tells you whether it's even worth doing before you spend a cent.

How it works

The service, explained.

Decide before you commit

We give independent advice on whether leaving Microsoft 365 makes sense for you at all, with the risk, cost, and timeline laid out plainly. This is deliberately separate from doing the migration, so the advice has no stake in the answer.

A realistic path if you go

If you decide to move, we map an exit that accounts for email, identity, files, and the dozen smaller dependencies people forget. You go in knowing what it takes rather than discovering it halfway through.

What you get

What's included

  • Independent advice on whether to leave M365 at all
  • A realistic exit path if you decide to move
  • Separate from the migration itself. No vendor bias
  • Risk, cost, and timeline laid out before you commit

The process

The flow, end to end.

Step 1
Inventory
What you actually use in M365: identity, mail, files, and the hidden hooks.
Step 2
Weigh
Cost, risk, and effort of leaving versus staying, in numbers.
Step 3
Decide
A recommendation you can defend either way, with the reasoning.
Step 4
Path
If you go: a staged exit plan. If you stay: the leverage you still have.

Pricing

from €1,900 one-time

Net, plus 19% VAT.

See full pricing

FAQ

Common questions.

Is the answer always to leave?

No, and that is the point of separating advice from migration. Staying, partial exits, and full exits all come out of this work; the recommendation follows the numbers, not a service we want to sell afterwards.

What are the usual alternatives?

European suites and self-hosted stacks for mail, files, and collaboration, and the realistic answer is often a mix. Identity is the hard part, and the plan treats it that way.

How disruptive is an exit for staff?

That depends on what you actually use, which is exactly what the assessment quantifies. Mail moves quietly; deeply embedded Teams and SharePoint workflows do not, and knowing that in advance is what the plan is for.

We only want the assessment, not the move. Is that fine?

Yes, it is deliberately sold separately. The assessment stands on its own, and whoever does the eventual migration can work from it. Us included, but not required.

Book a free infrastructure assessment.

A no-commitment look at your setup. What's healthy, what's at risk, and what to fix first. Real answers, no pressure.