The switch-over date is in the diary. Staff have been told that a new IT provider is coming. The outgoing provider has the domain registrar, admin credentials, monitoring tools and years of operational knowledge. The incoming team is ready to begin, but nobody has been given clear ownership of the handover.
That is how a provider change can start with avoidable disruption: support requests go unanswered, critical access is missing, or a routine change exposes a dependency no one knew existed.
Changing IT provider is not simply a swap of tickets and passwords. It is a business transition that needs an owner, a plan and a clear view of what the organisation depends on. The strategy must lead; the technical handover follows.
Why the handover gets lost
Over time, useful knowledge accumulates in an incumbent provider’s heads, service desk notes and internal runbooks. Some of it may never have made it into documentation the client can access. The estate itself may also have changed without a complete record of devices, applications, suppliers and dependencies.
Access can be spread across services the business uses every day: domain registration and DNS, Microsoft 365 tenant administration, backups and recovery keys, firewalls, remote monitoring, security tools and phone systems. A service may be in the company’s name, the old provider’s name or an individual employee’s account. The distinction matters when access needs to be transferred.
Tools and licences can create a similar snag. Monitoring, endpoint management or security services may be bundled into the outgoing provider’s agreement. Unless ownership, renewal dates and replacement arrangements are understood, the business may lose visibility or support during cutover.
The National Cyber Security Centre’s guidance on working with a managed service provider recommends clear responsibilities, access controls and contract terms. Those principles matter during a change as much as they do when selecting a provider.
Build the handover before day one
The business should appoint one person to own the transition. That person may be supported by an IT consultant or technical lead, but accountability should not be split between two providers who each assume the other is handling it.
Before the start date, assemble an estate document and asset register that covers the essentials:
- Devices, servers, networks and business-critical applications
- Cloud services, domains, DNS and connectivity
- Backup arrangements, retention and recovery procedures
- Key suppliers, licences, renewals and contract owners
- Open support issues, known risks and planned changes
Alongside this, create a credential and ownership inventory. Record who controls each account, how administrative access is granted and where recovery routes sit. Do not send passwords in ordinary email or circulate an unsecured spreadsheet. Agree a secure transfer method, create named accounts where possible, and plan to review or rotate credentials after the change.
Request the outgoing provider’s handover pack in writing. It should include current configurations and diagrams, asset and service records, backup and monitoring status, supplier contacts, open tickets and known problems. Agree what information will be shared, by when and through which secure channel. If a system is undocumented, mark it as a discovery task rather than treating the gap as proof that it is unimportant.

Onboard the incoming provider before it takes support
A new provider should not be expected to take tickets from day one with no understanding of the environment. Begin with discovery and a baseline: what is in place, what is working, what is exposed to risk and what needs attention first.
Turn the findings into a transition plan with named owners and dates. A short plan might cover the pre-start review, information transfer, access setup, service validation and formal cutover. Make responsibilities explicit: who requests the information, who verifies it, who approves changes and who tells staff what to expect.
Define the support model before the first issue arrives. What does “managed” include? Which systems and sites are in scope? How should staff contact the Helpdesk Support team, and how are urgent issues escalated? Who approves changes, and which work is chargeable outside the agreed service?
These questions are part of the service design, not administrative details. Managed IT Services should sit beneath an agreed IT strategy, with operational responsibilities and reporting that are clear to the business. The NCSC recommends written responsibilities and incident procedures in MSP contracts; its guidance is a useful reference when setting those expectations.
Use an overlap period to protect continuity
Where practical, allow a planned parallel period in which the new provider can validate its access and understand the environment before the outgoing provider’s access is withdrawn. The overlap needs boundaries: agreed dates, named contacts, a defined scope for each provider and a clear process for approving changes. Two providers making uncoordinated changes is not resilience; it is a particularly expensive guessing game.
Sequence the work around stability. Confirm that the new team can reach the systems it is responsible for, that monitoring and alerting are active, and that support routes work. Check that backups are running under the intended arrangements, then test a recovery or restore process. A backup status report is useful; a demonstrated ability to recover is better.
The same principle applies to infrastructure and communications. Review Cloud Solutions and Network Solutions access and dependencies, then validate the services staff rely on, including Voice and Connectivity. Ensure the new provider knows how to respond if a circuit, phone service or critical application fails.
Staff need a simple, timed communication: when the provider changes, how to contact support, what information to provide and whether any short-term service changes are expected. Keep the existing channel available until the new one is tested. Make it easy for employees to ask for help without having to guess which provider owns the problem.

Make contracts and costs part of the transition
Review the outgoing agreement for notice periods, handover assistance, charges, data return and the end of access. Honour the terms and agree what the old provider will deliver, by when. The new provider’s onboarding scope should also be priced and documented: discovery, migration, remediation and ongoing support are not necessarily the same thing.
Check who owns each subscription and when it renews. Re-point services to the right business contacts and make sure essential licences will remain active through the change. This is a good moment to use Technology Expense Management to see what is being paid for, identify overlapping services and make ownership visible. Cost control is most useful when it informs the operating model, not when it is a last-minute hunt for savings.
Agree the transition’s exit checks. These might include staff using the new helpdesk route, monitoring and backups verified, important suppliers and renewals accounted for, and agreed actions recorded with owners. Confirm that the outgoing provider’s access is removed at the right point and that the incoming provider has only the access required for its work. If recovery arrangements change, test them and document the result as part of Disaster Recovery.

Strategy owns the transition
A well-managed provider change is not defined by how quickly credentials move between inboxes. It is defined by whether the organisation understands what it relies on, who is accountable, and how service will continue while responsibility changes hands.
That is the role of the Fractal IT Director: to own the direction, priorities and governance of the transition, then bring in the right technical execution beneath that strategy. Helpdesk, cloud, network, recovery and connectivity services are important bolt-ons, but they do not replace a business-led plan.
For organisations reviewing a wider range of group services alongside their IT arrangements, the Evestaff gateway provides a route to the group’s service areas. The IT consultancy’s primary site is itandconsultancy.co.uk.
The handover may involve two providers. Ownership should never be left between them.
SEO keywords:
Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity
Join The Discussion