3 6 Ke·2025-11-28 11:34Core Viewpoint - Airbus's ambitious plan to migrate 130,000 employees from Microsoft Office to Google Workspace has faced significant challenges, leading to a prolonged and complex transition process that remains incomplete after several years [1][6]. Migration Plan - The migration aimed to eliminate local deployment of Office and transition to cloud-based digital tools, marking a new phase in the company's digital transformation [3]. - Former CEO Tom Enders emphasized the need for modern digital tools to support new collaborative work methods and promised employee support and training for the transition [3][5]. Challenges in Migration - The initial estimate of completing the migration within 18 months was overly optimistic, as acknowledged by Airbus's digital transformation executive [6]. - As of now, Airbus has grown from 130,000 to 150,000 employees, with over two-thirds having switched to Google tools, yet many teams still rely on Microsoft software [7]. Reasons for Incomplete Migration - Excel's Unmatched Capability: Excel remains essential for handling large datasets, with some financial spreadsheets containing up to 20 million cells, far exceeding Google Sheets' capabilities [8][9]. - Advanced Document Management Needs: Teams such as legal and procurement require robust document management features that Google Workspace currently lacks [10]. - Regulatory and Data Security Constraints: Certain confidential documents cannot be stored in the cloud, necessitating continued use of local solutions [11]. Current State and Issues - Airbus is currently in a hybrid state, using both Google and Microsoft tools, which has led to increased costs and compatibility issues [11]. - Employees have reported frustrations with document format inconsistencies and collaboration conflicts due to the dual-tool environment [11]. Broader Implications - The migration challenges highlight that transitioning to new software is not merely a technical issue but a complex system-wide endeavor involving process reengineering and cultural shifts [12]. - The experience raises questions about the feasibility of replacing established software ecosystems, especially when existing solutions meet specific operational needs [12][13].