March 8, 2026

Summary

A specialist delivery partner was engaged to assess and plan a large-scale collaboration migration for a UK construction business with around 3,200 users. The organisation was preparing to move from Workplace by Meta to Viva Engage, but it wanted to execute the migration itself rather than outsource the full implementation.

The engagement focused on creating the programme, governance, and readiness pack that would allow the client to deliver the migration internally with clear ownership, controlled dependencies, and a realistic adoption path.

Challenge

The environment covered a wide range of user groups, from frontline workers to senior stakeholders, across multiple departments with different communication habits and operational pressures. That meant the migration could not be treated as a simple tool swap.

The client needed a plan that combined technical readiness, communications, adoption, training, and governance, while also making it practical for internal teams to execute without an external implementation partner running the project day to day.

Objectives

• Assess the current-state collaboration estate and identify migration dependencies.
• Design a full migration programme that internal client teams could execute safely.
• Break the delivery down into clear phases, owners, dependencies, and acceptance points.
• Ensure the move to Viva Engage aligned with Microsoft 365 adoption guidance and Teams deployment realities.
• Provide enough structure for departments to manage their own responsibilities without ambiguity.

Approach and Delivery

The work started with discovery across business functions, stakeholder groups, and operational workflows. Current-state collaboration usage, governance gaps, ownership models, and readiness constraints were assessed so the programme plan would reflect how the organisation actually operated rather than how the platform worked in theory.

From that foundation, a 15-phase migration programme was created. The plan sequenced governance decisions, technical preparation, communications, pilot activity, user enablement, wider rollout, and stabilisation. This was then expanded into a detailed cross-department work breakdown containing just under 1,200 tasks, so each area knew what had to be completed and when.

Technical Implementation

Although this was a planning engagement rather than a hands-on migration, the technical workstream was defined in practical terms. The programme covered licensing assumptions, tenant readiness, identity and access dependencies, Teams deployment considerations, Viva Engage community structure, communications ownership, and operational governance.

Microsoft guidance on service adoption and Viva Engage launch readiness was used to shape the design. That included planning for stakeholder sponsorship, launch sequencing, user segmentation, and the use of Teams as an access point for the new collaboration experience.

Outcome

The client received a complete migration blueprint that it could execute internally. This included the phased programme, task-level breakdown, governance structure, and adoption plan needed to move from Workplace by Meta to Viva Engage in a controlled way.

Because the work was decomposed by department and dependency, the organisation was left with a practical delivery pack rather than a high-level strategy document. That materially reduced ambiguity and made self-delivery viable.

Risks, Controls and Governance

The main risk was that a self-delivery approach could fail through unclear ownership, poor sequencing, or low adoption across the workforce. This was controlled by defining departmental responsibilities explicitly, setting phase gates, and separating technical readiness from adoption readiness rather than treating them as the same thing.

A second risk was uneven uptake between frontline, office-based, and senior user groups. That was addressed through role-based adoption planning, stakeholder mapping, and a phased rollout model supported by communications and training controls.

Key Lessons

Large collaboration migrations succeed when they are treated as business change programmes, not just platform changes. A detailed task model, clear ownership, and realistic adoption sequencing are essential when the client intends to deliver the work itself.

The engagement also reinforced that Viva Engage planning needs to account for the wider Microsoft 365 operating model, especially Teams entry points, governance, and stakeholder-led adoption.