What are the discrete phases of transition, and what happens in each?

While every onboarding is tailored, Espria transitions typically follow the phases outlined below. Each phase builds on the previous one and includes formal checkpoints before moving forward.

Discovery

The discovery phase establishes a clear understanding of your current environment and operating model.

This includes:

• Technical assessment of systems, services and dependencies
• Review of documentation, credentials and access
• Identification of third-party vendors and contracts
• Initial risk, issue and dependency capture

The output is a current-state baseline that informs planning, remediation and transition sequencing.

Remediation

Where risks, gaps or unsupported configurations are identified, remediation actions are defined.

This phase may include:

• Addressing security or compliance gaps
• Resolving documentation shortfalls
• Stabilising services prior to take-on
• Agreeing what must be fixed pre–go-live versus post–go-live

Remediation is prioritised based on risk to continuity, not cosmetic improvement.

Planning

Transition planning converts discovery outputs into a controlled delivery plan.

Key activities include:

• Defining transition scope and sequencing
• Agreeing milestones, dependencies and acceptance criteria
• Confirming fallback and rollback options
• Aligning internal and third-party responsibilities via RACI

This phase ensures all stakeholders understand what will happen, when, and who owns each step.

Migration (where applicable)

Where services, data or workloads need to be moved, migration activities are planned and executed in line with agreed controls.

This may include:

• Data or workload migration
• Service reconfiguration or platform changes
• Device onboarding or rebuilds
• Validation testing following changes

Not all transitions require migration; where they do, changes are staged and validated to minimise disruption.

Service take-on (Go-Live)

Service take-on is the point at which services formally enter Espria’s managed service framework.

At this stage:

• Monitoring and alerting are live
• SLAs and escalation paths are active
• Support teams are fully briefed
• Reporting and governance are operational

Enhanced monitoring is typically applied during early life support to ensure stability.

Lessons learnt and stabilisation

Once services are stable, we conduct a formal review to:

• Validate performance against success criteria
• Capture lessons learned
• Identify improvement opportunities
• Confirm readiness for business-as-usual delivery

This phase closes the transition and ensures onboarding insights feed directly into continuous improvement.

Why a phased approach matters

Delivering onboarding in discrete phases allows Espria to:

• Control risk and dependencies
• Avoid unmanaged handovers
• Prevent premature go-live
• Maintain accountability at every stage

Progression between phases is based on readiness and sign-off, not assumptions or time pressure.

Key takeaway

Espria transitions are delivered through clearly defined phases, from discovery through to stabilisation, each with specific objectives, ownership and acceptance criteria.

This phased, governed approach ensures services are taken on safely, predictably and without disruption, providing a strong foundation for long-term managed IT service delivery.

Related questions

• How long does onboarding or transition take and what are the key milestones?
• How is mobilisation, current state assessment, transition and go-live executed?
• What prerequisites and success criteria are identified at inception?