The UK Cabinet Office has handed its faltering migration from Google Workspace to Microsoft 365 to a shared government service, slashing the project’s projected whole-life cost from £51 million to £23 million. But the move hasn’t erased the programme’s Red delivery confidence rating, with pilot delays and resourcing gaps threatening the long-anticipated shift for around 15,000 users. As first reported by The Register, the revised plan outsources platform delivery to the Integrated Corporate Services (ICS) managed by the Department for Energy Security and Net Zero (DESNZ), abandoning an earlier bespoke build.

What Actually Changed: From Bespoke Build to Shared Service

Until recently, the Cabinet Office intended to construct its own departmental IT platform and manage the migration internally under the Falcon programme. That strategy has been overturned. Following a review recorded in the Government Major Projects Portfolio (GMPP), the department concluded that designing and building everything in-house was not the most cost‑effective option.

Approved now: the Cabinet Office’s digital services will move into ICS, a central shared service already operated by DESNZ. The programme’s whole‑life cost estimate has tumbled from roughly £50–52 million to approximately £23 million. According to authorities, savings come from avoiding the expense of a bespoke platform build and from securing “migration resource from Microsoft and partners at no investment cost.” That phrase suggests that Microsoft and delivery partners will provide migration assistance under existing enterprise or inter‑departmental arrangements, reducing immediate capital outlay.

There’s a trade‑off. The Infrastructure and Projects Authority’s replacement, the National Infrastructure and Service Transformation Authority (NISTA), says the project “will take a bit longer to complete.” The pilot phase, originally due earlier, is now projected for completion by September 2025. And NISTA’s delivery confidence assessment for Falcon remains Red—a stark signal that successful delivery is unachievable unless fundamental changes are made.

What It Means for You—Across the IT Spectrum

For IT Administrators and Migration Specialists

If you manage or plan large‑scale cloud migrations, the Falcon programme is a live case study in everything that makes a Workspace‑to‑M365 move complex. It’s not a simple data copy. The Cabinet Office’s environment includes email, calendars, contacts, shared drives, retention policies, and likely thousands of user‑created automations. Mapping Google’s collaboration model (Docs, Sheets, Shared Drives) onto SharePoint Online, OneDrive, and Teams requires careful design. Permissions, external sharing, and content classification often don’t map one‑to‑one, and history shows that over‑sharing incidents spike during migration windows.

Security and compliance are another hot spot. The Cabinet Office handles Official‑level information and must meet Government Security Group and NCSC standards. Moving to a central government M365 tenant can simplify baseline security, but it also demands rigorous configuration to ensure data residency, retention, and classification controls match official workloads—especially with AI features increasingly bolted onto the platform.

For Government IT Decision‑Makers

The shift to ICS is an explicit bet on shared services over bespoke builds. That promises economies of scale and eliminates duplicated platform costs. But it creates a single point of dependency: if ICS lacks capacity, clear service level agreements, or tenant‑migration expertise, the Cabinet Office could face new bottlenecks. For public‑sector projects still considering similar moves, the Falcon story underscores the need to audit the receiving shared service’s readiness before handing over critical workloads.

For End‑Users and Business Units

Effective migration is as much about people as about technology. The Cabinet Office’s 15,000 staff will eventually need to abandon familiar Google Workspace workflows and adapt to Microsoft 365. The Red rating flags a risk that business units won’t transition within planned time frames. For any organization, that means disruption to productivity, fragmented collaboration during the cutover, and the potential for shadow IT if users resist the change. The best migrations invest up‑front in role‑based training, quick‑start guides, and dedicated support during go‑live windows.

How We Got Here: A Timeline of Resets

The Falcon programme hasn’t simply drifted; it has been repeatedly re‑scoped since its 2022 launch. Understanding that path helps explain why a Red rating persists despite the recent cost headline.

  • May 2022: Programme launched to modernise the Cabinet Office’s IT platform and migrate ~15,000 users from Google Workspace to Microsoft 365. Initial cost estimates were in the £50–52 million range, with a target completion around March 2025.
  • 2023: Capgemini awarded a technical partner contract valued in the low‑teens of millions to support platform delivery and migration.
  • 2024: A separate migration delivery contract with Microsoft was terminated after the discovery phase. The department paid for discovery but invoked its right to stop the three‑year migration deal. The Register revealed a “planned pause” so the business case could be reassessed.
  • 2025: Following a departmental review, the Cabinet Office abandoned the bespoke‑build model and assigned the migration to ICS/DESNZ. The GMPP data sheet recorded a fall in whole‑life cost from ~£51m to £23m, but NISTA’s Red rating remained, citing “resource constraints in transitioning the Cabinet Office Business Units within planned timeframes” and the pilot delay.

