The Danish Digital Sovereignty Pilot Project and the Reality of Moving Away from Microsoft Office

The pursuit of digital sovereignty has become a central theme for European governments looking to reduce their reliance on foreign, closed-source technology stacks. In June 2025, the Danish Ministry of Digitalization initiated a high-profile pilot program aimed at testing the feasibility of replacing Microsoft Office—the industry-standard suite—with the open-source Collabora Office platform. While early media reports suggested a decisive, government-wide migration, the reality of the project proved far more complex, characterized by internal technical hurdles, political administrative changes, and a quiet conclusion that left the future of open-source adoption in the Danish public sector in a state of ambiguity.

The Genesis of the Pilot Program

The project was officially launched in the early summer of 2025 within the Danish Ministry of Digitalization. The objective was to integrate Collabora, an enterprise-ready version of LibreOffice, into the ministry’s existing infrastructure, specifically the F2 case and document management system maintained by the Danish firm cBrain. The goal was to determine if a public sector department could function efficiently using open-source alternatives to Word, Excel, and PowerPoint.

From its inception, the ministry was careful to manage expectations. Caroline Stage Olsen, the minister overseeing the initiative at the time, consistently emphasized that the project was a controlled, limited-scope test rather than an immediate abandonment of Microsoft software. Despite these clarifications, the narrative of "Denmark moving off Microsoft" gained significant traction in the international technology press, fueled by the broader European trend of favoring digital autonomy.

A Chronology of the Pilot

The timeline of the pilot is critical to understanding why the project eventually stalled. The following sequence outlines the progression and eventual dissolution of the initiative:

• June 2025: The pilot project begins with a group of volunteer employees in the Ministry of Digitalization. cBrain is tasked with the technical integration of Collabora into the ministry’s document management workflow.
• Late June 2025: Public reports circulate suggesting a full-scale migration to LibreOffice. The ministry issues clarifications, confirming that no decision has been made to phase out Microsoft or transition the ministry’s operating systems to Linux.
• October 2025: An internal evaluation workshop is held. Correspondence obtained via records requests indicates significant friction, with testers reporting formatting issues and interoperability gaps when interacting with external agencies.
• December 2025: Media reports highlight the frustrations of the testers, citing "blank" documents and erratic line spacing as primary technical pain points.
• February 2026: A surprise election is called, leading to a major cabinet reshuffle.
• June 2026: The new government takes office, effectively dismantling the Ministry of Digitalization as a standalone entity. The ministry’s responsibilities are merged into the Ministry of Research and Education.
• October 2026: The project is confirmed to be defunct, with no plans for further rollout or formal evaluation.

Technical Hurdles and User Experience

The challenges encountered during the pilot were largely centered on document interoperability. In a public sector environment, the seamless exchange of files between different government agencies and the public is a requirement for operational continuity. Testers reported that documents created or edited in Collabora often suffered from formatting degradation when opened in standard Microsoft Office environments. Specifically, "track changes" features—a staple of legal and administrative review—were described as difficult to navigate, and document layouts, including line spacing and margins, frequently shifted.

These technical difficulties are not unique to the Danish pilot; they are well-documented challenges in any organization attempting to migrate from a proprietary ecosystem to an open-source alternative. Proprietary formats often include undocumented features or specific rendering instructions that standard open-source tools must interpret, which can lead to inconsistencies. While Collabora engineers worked to address these specific tickets—an effort the company noted they funded themselves—the learning curve and the "friction of change" became significant barriers to employee adoption.

Differing Perspectives on the Conclusion

The reason for the project’s termination remains a point of contention between the ministry’s communications office and the technology vendors involved. According to the ministry, the project was essentially left in limbo due to the election and the subsequent administrative reorganization. The ministry maintains that because the department tasked with the pilot was absorbed into a larger entity, the original mandate for the evaluation became obsolete, and staff eventually reverted to their previous software suites without an official "sunset" ceremony.

Collabora, however, presents a more nuanced defense of the project’s outcome. They argue that the pilot was not a failure of the software itself, but a victim of political timing. Collabora asserts that the first phase of the integration was successful, that technical bugs were being actively managed, and that the project should not be characterized as a rejection of their suite. They view the work performed during the pilot as a valuable investment that has already begun to pay dividends in other partnerships with Danish authorities, suggesting that the "hard work" of integration has already been done, even if the specific ministry pilot did not reach a formal conclusion.

The Broader Implications for Digital Sovereignty

The Danish experiment serves as a microcosm for the challenges facing European states in the digital age. Digital sovereignty—the ability of a state to control its own digital infrastructure and reduce reliance on third-party providers—is an attractive policy goal, but it is frequently tempered by the realities of technical inertia and the high costs of switching ecosystems.

The incident highlights several key lessons for future projects:

1. Interoperability is the Primary Barrier: Even when an open-source tool is functionally equivalent, the dominance of proprietary file formats (like .docx and .xlsx) creates a "network effect" that makes migration difficult for any single department acting in isolation.
2. Administrative Stability is Required: Large-scale digital transitions require long-term political and administrative commitment. As seen in the Danish case, a change in government or a department merger can effectively kill a project before it has the opportunity to yield data or reach a maturity stage.
3. Transparency in Public Procurement: The discrepancy between initial media reports and the actual, limited scope of the pilot underscores the need for clearer communication from public bodies. When "pilot" is conflated with "government-wide policy," it creates a skewed perception of success or failure that can ultimately hinder future, better-resourced initiatives.

Data and Infrastructure Context

In 2026, the cost of licensing proprietary office suites for government employees represents a significant portion of IT budgets. While exact figures for the Danish Ministry’s Microsoft spend remain proprietary, similar European government contracts often run into the millions of Euros annually. The promise of open source is to claw back a portion of this expenditure while gaining transparency and security.

However, the cost of migration is not just the software license; it includes staff retraining, technical integration (such as the work performed by cBrain), and the potential productivity loss during the transition phase. The Danish experience suggests that unless these costs are calculated against a multi-year horizon and backed by sustained political support, the path of least resistance—continuing with the incumbent provider—remains the default choice for civil servants.

The Legacy of the Pilot

Ultimately, the Danish pilot concluded without a definitive victory for either side of the debate. It did not definitively prove that open-source software is unsuitable for government work, nor did it successfully demonstrate a seamless migration process. Instead, it highlighted the complexity of moving away from entrenched software ecosystems.

For the Danish government, the focus appears to have shifted toward other digital priorities following the merger of the digitalization ministry. For the open-source community, the episode provides a blueprint of what to expect when entering the complex, highly interconnected world of public sector IT. The technical work completed by Collabora and the lessons learned regarding the F2 document system integration may yet form the basis for future projects, but for now, the episode stands as a reminder that technological shifts in government are rarely just about the software; they are about the interplay of politics, procurement, and the often-frustrating reality of legacy document standards.

As governments across the globe continue to grapple with the tension between convenience and sovereignty, the Danish project will likely be cited as a case study in how not to manage expectations, and perhaps more importantly, as a testament to the fact that even the most well-intentioned digital initiatives are subject to the unpredictable nature of political and administrative change. Whether Denmark will attempt a similar transition in the future remains to be seen, but the current consensus is one of caution, focusing on stability over radical infrastructure shifts.