A woman reviews marked-up documents at her desk beside a checklist and Danish flag.
Denmark’s Ministry of Digitalisation has ended its pilot of Collabora as a Microsoft Office alternative, with no plans to restart it and no completed evaluation. Employees reportedly encountered document-formatting and tracked-change problems, but the available reporting does not establish that those difficulties caused the cancellation—or that Denmark has abandoned every effort to reduce its Microsoft dependence.

For IT administrators, that distinction matters. A stopped experiment is not the same thing as a measured verdict on an office suite.

A woman reviews marked-up documents at her desk beside a checklist and Danish flag. What Denmark actually stopped​

According to Dutch public-sector publication iBestuur, citing Denmark’s Computerworld, the trial began in summer 2025 with 38 ministry employees. Collabora was connected to F2, the case-management system supplied by Danish vendor cBrain. Document exchange was therefore part of an operational workflow, not merely a contest between word processors.

iBestuur reports that the experiment stopped when elections were called in spring 2026. A ministry spokesperson confirmed that it would not resume and that the planned evaluation had not happened. Reported difficulties included blank pages, formatting and tracking changes. Without that assessment, their severity, resolution and role in the decision remain unclear.

The original ambition was broader. In June 2025, The Record reported that then-digitalisation minister Caroline Stage Olsen planned to move more than half the ministry’s staff from Microsoft Office to LibreOffice the following month, with a wider open-source transition intended by year-end. Crucially, that reporting also said the ministry could return to Microsoft products if the transition proved too complicated.

Those earlier LibreOffice plans and the later Collabora pilot should not be treated as identical deployments. Nor does the reporting establish a completed nationwide Windows-to-Linux migration that has now been reversed.

Compatibility is more than a file extension​

There is an important technical correction to the idea that Collabora uses OpenDocument Format while Microsoft Office uses something entirely inaccessible to it: Collabora supports Microsoft formats too. Its published FAQ lists DOCX, XLSX and PPTX alongside older Office formats. Supporting a format, however, is not a promise that every document feature will survive every editing workflow unchanged.

Microsoft’s own documentation supplies a concrete example. Its compatibility guidance for Word for Microsoft 365, Word 2024 and several earlier releases says that saving a Word document as OpenDocument Text (.odt) accepts all tracked changes. That is a documented limitation of that particular Word save operation—not a diagnosis of what happened inside the Danish ministry.

Microsoft also warns that some positioning and section-break properties can change when saving to .odt. A document may therefore retain its words while losing aspects of its layout or editing behavior. That distinction matters when the deliverable is an editable official document rather than a page that merely looks correct on screen.

The practical takeaway is not “ODF is broken” or “Office files cannot be exchanged.” It is that compatibility needs to be tested against the actual application, format and sequence of edits involved. The documented Word limitations illustrate why format conversion deserves its own test cases; they do not prove the cause of Denmark’s reported problems.

What administrators should take from the pilot​

For organizations considering an Office alternative, our recommendation is to make the evaluation a required deliverable before the pilot begins. A migration should not have to survive on recollections of whether the spreadsheets seemed happy.

A useful assessment would include:

  • Representative documents: Test real templates, long reports, tables and frequently exchanged files—not just newly created samples.
  • Round-trip editing: Open, edit, save and reopen documents in both suites, using copies rather than production originals.
  • Review workflows: Check whether comments and tracked revisions retain the behavior your approval process requires.
  • Business-system integration: Test document retrieval, editing and storage through the systems employees actually use.
  • Recorded outcomes: Log application versions, file formats, reproducible failures, attempted fixes and time spent correcting documents.
  • Explicit acceptance criteria: Decide beforehand which defects are tolerable, which require a workaround and which block deployment.

These are recommended evaluation practices, not claims about tests Denmark performed. In particular, administrators should treat a Word-to-ODT conversion as a separate scenario from exchanging a DOCX file: Microsoft documents specific feature changes associated with that conversion.

An unanswered question, not a universal verdict​

The defensible conclusion is narrower than “Denmark tried to quit Microsoft and failed.” One ministry ended a Collabora pilot without completing its evaluation. That leaves insufficient evidence to judge either the alternative’s suitability in that environment or the feasibility of a broader migration.

Our assessment is that the missing evaluation is the most consequential part of the story. Stopping an unsuitable deployment can be sensible; continuing a promising one can be equally sensible. What other IT teams need is the evidence that distinguishes the two—not another trophy for either side of the office-suite argument.


Update: Collabora says pilot issues were resolved and work continues (October 30, 2026)​

Collabora says its engineers investigated and resolved the issues reported during the Danish ministry’s pilot, according to a company statement reported by XDA Developers. The company says it provided engineering and quality-assurance work at its own expense.

The vendor also says testing paused before a second phase because of a government reshuffle, not because of the software’s quality. Its account does not establish that the ministry’s pilot will restart: the ministry previously said it would not resume and had not completed an evaluation.

Collabora says it is working with F2 supplier cBrain to deploy the software to other Danish public authorities. The company also says the pilot let participants switch between Collabora and Microsoft Office while using Microsoft’s file format.

For administrators, the claimed fixes are relevant, but the statement does not provide a completed ministry evaluation or enough detail to independently assess how well the corrected workflows performed. XDA Developers says it has asked Denmark’s Ministry of Digital Affairs to verify Collabora’s claims.

 

References

  1. Denmark has abandoned plans to ditch Microsoft Office after technical problems Neowin 2026-10-25T00:44:01+00:00
  2. Collabora hits back at claims that Denmark ditched it, saying its problems were fixed long ago XDA 2026-10-30T15:18:32+00:00
  3. Denmark ditches its plan to replace Microsoft Office with Collabora because it wasn't working with OOXML files XDA 2026-10-25T02:56:37+00:00