People, access and suppliers
- organisation contacts, sites, users and supported devices
- administrative and recovery access
- suppliers, licences, contracts, contacts and important renewal dates
Switch IT provider
Switch IT provider with a controlled handover.
We use a structured four-week transition approach to understand your environment, secure and verify access, prepare the new support service and move responsibility in a controlled way. Exact timing depends on the environment, available access and any customer, outgoing-provider or third-party dependencies.
A controlled handover
Changing IT provider can feel risky, even when the current arrangement needs reviewing.
The concern is usually not just choosing a new provider. It is understanding access, documentation, Microsoft 365, backups, devices, suppliers, open issues and who keeps supporting users while responsibility changes.
A good handover starts by understanding what already exists, what needs to move, where information is missing and which dependencies need coordinating.
The centre of the handover
The four-week transition
Our standard approach is organised around four stages. The structure gives everyone a clear sequence, while the detail and exact timing still depend on the environment, access and third-party dependencies.
Week 1: Understand and secure
Map the key people, users, devices, sites, suppliers, cloud services, domains, backup arrangements and security tools, while identifying urgent access or support risks.
Outcome: The aim is a reliable picture of the current environment and the issues that need attention first.
Week 2: Document and verify
Validate administrative and recovery access, review available documentation, confirm important systems and suppliers, and identify missing information or unresolved dependencies.
Outcome: The aim is to understand what CompTech can take responsibility for and what still needs input from the organisation, outgoing provider or another supplier.
Week 3: Prepare the new support service
Agree support and escalation routes, prepare monitoring, management and security onboarding where included, coordinate suppliers and make sure users know how support will work.
Outcome: The aim is to prepare the organisation and CompTech for day-to-day support to move when the required dependencies are ready.
Week 4: Take over and stabilise
Where the required access and dependencies are in place, CompTech becomes the normal support route, monitors early issues, closes remaining handover gaps where possible and agrees the next improvement priorities.
Outcome: The aim is a stable support position with clearer ownership, known outstanding issues and an agreed route for anything that needs further work.
The four-week structure is our standard transition approach, not a guarantee that every dependency or inherited issue will be resolved inside four weeks. Timing can change where access, outgoing-provider responses, customer decisions or third-party actions are still required.
Complex projects, migrations or inherited remediation may continue separately after the support transition.
What we need to understand
Build one clear picture of the environment before responsibility moves.
You do not need to arrive with perfect documentation. CompTech can work through the available information with your organisation and, where appropriate, the outgoing provider and other suppliers.
The exact information available will depend on the environment and current arrangements.
Microsoft 365 and domains
- Microsoft 365 tenant, partner relationships, licensing and domain ownership
- domains, DNS, email and registrar access
Infrastructure and protection
- servers, network, firewall and cloud platforms where relevant
- backup platforms, administrative access and existing protection
- security, monitoring, device-management and remote-access tools
Documentation and dependencies
- documentation, open incidents, known risks and temporary workarounds
- existing projects, migrations and agreed transition dependencies
Clear responsibility
Know who owns what while support is changing.
The organisation should retain appropriate ownership and recovery access to its own critical systems rather than being completely dependent on one supplier.
Your organisation
Appoints an internal transition owner, authorises access and changes, makes decisions about its contracts and confirms business priorities.
CompTech
Coordinates discovery, verifies the access available to us, documents the known environment, prepares the agreed support service and highlights gaps or dependencies that still need action.
Outgoing provider
May be asked to supply agreed documentation, credentials, service information and other handover material under the organisation’s existing arrangements.
Other suppliers
Registrars, internet providers, software vendors and other third parties may control their own access, processes and lead times.
Before the support route changes, we agree who handles new tickets, open incidents, urgent problems, supplier contact and the point at which CompTech becomes the normal support route.
CompTech does not assume or invent obligations for an outgoing provider or third party that are not part of the organisation’s existing arrangements.
Incomplete handovers
What if documentation or access is missing?
A cooperative handover is usually the simplest route, but incomplete documentation, delayed responses or missing access do not automatically make a transition impossible.
CompTech can identify what is missing and work through legitimate alternatives where appropriate. That may include confirming organisational recovery access, identifying equipment, rebuilding documentation or contacting suppliers where authorised.
Change with a reason
We do not change everything just because you have changed provider.
A provider switch is already a period of change. Systems that work well may not need replacing immediately.
Transition work
What is required to safely take responsibility for the existing environment.
Priority remediation
Problems that need relatively quick attention because they create meaningful risk or instability.
Future projects
Improvements that can be planned separately once the support service has settled.
This keeps the provider transition separate from larger migrations, upgrades or inherited remediation that need their own scope.
A steadier starting point
What should be clearer after the handover?
Support and responsibility
A known support route, clearer responsibilities and a better understanding of who owns the important systems and supplier relationships.
Access and documentation
A clearer position on administrative access, documentation, licences, dependencies and the services that still need follow-up.
Risks and priorities
Known inherited issues are separated from immediate remediation and future projects so the next improvements can be planned properly.
A managed transition
Want to understand what changing provider would involve?
Tell us what is not working today, what concerns you about the handover and when you would ideally like support to move.
We’ll help you understand the practical steps, the dependencies that need resolving and whether our four-week transition approach is realistic for your environment.