The Danish Government's Office 365 Retreat Is a Lesson for Every Indie Hacker

Open-source evangelists have been predicting the death of Microsoft Office for two decades. The Danish government just gave that prediction a quiet, bureaucratic burial. According to a report from Computerworld Denmark, the Ministry of Digitalisation has silently dropped its large-scale plan to replace MS Office with an open-source alternative—no announcement, no fanfare, just another migration that didn't survive contact with reality.

But here's the thing: this isn't a story about government inefficiency. It's a story about incentives, user psychology, and the invisible moat that proprietary software builds around itself. And for indie hackers, it's a goldmine of product insights.

The easy take is that open source lost. The more useful take is that the migration failed for predictable reasons—reasons that anyone can see coming if they look at the right data. PainSignal tracks dozens of these problems across industries, and the Danish case lines up almost perfectly with what the data says.

The resistance problem

Ask any IT director why migrations fail, and they'll tell you: people hate change. That's not a platitude; it's a measurable pain point. In our dataset, one of the most common complaints is "Users resist switching to new collaboration tools" with a severity rating of 4.2 out of 5. That's not a mild annoyance. That's a full-blown organizational crisis waiting to happen.

The Danish government isn't unique here. Across all industries, we've logged 12 separate problems specifically about open-source office suite adoption—spanning government, education, and enterprise. The average severity is well above 3.0, which means these aren't theoretical gripes. They're daily frustrations with real costs.

The compatibility moat

There's a less obvious but more durable barrier: file format lock-in. Open-source suites have come a long way, but they still struggle with complex documents. Macros break. Templates glitch. Rendering is inconsistent. We track multiple problems around these issues, with severity ratings between 3.8 and 4.0. When a government agency has thousands of Excel spreadsheets with embedded VBA scripts, switching to LibreOffice isn't a software change—it's a rebuild.

Microsoft understands this perfectly. Every new feature that uses proprietary formats, every integration with SharePoint, every auto-save to OneDrive reinforces the moat. The Danish government didn't just abandon open source; they realized that the cost of migration outweighed any licensing savings within a single budget cycle.

What the article missed

The Computerworld piece, while solid, focuses on the decision itself. It doesn't explore the underlying user-centric issues that make such migrations so fragile. And that's where the opportunity lives.

When the Danish government tried and failed, they left behind a list of unsolved problems. Those problems are not confined to Denmark. They're global. And they're not going away.

For an indie hacker, this is a signal. Build something that solves one of these specific pain points, and you've got a market that's already proven to pay for solutions. Here are three areas worth exploring:

Migration compatibility layers. A tool that automatically converts complex Office documents to open formats without breaking macros or templates. We already see 5 reports of "Lack of training resources for open-source office software" with average severity 3.6—suggesting training alone won't fix the technical gaps.
Change management SaaS. Software that helps organizations track and reduce user resistance before migration, not after. Since "Users resist switching to new collaboration tools" is severity 4.2, a pre-migration assessment tool could sell to any large enterprise eyeing a switch.
Format-agnostic collaboration. The future isn't replacing one office suite with another. It's making the suite irrelevant. Tools that work across Google Workspace, Microsoft 365, and LibreOffice without friction have a built-in advantage. The problem "Inconsistent rendering of complex documents across office suites" (severity 3.8) is a clear demand signal.

The real lesson

The Danish government's retreat isn't a failure of open source. It's a failure of migration strategy. They tried to swap the engine while the car was moving, and they didn't account for the passengers screaming from the back seat.

For builders, the message is simple: don't try to replace Microsoft Office. Build the bridges that make replacement possible. The market is already telling you what hurts. Listen to the pain.

And if you're sitting on an idea that addresses any of these problems, now's the time. The Danish government just gave you the clearest case study in years.