Digital sovereignty: governments are leaving Microsoft — where does an SME start?
Several European administrations are announcing migrations to open source. What the movement says, what it doesn’t, and a gradual approach for an SME.
In 2026, digital sovereignty is no longer a conference theme. According to the specialist press, France asked each ministry to present a strategy for moving its workstations to Linux systems by autumn, Bavaria dropped a framework agreement with Microsoft, and several German states replaced their collaboration tools with European open source solutions (FOSS Force). Figures quoted vary between sources; keep the direction rather than the totals.
What the movement says — and doesn’t
It says that dependence on a single vendor subject to non-EU law is now a risk that large organizations are willing to put a price on. It doesn’t say migration is simple: these projects stretch over years, with budgets, coexistence periods and the occasional step back. An SME has neither that scale nor that need for uniformity, which is an advantage: it can move block by block.
Define what "sovereign" means for you
The word covers three distinct things, to be separated before choosing:
- Jurisdiction: under which law is your data hosted, and who can demand access to it?
- Reversibility: can you export your data in an open format and change supplier without rewriting your business? (See how to spot vendor lock-in.)
- Operational control: do you know who administers your systems, and could you carry on without them?
Open source answers the second and third well; the first depends mostly on where you host it and who operates it.
A four-step approach
1. Map. List your tools, the data they hold and how critical they are. Many SMEs discover at this stage services quietly subscribed to by teams.
2. Start with low-friction blocks. Video conferencing (Jitsi), team messaging (Matrix and Element), the mail client (Thunderbird), open source office tools, telephony (Linphone): reversible migrations with limited business risk.
3. Then tackle the management core. ERP and CRM touch invoicing and accounting: migrate them with a data-recovery plan, a short double-entry period and user validation (Dolibarr versus a proprietary CRM).
4. Keep an exit plan. Even open source, a poorly documented solution makes you dependent on whoever installed it. Demand documentation, access and tested backups (the 3-2-1 rule).
Pitfalls to avoid
- Migrating out of ideology rather than risk. Replace first what exposes you most or costs you most.
- Underestimating change management. A technically superior tool that people don’t adopt is a failure.
- Confusing open with free. The saving is on licenses; operations and maintenance remain a real cost, which can be entrusted to a provider.
Sources
A question about your situation?
Take the self-audit — 93 questions, no sign-up — or ask for a free audit straight away: we’ll look at your specific case.