Case Study 4

Denmark — Digital Sovereignty as Ministerial Priority

PRAGMATIC PILOT

Denmark’s Ministry of Digitalisation is executing an office suite migration from Microsoft Office 365 to LibreOffice, explicitly framed as achieving “digital sovereignty” in response to geopolitical risks. Separate parallel initiatives in Copenhagen and Aarhus are pursuing similar migrations. Minister Caroline Stage Olsen explicitly stated that “if the transition becomes too challenging, we can switch back to Microsoft without delay.”

Status: Active migration (Mid-2025 start, Autumn 2025 ministerial completion target)

Classification: Pragmatic Pilot — Ministerial-level testing with explicit fallback plan

Ministry-level Pilot scope
Office 365 to LibreOffice
Explicit Fallback plan
European Part of wider movement

Strategic Context


Strategic Drivers

  1. Digital Sovereignty: Control over government data and systems
  2. Geopolitical Risk Mitigation: Reduce vulnerability to US political decisions
  3. Cost Savings: Windows 10 end-of-life (October 2025) creating forced upgrade decision point
  4. Dependency Reduction: Less reliance on single foreign vendor
  5. European Leadership: Demonstrate digital autonomy

Migration Scope

Ministry of Digitalisation

Phase Timeline Users Technology Change Status
Phase 1 Summer 2025 50% of ministry staff Office 365 to LibreOffice In Progress
Phase 2 Autumn 2025 100% of ministry staff Complete transition Target

Municipal Initiatives

Copenhagen and Aarhus are separately and independently pursuing similar migrations.

Warning Important Clarification: Initial reporting suggested full Windows-to-Linux migration. The Danish government clarified that Windows will remain on many devices. The primary change is Office 365 to LibreOffice, not an operating system migration.

Technology Stack

Component From To Status
Office Suite Microsoft Office 365 LibreOffice Deploying
Operating System Windows Windows (mostly retained) No change for most
Windows Linux (some instances) Specific use cases
Cloud Services Microsoft 365 cloud Unclear Not detailed publicly

Risk Management and Contingency Planning

Explicit Fallback Plan

“If the transition becomes too challenging, we can switch back to Microsoft without delay.”
— Minister Caroline Stage Olsen

Contingency Characteristics

  1. Microsoft licences maintained during transition
  2. Dual capability period: both systems available
  3. Decision authority clear: Minister can authorise reversion
  4. No “burning bridges”: preserve ability to return

Psychological and Political Benefits

Potential Downsides


Contingency Approach Comparison

Government Contingency Approach Outcome
France No public fallback plan; military directive 17+ years sustained
Munich No planned fallback; political reversal forced it Reversed 2017, restored 2020
Denmark Explicit fallback plan TBD (in progress)

Copenhagen and Aarhus Municipal Context

“Political fallout could lead to inability to send emails or communicate internally.”
— Copenhagen municipality, framing Microsoft dependency as a potential single point of failure in a geopolitical crisis

Both Copenhagen and Aarhus are independently pursuing their own migrations away from Microsoft products, citing geopolitical risk as a primary motivator. These municipal initiatives are separate from the Ministry of Digitalisation’s programme but represent a broader Danish trend towards digital sovereignty.


Comparison to Schleswig-Holstein

Factor Schleswig-Holstein Denmark
Scope Comprehensive (office, email, collaboration, messaging, OS pilot) Limited (primarily office suite)
Scale 90,000 users Hundreds (single ministry)
Timeline 4+ years (2021–2025+) 6 months (mid-2025 to autumn 2025)
Commitment High; minister publicly vocal Moderate; explicit fallback plan
Governance OSPO, Innovation Hub Not disclosed
Legal Foundation GDPR compliance requirement Policy decision (no legal mandate)
Economic Framing Explicit economic development Cost savings mentioned, not emphasised

Denmark is taking a more cautious, incremental approach — which may reflect smaller initial scope, the pilot nature of the programme, consensus-oriented political culture, and lower risk tolerance.


Current Status (January 2026)


Lessons Learned (Preliminary)

Strengths

Weaknesses


Future Scenarios

Scenario 1: Ministry Success Leading to Expansion

OPTIMISTIC

The ministry pilot succeeds, demonstrating that LibreOffice can replace Office 365 for standard government work. Other ministries adopt the approach, and the Copenhagen and Aarhus initiatives reinforce the national momentum. Denmark becomes a Nordic exemplar for digital sovereignty.

Scenario 2: Ministry Success, Limited Expansion

MODERATE

The ministry completes its migration successfully but the approach does not expand significantly beyond the initial pilot. Other ministries cite different requirements or higher complexity. The initiative remains a valid proof of concept but does not catalyse broader change.

Scenario 3: Challenges Leading to Fallback Invoked

CAUTIONARY

Compatibility issues, user resistance, or integration problems prove more challenging than anticipated. The Minister invokes the explicit fallback plan and the ministry returns to Microsoft. The outcome is cited as evidence that migration is impractical, potentially discouraging other governments.

Scenario 4: Quiet Deferral

REALISTIC?

The initiative loses political momentum without a formal announcement. The autumn 2025 target passes quietly, the ministry continues with a mixed environment, and the programme is neither completed nor officially abandoned. Given the lack of public updates as of January 2026, this scenario cannot be ruled out.


Sources


Related Documentation