Separate service gaps from a difficult month
Start with specific incidents rather than a general feeling that support is poor. Record when you asked for help, the business impact, who responded and what remained unresolved. Repeated access problems, unexplained charges or unclear ownership of backups warrant different questions from a single delayed ticket. Compare the experience with your current written scope and escalation process.
If it is safe and practical, ask your current provider for a written improvement plan and a review date. You may discover a scope mismatch that can be resolved without moving. If you decide to change, turn the unresolved gaps into requirements for the next agreement—not promises that any new supplier will automatically fix them.
Check the agreement before setting a move date
Find the renewal date, notice period, termination provisions and any transition charges. Check which licenses, equipment leases and vendor subscriptions sit outside the support agreement. Ask who can transfer them and whether access depends on the outgoing provider's account. Do not assume ending support also cancels every related service.
Seek legal advice for disputed terms or obligations. A new MSP's sales proposal is not a substitute for reviewing your existing contract. Agree a realistic handover window before issuing notice, especially if your business cannot tolerate interruptions during payroll, trading hours or a seasonal peak.
Keep business ownership and access explicit
Prepare an inventory of your email tenant, domains, devices, network equipment, business applications, backups and third-party vendors. Confirm which accounts belong to your company, who has administrator access and where recovery information is held. Request documentation through an authorized secure process; do not put passwords, recovery codes or confidential customer records in a matching inquiry.
Ask the incoming provider how it will validate access and recovery before removing old tools or permissions. Avoid blanket access changes until responsibilities and dependencies are understood. Any access revocation should be planned by authorized people, with continuity and security considered together.
Compare the replacement against your actual requirements
Give each prospective MSP the same business brief: locations, employee count, working hours, essential applications, recurring problems and desired transition timing. Ask which services are included, which require a project and who coordinates with software vendors. Distinguish a response commitment from a resolution commitment, and remote help from on-site coverage.
- Who owns escalation when an incident spans several vendors?
- How will you assess inherited systems, and what findings may change the proposed scope?
- What are the recurring fee, onboarding charge, exclusions and minimum contract commitments?
- Can our company retain licenses, documentation and administrator ownership if we leave?
Request written answers and verify relevant references independently. Use the free provider selection checklist to compare proposals without treating the lowest headline price as the complete cost.
Agree a handover with clear acceptance checks
A transition commonly starts with discovery, access verification and a documented onboarding plan. Specify the outgoing and incoming providers' responsibilities, your internal decision-maker and a fallback contact. List tool removals, backup changes and license transfers separately so nothing is assumed complete merely because the support contract has started.
Before signing off, confirm users can obtain support, essential applications work, the agreed recovery checks have been performed and ownership records are current. Record unresolved items and their owners. A planned transition can help you manage uncertainty, but it cannot guarantee zero disruption. This guide is general purchasing advice; PipelineForge introduces independent providers and does not deliver IT, legal, cybersecurity or compliance services.