PLANNING A HANDOVER

Switching IT providers.
Plan the handover.

A structured transition helps you understand what is moving, who owns each system, and which dependencies need attention.

BEFORE YOU COMMIT

Review the existing arrangements.

Begin with your current agreement, renewal dates, notice requirements, and the services it covers. A provider change can involve more than support: licences, domains, hosting, backups, and equipment may have separate owners or terms.

Keep the handover factual and coordinated. Agree which information is needed, who can authorise its release, and how access will be transferred. Avoid cancelling a service before its replacement and dependencies are understood.

HANDOVER CHECKLIST

Build a useful picture of the environment.

Accounts and ownership

Identify authorised administrators for domains, cloud platforms, subscriptions, and key business applications.

System documentation

Gather an asset list, network information, application dependencies, and support contacts.

Services and renewals

List contracts, licences, carrier services, renewal dates, and any separately managed websites.

Backups and recovery

Understand what is backed up, where it is stored, and how recovery access is controlled.

Open work

Record unresolved issues, scheduled changes, and projects already underway.

People and approvals

Name the business decision-maker and contacts responsible for each part of the handover.

THE TRANSITION

Agree the sequence before the switch.

Plan

Confirm scope, required access, responsibilities, dependencies, and the target handover date.

Validate

Check that the incoming arrangement can support the systems in scope and that essential information is available.

Transfer and review

Coordinate the change, update contacts and approved access, and review outstanding issues after handover.

COMMON QUESTIONS

Make the change informed.

Can we keep existing equipment and applications?

The initial review identifies what can be retained, what needs attention, and what is outside the proposed support scope. A change of provider does not automatically mean replacing everything.

How long will the transition take?

Timing depends on the environment, access availability, contract dates, and the work involved. Set a schedule after those dependencies have been reviewed.

What if documentation is incomplete?

Identify the gaps early. Additional discovery may be needed before responsibilities can transfer, and that work should be scoped explicitly.

Can our existing provider remain involved?

Yes, responsibilities can be divided where that suits the business. Document ownership and escalation paths so requests do not fall between providers.

LET’S TALK ABOUT YOUR TECHNOLOGY

Start with a conversation.

Tell us what’s working, what isn’t, and where you want to go.

Request a consultation

Switching IT providers.Plan the handover.