You should be able to change IT support provider without losing control of your email, website or business files. That requires more than agreeing a start date with the replacement company.
A provider can administer systems through named accounts, delegated permissions, remote support agents and application connections. Subscriptions and recovery contacts add another layer. These need to be understood before responsibility changes hands.
The handover issue we would prioritise is control of the accounts, not the transfer of a password list. If the business cannot establish who owns and administers its critical services, the transition is not ready.
Identify why you want to move
Write down the problems that prompted the decision. Repeated login faults, slow responses and unclear security responsibilities are more useful starting points than a general feeling that the service is poor.
The new provider needs to distinguish support failures from underlying technical problems. Changing the helpdesk will not repair failing equipment or improve an unsuitable internet connection by itself.
Use those problems to define what success looks like after the move. That gives you something concrete to review once the new service is operating. Our guide to IT support for small businesses in the UK sets out what a good service should include.
Establish business control of critical services
Build an account register covering Microsoft 365, your domain registrar, DNS, website hosting, backups, internet services and important business applications.
For each service, identify the contracting organisation, administrator access, billing arrangement and recovery contacts. A domain registered through an employee's personal account deserves attention before that person becomes unavailable.
For Microsoft 365, record the organisation's tenant details and establish authorised administrative access under business control. A licence invoice from a reseller does not explain all the access and recovery arrangements for your tenant.
Business control does not mean giving every director unrestricted administrator access. It means having a secure, documented way for authorised people to retain control when a supplier changes.
A password change does not remove every access route
This is where we would challenge an overly simple handover plan. Changing a shared password does not automatically remove delegated administration, application permissions or remote management software.
The transition needs an access inventory and a removal plan. Review provider accounts, partner relationships, application connections, remote tools and relevant secrets. Separate access used only by the outgoing provider from integrations the business still needs.
Remove obsolete access after replacement access and service continuity have been confirmed. Record what was removed and investigate anything the team cannot explain. Do not disable unfamiliar connections blindly during a busy working day.
Keep security and backups operating throughout
A handover needs named responsibility for endpoint protection, monitoring and backups at each stage. Otherwise, both providers can assume the other is watching an alert.
Security tools also need an orderly transition. Removing the old product before the replacement is operating creates a gap; installing conflicting tools without checking compatibility creates a different problem.
Confirm backup coverage, access to existing recovery points and retention arrangements before ending the old service. Moving to a new backup product does not automatically transfer the historic copies held by the previous service. Our article on Microsoft 365 backup explains what to check.
Separate the handover from the improvement project
Our recommendation is to transfer control and establish a stable baseline before making unrelated changes.
A provider move is already a significant operational change. Combining it with a new file structure, a website migration and a telephone-system replacement makes failures harder to diagnose and recovery more complicated.
Fix urgent security exposures promptly, with a documented plan. Schedule other improvements in stages once the new provider has verified how the business operates.
Check contracts and tell staff what will change
Review support notice periods and separate licence or connectivity commitments. Establish handover charges and any continuing subscriptions before choosing a date.
Tell staff when the new service starts, how to request help and how legitimate support staff will identify themselves. A transition announcement should not teach employees to trust any unexpected caller claiming to be the new IT company.
Close the handover with evidence
Confirm that staff can use their main applications, mail flows correctly and shared files remain available. Verify security monitoring and perform an appropriate backup restore test.
Record outstanding issues, responsible owners and completion dates. The final handover should leave the business with clear documentation and a provider whose responsibilities are explicit.
Considering a different IT support provider?
Montalex provides managed IT support for UK small businesses. We can scope the transition, review account control and plan the move around the services your team depends on.
Tell us what needs to improve