The Challenge

Our client, a mid-sized public sector organisation, was operating across three separate Microsoft tenants — a legacy of previous departmental mergers and acquisitions. This fragmented estate created significant operational inefficiencies: duplicated licensing costs, inconsistent security policies, inability to collaborate easily across departments, and a desktop environment running Windows 7 with end-of-life applications.

The organisation had previously attempted a consolidation project internally, which had stalled after six months due to technical complexity and resource constraints. Senior leadership mandated a successful completion within two financial quarters, with no tolerance for service disruption during the public-facing operational periods.

The Aetherbridge Approach

Phase 1: Discovery and Architecture (Weeks 1–4)

We began with a thorough discovery of all three tenants — cataloguing users, mailboxes, shared drives, Teams environments, licensing assignments, and third-party integrations. This produced a comprehensive dependency map that the previous internal attempt had never completed, and revealed several undocumented legacy integrations that would have caused failures during migration.

A detailed migration architecture was designed, including a phased cutover sequence that prioritised lower-risk departments first, allowing the methodology to be refined before tackling the most complex areas.

Phase 2: Infrastructure Preparation (Weeks 5–10)

The target tenant was prepared and hardened — security baselines applied, Conditional Access policies configured, and Modern Desktop deployment packages built and tested on representative device types. Pilot migration of a 50-user test cohort validated the migration toolchain and user communication approach.

Phase 3: Phased Migration (Weeks 11–22)

Departments migrated in seven waves, each preceded by a user briefing, tooling pre-checks, and a readiness sign-off gate. Our team provided dedicated support during each wave's first business day post-migration, with a streamlined escalation path for urgent issues. The maintenance windows ran from 10pm–4am, with pre-planned rollback procedures that were never needed.

Phase 4: Optimisation and Handover (Weeks 23–26)

Post-migration, we conducted a full licensing audit that identified significant over-licensing from the legacy estate. Rationalising to appropriate licence tiers generated the majority of the £407,000 documented saving. A knowledge transfer programme equipped the internal IT team with the skills to manage the consolidated environment confidently.

The Results

• Zero critical incidents during migration, across all seven waves
• 100% of users on Modern Desktop (Windows 11 + Microsoft 365 Apps) within the project timeline
• Three tenants consolidated to one, with unified security policies and consistent user experience
• Security posture substantially improved — Conditional Access, MFA, and Defender deployed where previously absent
• Internal team upskilled with documented runbooks for ongoing management

The Challenge

A fast-growing professional services SME engaged Aetherbridge at a critical inflection point. The company had expanded from 40 to 120 employees in 18 months and was simultaneously rolling out a new CRM platform, transitioning from on-premise file storage to cloud, and onboarding two acquired businesses with separate IT environments.

Their single internal IT generalist was overwhelmed. Incidents were taking days to resolve. New starters were being onboarded inconsistently. The CRM rollout was at risk. Leadership recognised that the internal team, though capable, lacked the capacity and specialist expertise needed for the transformation period.

Our Approach

Stabilising the Service Desk

Our first priority was triage — categorising and resolving the existing backlog of 60+ open tickets. Within three weeks, the queue was cleared and an ITIL-aligned ticketing process was in place. Consistent categorisation and SLA tracking gave leadership, for the first time, a clear picture of where IT resource was being spent and what the real pressure points were.

Supporting the Transformation Programme

Working alongside the client's project team, our engineers provided technical troubleshooting for the CRM rollout — resolving integration issues, managing user access provisioning, and supporting the go-live. The cloud storage migration was completed over four weekends with zero data loss and minimal user disruption.

Knowledge Transfer as a Core Deliverable

Every ticket resolved was documented in a shared knowledge base. The internal IT team member shadowed complex resolutions. Monthly capability reviews assessed progress against an agreed skills roadmap. By month nine, the internal team was handling 80% of incidents independently, with Aetherbridge providing overflow and specialist support only.

The Results

• Zero service disruptions during the entire 18-month transformation period
• 85% reduction in P1 and P2 incident volume over 12 months, from improved processes and preventive maintenance
• Onboarding time halved — from an average of 3 days to 1.5 days per new starter
• Internal team fully capable of independent service management — the explicit goal from day one achieved
• CRM rollout completed on time and on budget, with technical support from Aetherbridge throughout

The Challenge

A 200-person enterprise professional services firm had an IT team of six that was, by their own admission, "always firefighting". Incidents were raised informally through phone calls and corridor conversations. There was no formal change management process — changes were made ad-hoc and frequently caused service disruptions. Problem management didn't exist: the same incidents recurred week after week.

Staff morale in the IT team was poor. Business stakeholders had lost confidence in IT's ability to deliver. The newly appointed IT Manager had been brought in specifically to address the situation and engaged Aetherbridge as their transformation partner.

The Transformation Approach

Stage 1: Assess and Stabilise (Months 1–2)

We began with a full ITIL maturity assessment across all five ITIL 4 dimensions and the four dimensions model. This produced a clear baseline and a prioritised improvement roadmap agreed with the IT Manager and executive sponsor. Critically, we identified quick wins that could demonstrate early progress — essential for rebuilding stakeholder confidence.

A basic incident management process was implemented within the first three weeks, using the existing helpdesk tool (which the team had but was barely using). A simple, enforced process for logging, categorising, and routing incidents created immediate visibility where there had been none.

Stage 2: Process Design and Implementation (Months 3–6)

Working collaboratively with the IT team — not imposing on them — we designed and implemented core ITIL 4 practices appropriate to the organisation's size and context:

• Incident Management: Full tiered categorisation, SLA definition, escalation paths, and regular service review meetings
• Problem Management: Root cause analysis for all P1s and recurring incidents, known error database, and trend analysis
• Change Management: RFC process, change advisory board (scaled to fortnightly 45-minute calls), and a standard change catalogue for low-risk activities
• Service Catalogue: First documented catalogue of IT services, with clear ownership and SLA commitments per service

Stage 3: Embedding and Optimisation (Months 7–9)

Process adherence is where many ITIL transformations fail — the discipline gets abandoned under pressure. We ran a four-month embedding phase with regular process audits, team coaching sessions, and refinement of anything that was creating unnecessary overhead rather than genuine value.

By month nine, the team was operating the processes autonomously with genuine confidence. Monthly service reviews with business stakeholders were running, producing dashboard data that told a compelling story of transformation.

The Results

• SLA compliance moved from 34% to 92% within nine months
• 67% reduction in repeat incidents — a direct result of problem management practices identifying and eliminating root causes
• Zero major incidents caused by unmanaged changes in the final six months (compared to four in the six months prior)
• User satisfaction improved from 2.4/5 to 4.6/5 as measured by quarterly survey
• IT team morale transformed — structured processes removed the constant stress of informal firefighting