Case Study 2

Munich LiMux

Technical Success, Political Reversal, Renewed Commitment

CAUTIONARY TALE
15,000 Desktops targeted for migration
€11.7M Saved by 2014 ($16M USD)
84% Migration completion rate
15 years Linux use in city administration

Status

Completed (2004–2013) → Politically Reversed (2017–2020) → Open Source Preference Restored (2020–present)

Classification: Cautionary Tale — Demonstrates that technical success does not equal political sustainability.

Overview

Munich’s city administration executed a nine-year migration of 15,000 desktops from Windows and Microsoft Office to a custom Debian/Ubuntu-based operating system (“LiMux”) and LibreOffice. The project was completed successfully in 2013, saved €11.7 million, and operated effectively for four years. However, a 2017 political decision reversed the migration, citing productivity concerns. In 2020, a new city council restored open source preference, making Munich a complex case study in the political dimensions of government IT decisions.

Migration Timeline

Phases of the LiMux project, 2003–present
Phase Years Action Status
Planning 2003–2004 Business case development, vendor evaluation, legal review Completed
Pilot 2004–2006 Feasibility testing, custom tool development (WollMux) Completed
Migration 2006–2013 Phased rollout: LiMux OS + OpenOffice then LibreOffice 12,600 of 15,500 desktops completed
Operation 2013–2017 Sustained operation, continuous improvement Successful; support tickets below baseline
Political Reversal 2017–2020 City council votes to return to Windows Announced but not completed before 2020 election
Restoration 2020–present New city council cancels reversal, restores open source preference Policy restored

Technology Stack

Components deployed across the LiMux programme
Component Initial Solution Final Solution Notes
Operating System Debian-based LiMux Ubuntu-based LiMux Switched base distribution
Office Suite OpenOffice.org LibreOffice (Oct 2012) Switched after fork
Custom Tools WollMux WollMux Extended LibreOffice capabilities
Browser Mozilla Firefox Mozilla Firefox Standard browser
Email Various Mozilla Thunderbird Standardised

WollMux — Custom Document Management Tool

Developed in-house between 2005 and 2008, WollMux extended LibreOffice with capabilities essential for municipal administration:

  • Letterhead management
  • Form templates
  • Standard text blocks
  • Document versioning
  • Document merging

WollMux was released as open source in May 2008, enabling other organisations to benefit from Munich’s investment.

Quantitative Outcomes

  • €11.7 million saved by 2014 ($16 million USD)
  • Support ticket volumes fell below pre-migration levels
  • 12,600 of 15,500 targeted desktops migrated (84% completion)
  • Remaining 2,900 desktops maintained Windows for application dependencies
  • Maintained “conversion stations” — approximately 1 per 500 users

The 2017 Political Reversal

The Munich reversal is the single most cited example used to argue against government open source migration. A careful analysis reveals that technical success was not disputed — the reversal was driven by political factors and vendor lobbying, not by technology failure.

Political context

  • Deputy Mayor Josef Schmid (CSU) and Mayor Dieter Reiter (SPD) elected in 2014
  • Microsoft’s German headquarters relocated to Munich during this period
  • Timing coincided with political pressure to reverse the migration

Stated justifications

  • User productivity concerns
  • IT complexity
  • Application compatibility

Critical analysis

  • Technical success was not disputed. Support metrics demonstrated the system worked effectively.
  • OpenOffice compatibility issues were real but LibreOffice addressed many of these before the reversal decision.
  • Political factors dominated. The relocation of Microsoft’s German headquarters to Munich created significant lobbying opportunities.
  • Communication failure: insufficient stakeholder engagement left the project politically exposed.
Key lesson: Technical success alone does not guarantee political sustainability. Without legislative protection, cross-party consensus, and sustained stakeholder communication, even a demonstrably successful migration remains vulnerable to reversal.

The 2020 Restoration

  • New city council elected with Green Party and Social Democrats gaining influence
  • Reversal plan cancelled before implementation was completed
  • Open source preference restored for future procurements
  • 15 years of Linux use cited as proof of viability

Critical Success Factors (Technical)

  1. Custom tooling addressed real needs — WollMux solved genuine administrative requirements
  2. Comprehensive interoperability planning — conversion stations ensured no user was left without access
  3. Gradual migration — phased rollout minimised disruption
  4. Strong technical team — in-house expertise sustained the programme
  5. Support metrics proved success — measurable evidence of operational effectiveness

Critical Failure Factors (Political)

These political failure factors are more important than the technical success factors. Any future migration must address all five to avoid Munich’s fate.
  1. Insufficient communication strategy — technical team did not adequately engage political stakeholders
  2. Political change without binding commitment — no legislative or contractual protection against reversal
  3. Vendor lobbying opportunity — Microsoft’s headquarters relocation to Munich created direct influence channels
  4. Technical issues weaponised politically — minor compatibility problems amplified for political purposes
  5. Lack of cross-party consensus — migration was identified with one political faction rather than treated as non-partisan infrastructure

Document Compatibility Strategy

Template Conversion Programme

All administrative templates were audited, converted, simplified, and tested as part of the migration programme. This systematic approach ensured that the most frequently used documents were available from day one.

Macro Migration

Existing macros were assessed for necessity. Those still required were rewritten in LibreOffice Basic. Many legacy macros were found to be redundant and were retired.

Conversion Stations

Approximately 1 conversion station per 500 users was maintained. These were Windows PCs with Microsoft Office available for edge cases where full compatibility was essential.

Document Format Policy

The Open Document Format (ODF) was mandated for internal use. Microsoft formats were accepted from external correspondents and converted as necessary.

Less than 5% of documents required conversion station intervention. The vast majority of daily administrative work was handled entirely within LibreOffice.

Comparative Analysis: Why France Succeeded Where Munich Partially Failed

Factors distinguishing sustained success from political reversal
Factor France Gendarmerie Munich
Political Context National security / military Municipal government
Vendor Lobbying Vulnerability Low High (Microsoft HQ move)
Political Commitment Cross-government, sustained Single administration, not sustained
Communication Strategy Military command structure Insufficient political engagement
Legislative Foundation Implicit national security mandate None; vulnerable to reversal
Cost Savings Publicity Modest but sustained Larger but not leveraged politically
Outcome 17+ years sustained Technically successful but politically reversed then restored

Lessons Learned

For Technical Teams

  • Phased migration works — gradual rollout reduces risk and builds confidence
  • Custom tools add value — WollMux demonstrated that bespoke solutions can exceed vendor offerings for specific needs
  • Interoperability planning is essential — conversion stations eliminated the “can’t open this file” complaint
  • Support metrics matter — quantitative evidence of success provides the strongest defence
  • LibreOffice is superior to OpenOffice for government deployment — the fork improved compatibility significantly

For Political Stakeholders

Munich proves that getting the technology right is necessary but not sufficient. The following political lessons are equally critical for any government considering migration.
  • Technical success is not equal to political sustainability — operational excellence did not prevent reversal
  • Legislative foundation is protective — without statutory backing, policy changes with each election
  • Communication is as important as technology — stakeholder engagement must be continuous and proactive
  • Vendor lobbying is real — incumbent vendors will actively work to reverse migration decisions
  • Cross-party consensus is essential — migration must be positioned as non-partisan infrastructure policy

Sources

Related Documents