Consolidated Analysis

Critical Success Factors

Analysis of 10 European government migrations spanning 2004–2026 reveals five critical success factors that consistently determine whether a migration succeeds or fails. These factors are drawn from both successful deployments (France, Schleswig-Holstein, Italy) and instructive failures (Munich’s political reversal).

1

Multi-Year Political Commitment

Evidence from Case Studies

  • SUCCESS France: 17+ years of sustained operation across multiple governments, demonstrating that political commitment can outlast individual administrations when properly embedded
  • CAUTION Munich: Technical success but political reversal when commitment was lost following a change in city leadership
  • SUCCESS Schleswig-Holstein: Minister Dirk Schroedter’s public commitment creates accountability, making reversal politically costly
  • SUCCESS Switzerland: Legislative foundation (EMBAG Law) ensures sustained commitment regardless of political changes

Requirements

  • Executive or ministerial sponsorship (not just IT leadership)
  • Cross-party support where possible (Munich lesson: single-party ownership is vulnerable)
  • Legislative foundation or binding mechanism (Switzerland and Estonia examples)
  • Public communication creating accountability (Schleswig-Holstein model)
Failure Mode: Munich demonstrated that technical success is insufficient if political commitment wavers. When the political leadership changed and questioned the project, technical achievements were ignored in favour of political reversal.
2

Phased Application-First Approach

Evidence from Case Studies

  • SUCCESS France: OpenOffice (2004–2006), then Firefox/Thunderbird (2006–2008), then Ubuntu (2008–2013). A 9-year timeline with a 2-year gap between applications and OS migration
  • SUCCESS Schleswig-Holstein: Office (2021–2024), then Email (2024–2025), then Collaboration (2025–2026), then OS (pilot). A 4+ year timeline with the OS migration not yet committed
  • SUCCESS Italy Defence: Office suite only, 14 months, 150,000 users. Rapid success because the scope was focused on a single component
  • CAUTION Munich: Good phasing overall but OpenOffice compatibility issues created problems; the switch to LibreOffice was delayed until 2012

Why This Approach Works

  • Users adapt to one change at a time
  • Training is more effective when not overwhelming
  • Early wins build confidence across the organisation
  • Testing and learning occur between phases
  • Fallback is easier if applications still work on Windows

Optimal Migration Sequence

Phase 1: Office Productivity (6–12 months)
MS Office to LibreOffice, running on Windows. This is the lowest-risk starting point and addresses the most visible change for end users.

Phase 2: Email and Collaboration (6–12 months)
Exchange/Outlook to Open-Xchange + Thunderbird, SharePoint to Nextcloud. Still running on Windows to limit disruption.

Phase 3: Messaging and Video (3–6 months)
Teams to Matrix/Element + Jitsi. Still running on Windows. Typically a smaller change as these tools are less deeply embedded in workflows.

Phase 4: Operating System (12–24 months, optional)
Windows to Ubuntu/openSUSE. Only commenced after Phases 1–3 are complete and stable. This is the highest-risk phase and is not required for significant cost and sovereignty benefits.

Critical Gap: France’s 2-year gap between office suite migration and OS migration was key to success. Schleswig-Holstein is following a similar pattern with 3+ years between office suite and OS pilot. A minimum 18-month gap between application migration completion and OS migration commencement is recommended.
3

Comprehensive Training Programmes

Evidence from Case Studies

  • SUCCESS Italy Defence: Explicit comprehensive training for 150,000 users was identified as a critical success factor in the rapid deployment
  • SUCCESS The Document Foundation Protocol: Training identified as a “fundamental step” and “one of the steepest barriers to adoption”
  • SUCCESS Munich: Support tickets fell below the baseline after training and adaptation periods were completed
  • CAUTION France: Minimal training worked in a military context with strong hierarchical compliance, but this approach may not be replicable in civilian government settings

Training Requirements by Role

Role Training Duration Content Focus Timing
Executive Leadership 2–4 hours Strategic rationale, organisational impacts 6 months before migration
Middle Management 4–8 hours All executive content plus workflow implications 3 months before migration
Technology Leaders 16–24 hours Advanced technical, support skills, train-the-trainer 2 months before migration
IT Support Staff 24–40 hours Comprehensive technical, system administration, troubleshooting 1–2 months before migration
End Users 4–8 hours Practical task-focused, differences from Microsoft products Within 1 week of deployment
Critical Rule: Users must have the software installed and accessible immediately after training. Delays between training and tool availability dramatically reduce effectiveness. Schedule training sessions to coincide precisely with each department’s deployment date.

Training Content Principles

  • 90% of users need only basic features – focus training accordingly
  • Highlight differences from Microsoft products rather than teaching from scratch
  • Emphasise ODF format benefits for long-term document preservation
  • Hands-on practice is essential; lecture-only training consistently fails
  • Job aids and quick reference guides provide critical post-training support

Investment Required

Component Estimated Cost
Budget per end user (comprehensive training) €200–400 per user
Time per end user 4–8 hours
Resources required Trainers, training materials, online resources, help desk enhancement
Failure Mode: Inadequate training leads to user frustration, productivity loss, workaround behaviours, support ticket overload, and political vulnerability. Training is the single most important investment in a migration programme.
4

