Changing your Managed IT Support provider can feel like a significant undertaking.
Your existing provider may have access to critical systems, infrastructure, documentation and administrative accounts. They may also hold years of knowledge about how your organisation operates.
Understandably, one of the biggest concerns when considering a change is therefore not simply choosing a new provider. It is how you move from one provider to another without disrupting the business.
With the right preparation, switching Managed IT Support providers does not need to be disruptive.
A successful transition should be structured around understanding your existing environment, transferring knowledge and access securely, agreeing responsibilities and ensuring the new provider is ready to support the organisation before the handover is complete.
This guide explores the key areas organisations should consider when planning that transition.
Start by understanding why you are changing
Before beginning the transition, it is important to understand what you want to improve.
Perhaps support has become increasingly reactive. Response times may no longer meet expectations, or your existing provider may not have the expertise required as your technology environment develops.
Alternatively, the organisation itself may have changed.
You may have grown, introduced Microsoft 365 or Azure services, adopted hybrid working, increased your security requirements or simply reached a point where you need more strategic input from your IT provider.
Understanding these requirements helps establish what the new relationship needs to deliver.
Rather than simply replacing one support desk with another, changing provider can be an opportunity to review how IT supports the organisation more broadly.
Understand your existing IT environment
A new Managed IT Support provider needs to understand what they will be responsible for.
This begins with discovery.
Your existing environment may include:
- Servers and infrastructure
- Laptops, desktops and other devices
- Microsoft 365
- Microsoft Azure
- Business applications
- Networking and connectivity
- Backup and disaster recovery
- Security products and services
- Software and licensing
- Third-party suppliers and services
However, producing an inventory is only part of the process.
The new provider also needs to understand how these systems interact and which services are particularly important to the business.
For example, an application may rely on a database hosted elsewhere or a particular network connection. A process that appears relatively unimportant from a technical perspective could also be critical to a particular department.
The original environment documentation may not capture all of this, which is why discussions with internal stakeholders can be just as valuable as technical discovery.
Document systems and dependencies
Good documentation makes the transition considerably easier.
The incoming provider should build a clear picture of important systems, their configurations, dependencies and ownership.
This may include information such as:
- Key applications and infrastructure
- Application dependencies and integration’s
- Network configuration
- Administrative access
- Backup arrangements
- Licensing
- Third-party suppliers
- Existing support processes
- Known technical issues
- Business-critical systems
This process can also highlight gaps in existing documentation.
IT environments evolve over time, and documentation does not always evolve with them. Applications may have been introduced, configurations changed or temporary workarounds adopted without being formally recorded.
A transition provides an opportunity to improve that position rather than simply transferring incomplete information from one provider to another.
Choose a provider that understands your organisation
Technical capability is important, but Managed IT Support should not simply be a technology decision.
Your provider needs to understand how your organisation operates and what employees need from IT.
Consider the provider’s experience across the technologies you use today as well as those you may adopt in the future.
For organisations using the Microsoft ecosystem, this could include expertise across Microsoft 365, Azure, endpoint management, identity and wider cloud infrastructure.
You should also understand how support will work in practice.
Who can raise a ticket? How are priorities determined? What happens when an issue becomes critical? How are problems escalated? Who is responsible for ongoing account management?
Service levels should be clearly defined, but the wider relationship is equally important. A good Managed IT Support provider should understand your priorities rather than simply focusing on closing individual tickets.
Plan the transition
Once the existing environment has been understood, a transition plan can be developed.
The complexity of this plan will depend on the organisation and the services being transferred.
A relatively straightforward environment may require a simpler handover, while an organisation with multiple locations, legacy infrastructure, cloud services and numerous third-party applications will require more detailed planning.
The transition plan should establish:
- What is being transferred
- Who is responsible for each activity
- What information and access are required
- Which systems are most critical
- How knowledge will be transferred
- How risks will be managed
- How employees will be informed
- When the new provider assumes responsibility
- What happens if an issue occurs during handover
The objective is to remove ambiguity.
Both the organisation and the incoming provider should understand what needs to happen before the transition is considered complete.
Manage access and credentials carefully
Administrative access is an important part of any IT support transition.
The incoming provider may require access to Microsoft 365, Azure, servers, networking equipment, security platforms, backup services and other business systems.
This information should be transferred securely and systematically.
Rather than simply handing over a collection of usernames and passwords, organisations should understand what each account is used for, who currently has access and whether that access is still required.
The transition can therefore provide a useful opportunity to review privileged access.
Where appropriate, credentials associated with the previous provider can be changed or removed once the handover is complete, helping ensure access reflects the organisation’s new support arrangements. The original article similarly identifies credential management and access handover as a distinct part of the transition.
Protect business continuity
One of the biggest concerns organisations have when changing IT providers is disruption.
A well-planned transition should be designed to minimise that risk.
Business-critical systems should be identified early so that additional attention can be given to anything the organisation cannot operate without.
Where changes are required as part of the handover, they should be planned around business requirements and tested appropriately.
Backup and recovery arrangements should also be understood before significant changes are made.
For more complex transitions, it may be appropriate to establish contingency or rollback plans so everyone understands what will happen if an unexpected problem occurs.
Communication is equally important.
Employees do not necessarily need to understand every technical aspect of the transition, but they should know when the new provider takes responsibility, how they request support and whether anything about their normal processes will change.
Do not overlook security
Changing providers can involve transferring privileged access to some of the organisation’s most important technology.
Security therefore needs to be considered throughout the process.
Access granted to the incoming provider should be appropriate to their responsibilities and transferred using secure methods.
Once the transition is complete, access associated with the previous provider should be reviewed and removed where it is no longer required.
It is also worth considering whether the transition reveals existing security issues.
Discovery may identify outdated accounts, unnecessary permissions, unsupported systems or other areas that should be addressed.
Not every issue needs to be resolved before the new provider takes over, but significant risks should be understood and prioritised.
Prepare for go-live
Before responsibility formally transfers, both sides should be confident that the incoming provider has what they need.
This means confirming that:
- Critical systems have been identified
- Appropriate administrative access is available
- Key documentation has been transferred
- Backup and recovery arrangements are understood
- Monitoring and support tools are configured where required
- Escalation processes have been agreed
- Employees know how to request support
- Important suppliers and contacts have been documented
- Responsibilities between the organisation and provider are clear
The aim is not to achieve perfect documentation before go-live.
It is to ensure there are no significant gaps that could prevent the provider from supporting the organisation effectively.
Allow time for stabilisation
The transition does not necessarily finish the moment the new provider takes responsibility.
There is usually a period in which the incoming team continues developing its understanding of the organisation and identifying opportunities for improvement.
Some issues may only become apparent once the provider begins supporting users and managing the environment day to day.
This period should be used to refine documentation, resolve outstanding issues and establish the working relationship between the internal team and the new provider.
It can also provide an opportunity to move beyond the immediate transition and consider longer-term priorities.
Are there recurring support issues that should be addressed permanently? Is infrastructure approaching end of life? Could Microsoft 365 be used more effectively? Are there opportunities to move appropriate workloads to Azure? Are backup, resilience or security arrangements still suitable?
The transition can therefore become the starting point for improving the wider IT environment.
What should good Managed IT Support look like?
Changing providers should ultimately result in more than a different telephone number or support portal.
A Managed IT Support provider should become an extension of your internal team, helping maintain the technology employees rely on while providing the additional skills and capacity the organisation needs.
That means combining responsive day-to-day support with a proactive approach to the wider environment.
Rather than waiting for problems to occur, your provider should help you understand where improvements may be required and support the organisation as its technology requirements evolve.
For mid-market organisations in particular, this can provide access to a broader range of IT expertise without needing to build every capability internally.
How HAYNE.cloud can support your transition
HAYNE.cloud works with organisations to provide ongoing Managed IT Support across their wider Microsoft and IT environment.
Our approach begins by understanding your organisation, existing technology and support requirements before developing a structured transition plan.
We can work alongside your existing internal IT team or provide broader outsourced IT support, depending on the level of assistance your organisation requires.
Our wider capabilities across Microsoft 365, Azure, Modern Workplace and Managed IT Support also mean that support does not need to stop with resolving day-to-day issues.
As your requirements develop, we can help you review and improve the wider technology environment, whether that involves cloud infrastructure, Microsoft 365, Azure, endpoint management or wider IT projects.
The objective is to make the transition as straightforward as possible while establishing a support relationship that can continue to develop alongside your organisation.
Ready to review your Managed IT Support?
If you are considering changing Managed IT Support providers, the first step does not need to be a commitment to move.
Start by understanding your current environment, what is working well and where your existing support arrangement is falling short.
HAYNE.cloud can help you review your requirements and understand what a transition could involve.
Speak to HAYNE.cloud about your Managed IT Support requirements and discover how we can support your organisation.
