Who Holds the Keys? The Hidden Risk in Moving From an MSP to Your First Internal IT Leader
- November 20 , 2026
- Share
The new IT Manager is to begin work from Monday. The team has been told, the announcement has been made, and the owner expects someone to take charge of technology and make improvements.
The new hire has yet to receive administrator access to key systems by Wednesday.
The email platform is outsourced to the IT service. No one within the organization knows who’s in control of the domain name registration. There are backups, but no one can vouch for when they have been last tested. Documentation of the firewall settings exists somewhere, but no one can find it.
The IT Manager has started work but the access and responsibilities needed to take charge have not yet been transferred.
This is where the shift to becoming an IT leader can stall for Manitoba businesses moving away from outsourced IT.
In the first post of our Black Box of IT series, we’ve covered the reasons why your first internal hire could be a costly mistake. Now, it’s time to switch to the handover.
A managed service provider, also known as an MSP, will typically provide service for a business over several years. It manages user accounts, software licenses, backups, network equipment, security, vendor relationships and the technical issues that no one outside of IT knows about.
A lot of this work goes on in the background.
A tech resolves a common logon problem. You make changes to a firewall rule for a new application. The software licence will be renewed from the provider’s account. Upon server upgrade, a backup job changes.
Business continues as normal, and employees finish their work. The owner is not always aware of the location of all settings or who possesses all passwords.
As time goes on, the MSP can turn into an effective technology steward for the business.
This could be appropriate if the provider is responsible for the setting. The challenges are that a new head of IT comes in and takes over before this expertise is passed on.
The provider is not at fault. Information might just be stored over a number of technicians, service tickets, systems and years of routine work.
A transformation in the operating model also means that access and knowledge-sharing arrangements need to change.
- 1. Who Actually Owns the Access?
Be owners of things, not a list of passwords on a spreadsheet.
Is the company able to interface with its Microsoft 365 or Google Workspace environment? Who owns the domain registrar and DNS records that can route traffic and email to a website? Is the software subscription owned by the business, or managed through the MSP’s subscription? Who is allowed to use the firewall and backup platform?
These questions are practical and relate directly to business issues.
When the relationship with the provider is to change unexpectedly, the company must have a way to access its systems, data and vital accounts.
Before the start date, set up an agreed access-transfer plan. Identify critical accounts, verify account ownership and set up proper administrative access for the incoming leader. When subscriptions or accounts remain with the provider, identify what needs to be moved and what contractual or technical procedures will need to be followed.
Security matters, too. It’s not logical to have a document with all of the passwords. If supported, use secure transfer methods, individual accounts, permissions and multifactor authentication. Use rotation of credentials as needed.
This simple objective is to ensure that the business is aware of who is operating on its systems and the methods used by authorized users to do so.
- 2. What Is Actually Documented?
It is helpful to have a list of software installed. Does not provide a complete environmental picture.
The new leader must become familiar with the systems and how they interact with one another and what’s required.
This means arranging for backups, recovery plans, security updates, network configuration, external vendors, etc. It contains other information, too – things that are not so obvious, like recurring issues, unusual places, manual shortcuts, applications that rely on older systems.
There might be some information in the MSP’s service desk. Other information might be included on invoices, emails and technician notes. Some may not have been officially documented.
The solution is not to expect a step-by-step how-to book in a single day. Discuss a sensible handover package that includes important systems, dependencies, known issues, vendors and important operating procedures.
Consider any great work, unresolved incidents or planned changes.
Backups are especially important. The business should be aware of what is being backed up, where the copies are being stored, who can access the copies, and whether the recovery of these copies has been tested. When it comes to backup, it doesn’t always mean that a company can get back up and running when it is required.
If that is not provided, the new recruit might take months to build the environment up, rather than building it up.
- 3. How Long Should the Handoff Last?
Calendar dates for handover do not imply that the handover is completed
This will depend on the size of the company, complexity of the system, quality of the documentation, and responsibilities to be transferred during this process.
A simple setting could require a brief, concise transition. Several weeks or more may be needed for a business with many locations, legacy applications, complex vendor relationships, and little documentation.
Establish a timeline in advance of the new hire. Establish targets or milestones for transferring access, reviewing documentation, meeting with vendors, completing knowledge-transfer sessions and confirming the ability to manage critical systems.
Give new leader time to ask questions and to try out what is handed to him/her. A document that is marked complete does not mean that the information is accurate, nor does it mean that access is successful.
Set parameters for what to do when there are gaps. Assign accountability for the recovery of an undocumented system or a system where a recovery procedure has not been documented and/or tested.
When the responsibilities required for the transition can be fulfilled – not just when the actual date has arrived.
Not necessarily.
However, for certain companies, a co-managed option is more appropriate. Activities and tasks are carried out by the internal IT leader for the day-to-day business, for internal coordination and for technology planning, while the MSP will keep on delivering the selected specialist services.
These could range from complex cybersecurity, around-the-clock monitoring, backup management, network support or skills that would be a challenging full-time hire.
This can be practical for a Manitoba business of 25-250 employees. The business establishes an insider control point without having to rely on one person to be a jack of all trades.
The difference is between keeping support and dependency.
A co-managed relationship should establish responsibilities, decision-making rights, escalation of incidents, and documentation ownership. It must also define how the internal leader and provider work together to coordinate changes without causing any competing directions or lines of accountability.
The partnership of the MSP is still there, but the business is now clear on what it owns and what is delegated, along with how they work together.
An adept IT leader can take over a complex IT landscape and enhance it. They can’t simply make undocumented systems and unclear responsibilities go away on the first day.
That’s why a transition should be part of a hiring process, rather than merely an administrative item that comes after the fact.
To business owners, presidents, CFOs and COOs, the bottom line is: the person joining your business requires more than a job description and an introduction to the team. They must be given the power, information and support to take responsibility.
Lambert Nemec Group is a partner of Manitoba businesses for recruitment in the Information Technology, Accounting & Finance and People & Culture sectors. Importance of the right person. So does training the organization for that person to succeed.
Before your new IT leader comes on board, decide who will have the keys, what knowledge will be shared, and how the handover will be validated.
The first day should be a day of better IT leadership, not a day spent trying to find out the password.