Technology Leaders / Champions Programme

Evidence from Case Studies

  • SUCCESS The Document Foundation Protocol: Explicit recommendation for a technology leaders network as part of any migration programme
  • SUCCESS Munich: Middle managers and employees mixed in the leadership group provided effective peer support throughout the migration
  • SUCCESS France: Core team of IT experts led the technical architecture, providing a permanent knowledge base within the organisation

Why It Works

  • Peer support is more effective than formal help desk interactions
  • Reduces support ticket volume significantly
  • Builds user confidence through trusted colleagues
  • Creates positive social proof for the migration
  • Serves as an early warning system for emerging issues
  • Provides a direct feedback loop to the project team

Implementation Model

  • Ratio: 1 technology leader per 25–50 users
  • Role mix: Administrative, technical, and management staff
  • Selection: Volunteers, not assigned – enthusiasm is essential
  • Standing: Respected by peers within their teams
  • Recognition: Compensated or formally recognised for their contribution

Timeline

Activity Timing Detail
Identify and recruit 3–6 months before migration Call for volunteers, selection, role definition
Train technology leaders 2 months before migration 16–24 hours of intensive training
Early access 2–4 weeks before department rollout Leaders receive software before their colleagues
Active support During rollout and 3–6 months after Regular meetings, issue resolution, positive advocacy
Ongoing community Indefinitely Bi-weekly meetings during migration, monthly during steady-state

Activities

  • Regular meetings (bi-weekly during migration, monthly during steady-state)
  • Share experiences and collaborative problem-solving
  • Provide structured feedback to the project team
  • Champion role: positive advocacy for the migration across their teams

Cost Estimate for a 10,000-User Organisation

  • Technology leaders needed: 200–400
  • Training investment (one-time): €100,000–400,000
5

Document Compatibility Strategy

Evidence from Case Studies

  • SUCCESS Munich: Maintained “conversion stations” for complex documents, achieving less than 5% of documents requiring intervention
  • SUCCESS The Document Foundation: Explicit template conversion and testing strategies are documented in their migration protocol
  • CAUTION Munich: OpenOffice compatibility issues were cited as an ongoing problem; the LibreOffice switch came too late to prevent user frustration
  • CAUTION Multiple migrations: Document compatibility issues are frequently cited as the most visible challenge in post-migration surveys

The Challenge

Complex Microsoft Office documents (macros, advanced templates, embedded objects) occasionally render incorrectly in LibreOffice. External partners send MS Office documents. Government templates often use advanced formatting features. These issues, whilst affecting only a minority of documents, are highly visible and can undermine confidence in the entire migration.

Compatibility Reality

Document Type Compatibility Rate Notes
Simple documents 95–99% Standard text, tables, basic formatting
Complex documents 80–90% Advanced formatting, embedded objects, conditional fields
Legacy formats Good LibreOffice often handles old .doc files better than modern MS Office
VBA macros Not supported Must be rewritten in LibreOffice Basic or Python

Solution Framework

  1. Template Conversion Programme
    Audit all organisational templates, retire obsolete ones (often 50%+), convert remaining to ODF, simplify where possible, and test thoroughly.
  2. Macro Migration
    Inventory all VBA macros, assess necessity (many are no longer needed), rewrite essential macros in LibreOffice Basic or Python, test rigorously, and document the new implementations.
  3. Conversion Stations (Munich Model)
    Provide 1 station per 500 users – Windows PCs with MS Office for edge cases. Establish a defined workflow for documents requiring external format compliance.
  4. Document Format Policy
    Adopt ODF as the internal standard, accept MS formats from external partners, and export to MS formats when required by external recipients.
  5. Compatibility Testing Programme
    Test all critical documents before migration begins, identify and resolve problems during the pilot phase, and maintain a known-issues register.
  6. User Guidelines
    Publish interoperability guidelines, best practices for document creation, and format recommendations for different use cases.

Success Metrics

  • Less than 5% of documents require conversion station intervention (Munich achieved this target)
  • Less than 10% of support tickets relate to document compatibility
  • Increasing acceptance of ODF by external partners over time

Investment Required

Component Estimated Cost
Template conversion €50–150 per user (one-time)
Conversion stations Approximately €1,500 per station
Testing resources 1–2 FTE during migration
User guidelines development €20,000–50,000
Failure Mode: Ignoring document compatibility leads to user revolt, productivity loss, political vulnerability, and workaround behaviours that undermine the entire migration.

Sources

Related Sections

  • Implementation Playbooks – Practical guidance for applying these success factors in a migration programme
  • Governance Model – Organisational structures that sustain political commitment and institutional continuity
  • Risk Register – Detailed risk assessment including mitigation strategies derived from these case studies
  • Programme Execution – End-to-end programme management incorporating all five success factors
  • Migration Case Studies Overview – The 10 European government migrations from which these factors are drawn
Previous ← Proven Technology Stacks
Back to Overview Migration Case Studies →