Public reporting suggests the Capgemini contract remains available if needed, but the new model leans heavily on Microsoft and its partners for migration execution at “no investment cost.”

What to Do Now: Practical Steps for Migration Teams

Any IT leader staring down a Workspace‑to‑M365 migration—whether for a government department or a private enterprise—can extract actionable lessons from Falcon’s troubles. Here are six guardrails drawn from the programme’s documented risks and from real‑world migration experience.

1. Adopt a Phased, Pilot‑First Strategy

Do not attempt a single big‑bang cutover. Start with a small, well‑instrumented pilot that exercises all migration paths: mail, calendar, contacts, user drives, shared drives, and any application integrations. Use iterative waves to scale lessons learned before broad roll‑out. The Falcon pilot’s delay to September 2025 is a stark reminder: a failed or late pilot can cascade into programme‑wide schedule slippage.

2. Govern Security and Data Classification Early

Map Google‑side controls to Microsoft equivalents before migration begins. Freeze or reconcile retention and messaging records management policies, because automated migration tools can mislabel content as missing if policies conflict. Define a target security baseline that covers data loss prevention, sensitivity labels, and external sharing settings aligned with your organisation’s risk appetite. For Official‑level data, ensure that AI features and telemetry are governed from day one, not bolted on after go‑live.

3. Plan for Permissions and Shared Spaces

Inventory all Google Shared Drives and external share links. Decide how they will become SharePoint team sites, communication sites, or OneDrive folders, and establish business rules for mapping. Automate permission export and import where possible, and verify integrity through sampling and audit trails. This is the period when accidental over‑sharing spikes; continuous monitoring and quick remediation channels are critical.

4. Invest in Workforce Change

Technology change fails when people are left behind. Budget for role‑based training, quick‑start job aids, and a dedicated support desk during cutover windows. Identify critical macros, Gmail add‑ons, or App Script automations that must be rebuilt in Power Automate or Outlook add‑ins. If users can’t replicate their workflows, adoption will lag and shadow IT will thrive.

5. Secure Commercial Clarity—Even “Free” Resources

If a vendor offers migration assistance at “no cost,” demand written detail on scope limits, SLAs, remediation guarantees, and liability allocation. Enterprise‑agreement migration funding often comes with constraints: it may cover only certain mailboxes, exclude shared drives, or require the customer to provide substantial project management and data remediation staff. Retain internal contingency funding for edge cases—data that won’t export cleanly, compliance holds, or custom integrations.

6. Build Verification and Rollback into Your Plan

Establish acceptance criteria for each wave, automated verification steps, and snapshot backups for critical mailboxes and repositories. Rehearse rollback procedures and maintain parallel access to both platforms where possible during transition. The ability to undo a problematic migration wave is not optional when business continuity is on the line.

Outlook: What to Watch Next

The Falcon programme’s future depends on a handful of near‑term indicators:

  • ICS capacity: Will DESNZ publish a clear, resourced migration plan with timeline commitments for Cabinet Office business units? Without it, the Red rating is unlikely to improve.
  • Pilot performance: The pilot, now projected for September 2025, must demonstrate strong data fidelity, acceptable user experience, and permission integrity to build confidence for wider roll‑out.
  • Vendor commitments: The scope and limits of the promised “no investment cost” migration resources from Microsoft and partners must become concrete—and transparent to oversight bodies.
  • NISTA monitoring: The programme sits in the GMPP; any improvement in delivery confidence will signal that the new model is actually working. If the rating stays Red through 2026, expect political scrutiny to intensify.
  • Operational continuity: Staged migrations must avoid disrupting ministers, policy teams, and crisis‑response units. Any hiccup in live services will quickly become a reputational problem.

For the Cabinet Office, the revised Falcon programme is a clear bet that standardisation and shared services can salvage a troubled migration. For the wider IT community, it’s a free masterclass in why large‑scale cloud moves demand more than a vendor commitment and a headline cost cut—they demand disciplined execution, technical rigour, and an unflinching focus on the people who actually use the tools.