A provider change is more than a new phone number for support. It affects administrator access, licensing, monitoring, documentation and the knowledge behind everyday decisions. A planned transition gives the incoming team something reliable to work from and gives your staff a clear route for help.
A good handover protects organisational knowledge as well as technical access.
Work backwards from the contract dates
Confirm renewal and notice requirements before agreeing a transition date. Identify any separate contracts for internet connections, telephone services, licences and specialist applications. A support agreement ending does not necessarily end those services. Build a timetable with explicit dependencies and named owners. Leave space for unresolved questions rather than assuming every supplier will respond on the same day.
Technical background: NCSC: Supply chain security guidance ↗
Create a handover inventory
Record your devices, cloud services, domains, network equipment, application suppliers and backup arrangements. Request configuration information and a current view of open issues. Store access information securely and share it through an agreed method; never email a spreadsheet full of passwords. The organisation should know who owns its tenant, domains and accounts before responsibility starts moving between providers.
Agree the transition sequence
Some systems may need new management tools or monitoring configuration. Ask how overlapping tools, device restarts and user communication will be handled. Define the point at which the incoming provider owns new support requests and how outstanding tickets are transferred. Keep an escalation route with the outgoing provider until agreed handover actions are complete. A structured sequence is safer than changing everything at once.
Treat the first review as part of onboarding
After the initial handover, review what was discovered and what remains uncertain. Confirm access, documentation, support routes and recovery responsibilities. Separate urgent gaps from improvements that can wait. Staff should know how to request help and what information to include. Finish with a shared action list, so the transition becomes the beginning of a better operating model rather than an indefinite onboarding project.
PUT IT INTO PRACTICE
Your starting checklist.
Use these prompts to prepare your next decision or conversation.
YOUR NEXT STEP WITH IT MOUNTAIN
Turn the question into a plan.
Bring your renewal date and current supplier list to IT Mountain. We can discuss a transition plan and the information needed to scope onboarding.
