When you change IT providers, it’s rarely just a technical project. Rather, it’s a finessing process that affects pride, job security, and control. A good offboarding process starts with empathy toward everyone involved.
To keep the process in perspective, remember why you dropped your last partner. Is your old IT person retiring and/or leaving on good terms? Or did your last partner miss response times and mishandle client relationships?
Whatever the case, you need to keep the new managed service provider (MSP) calm and focused. Here’s how:
1. Set Expectations
Ideally, offboarding would come with full documentation. As a manager, about the best you can expect in the real world is a download of usernames and passwords to major systems.
Ideally, offboarding would come with full documentation. As a manager, about the best you can expect in the real world is a download of usernames and passwords to major systems.
Your main goal is to ensure your business is supported from day one. That usually means admin access to the Microsoft 365 tenant, Active Directory, and line of business apps.
Also, as the manager, it’s your task to handle contract disputes. While the new IT team should lead you with practical advice, they’re not party to the old agreement and they’re definitely not legal counsel.
At the same time, tie your offboarding process back to your initial onboarding process. The better you document during onboarding, the less you’ll need from a reluctant outgoing partner later. Offboarding should feel like running your onboarding process in reverse.
2. Set A Cutover Day
A clean handoff needs to be early enough to reduce overlap confusion, yet realistic enough that access, billing, and admin rights will already be in place.
Before the switch, outline how backups work. Your new provider should know where backups live, how often they run, and how to restore them. Don’t settle for verbal assurances. Ask for written restore steps.
Also, make clear monitoring and alerts protocols (including who owns them on cutover day). If an alert fires at 2 A.M., you should already know who sees it, who responds, and what happens next.
3. Prioritize Systems
Start with what the new IT must have. You can transfer smaller details after Week 1.
It’s possible you won’t have every answer, and that’s ok. The new IT provider will build time into your offboarding checklist for discovery and cleanup.
4. Manage Hurt Feelings Well
Sometimes the new IT support walks into a tense situation. Your previous MSP might be angry, hurt or scared. They may feel they’ve got nothing to gain by helping you.
Tension between parties is likely. As manager, you’ll need to be the mediator between the old and new IT teams. Keep your tone calm, clear, and factual. Let them handle technical aspects while you ensure compliance.
Negative energy slows projects. A steady, methodical approach keeps risk low.
5. Manage the Overlap
Use the overlap between providers to plan the first 30 days. Align expectations on response times and who owns which responsibilities.
TechKnowledgey offers an exclusive, thorough 100-day on- and offboarding process that gives everyone a clear roadmap. That structure helps your staff stay calm. It also creates a visible path to a smooth transition.
Someone from the old MSP is getting fired, downsized or moved aside. Hold respect for that reality. Treat people the way you’d want to be treated in the same moment.
A strong offboarding process gives structure that ensures network monitoring, backups, security, and line of business apps keep running. It also helps your team keep working while people change around them. With clear steps, every project feels less chaotic.
If you approach each handoff with empathy, clear requirements, and a repeatable checklist, you build trust. You set your business up for long-term stability with your new provider and a clean break from the old providers.
