IT Support & MSPs

How do I survive switching IT providers without disaster?

Switching MSPs is daunting but sometimes necessary. Learn the step-by-step process to transition IT providers without downtime, data loss, or chaos.

centrexIT Team 8 min read

Key Takeaways

  • Organizations report an average 19% drop in IT operating expenses when switching to a better-fit MSP
  • The biggest transition risk isn't technical - it's knowledge loss from undocumented systems and tribal knowledge
  • Demand full documentation handoff: admin credentials, network diagrams, license keys, and vendor contacts
  • A good new provider will shadow your current environment for 30 days before full cutover
  • Never let your current provider know you're switching until you've secured all credentials and documentation

You know your IT provider isn’t working. Response times are slow. Problems keep recurring. Strategic guidance is nonexistent. But you stay because switching feels risky. What if the transition causes downtime? What if the new provider is worse? What if something falls through the cracks?

These fears are understandable - and they keep businesses stuck with mediocre IT support for years longer than they should be. Here’s how to make the switch without the disaster.

Signs It’s Time to Switch

Before we cover the “how,” let’s confirm the “whether.” Consider switching if:

  • Response times are consistently slow - you wait hours or days for help with critical issues
  • The same problems keep recurring - fixes are band-aids, not solutions
  • No proactive communication - you only hear from them when something breaks
  • No strategic guidance - no technology roadmap, no budget planning, no business alignment
  • Security is an afterthought - no regular security reviews, patching is inconsistent, no compliance support
  • Billing surprises - unexpected charges, unclear invoicing, scope creep
  • You’ve outgrown them - your needs have evolved but their capabilities haven’t
  • Poor documentation - they can’t explain your environment because nothing is documented

If three or more of these resonate, it’s time for a serious conversation about change.

The Transition Playbook

Phase 1: Preparation (Weeks 1-4)

Secure Your Assets First

Before telling your current provider anything, make sure you own and control:

  • Admin credentials for all systems (firewalls, servers, cloud accounts, domain registrar)
  • Microsoft 365 / Google Workspace global admin access
  • Domain registration login credentials
  • SSL certificate details and renewal information
  • Software license keys for all business applications
  • Vendor contact information and account numbers (internet provider, phone system, etc.)
  • Network documentation (IP addresses, VLAN configurations, firewall rules)
  • Backup locations and credentials

This is critical. If your current MSP controls your admin credentials and the relationship turns adversarial, you could be locked out of your own systems. Every business should maintain a secure, independent record of all administrative access.

Select Your New Provider

When evaluating new providers, ask:

  • How do they handle transitions from other MSPs?
  • What does their onboarding process look like?
  • Will they shadow the current environment before taking full responsibility?
  • What documentation do they produce during onboarding?
  • Can they provide references from clients who switched to them?
  • What’s their approach to cybersecurity, compliance, and strategic planning?

Review Your Current Contract

Check your existing MSP agreement for:

  • Termination notice period (typically 30-90 days)
  • Early termination fees (if applicable)
  • Data ownership clauses - your data should be yours
  • Transition assistance obligations - does the contract require the outgoing MSP to cooperate?
  • Equipment ownership - who owns the hardware on your premises?

Phase 2: Onboarding the New Provider (Weeks 4-8)

The Discovery Phase

A good new provider will conduct a thorough discovery of your environment:

Discovery AreaWhat They Should Document
Network infrastructureSwitches, firewalls, access points, IP schemes, VLANs
Servers and workstationsHardware inventory, specifications, age, warranty status
Cloud environmentMicrosoft 365 configuration, Azure/AWS resources, SaaS inventory
Security postureCurrent tools, policies, gaps, vulnerability assessment
Backup and DRBackup targets, schedules, retention, last test date
Users and accessActive Directory, user accounts, group policies, permissions
Vendor relationshipsISP, phone provider, line-of-business app vendors
Business contextCritical applications, peak hours, compliance requirements

This discovery should happen before the old provider is removed. The new provider needs to understand everything before they take the wheel.

Shadow Period

The best transitions include a 30-day shadow period where the new provider:

  • Monitors your environment alongside the outgoing provider
  • Identifies potential issues before they become the primary contact
  • Builds internal documentation
  • Meets key staff members and understands workflows
  • Deploys their monitoring and management tools in parallel

Phase 3: Cutover (Weeks 8-10)

Notify Your Current Provider

Once your new provider is fully prepared:

  1. Provide written termination notice per your contract terms
  2. Request formal documentation handoff
  3. Specify the transition date
  4. Request cooperation during the transition period
  5. Document everything in writing

Execute the Transition

A well-planned cutover typically happens over a weekend or after hours:

  • Replace monitoring and management agents on all devices
  • Update DNS, firewall rules, and network configurations as needed
  • Transfer security tools (EDR, email filtering, backup)
  • Test all critical systems and applications
  • Verify backup functionality
  • Update vendor contacts so the new provider is the authorized contact
  • Switch support contact information for employees

The “Day One” Communication

Your employees need clear communication:

  • Who is the new IT provider?
  • How do they contact support? (phone, email, portal)
  • What’s the new process for submitting requests?
  • Is there anything employees need to do differently?
  • Who to contact for urgent issues during the transition period?

Phase 4: Stabilization (Weeks 10-14)

The first 30 days after cutover are critical:

  • Heightened monitoring to catch issues quickly
  • Frequent check-ins between the new provider and your team
  • Documentation refinement as the new provider learns nuances
  • Ticket review to ensure response times and quality meet expectations
  • Feedback loop to address any concerns early

Common Transition Risks and How to Avoid Them

Risk: Knowledge Loss

The fear: “Our current provider knows everything about our systems. The new one will have to start from scratch.”

The reality: That knowledge should be yours, not theirs. If your current provider is the only entity that understands your network, that’s a dependency problem - and another reason to switch.

Mitigation: Demand documentation during the transition. A good new provider will build comprehensive documentation during their discovery phase, often producing better documentation than what existed before.

Risk: Downtime During Cutover

The fear: “Switching providers will cause days of downtime.”

The reality: Well-planned transitions typically result in zero downtime. The shadow period and after-hours cutover minimize disruption.

Mitigation: Schedule the cutover for a weekend or holiday. Have both providers available during the transition window. Test critical systems before declaring the cutover complete.

Risk: Hostile Current Provider

The fear: “Our current provider will make the transition difficult.”

The reality: This happens occasionally, but you’re protected if you’ve secured your admin credentials and documentation upfront.

Mitigation: Secure all admin access before notifying the current provider. Document everything in writing. Review your contract for transition cooperation requirements. If necessary, involve legal counsel.

Risk: Discovering Problems

The fear: “The new provider will find problems we didn’t know about.”

The reality: This is actually a benefit, not a risk. A thorough discovery often reveals security gaps, configuration issues, and ticking time bombs that the previous provider either missed or never addressed.

Mitigation: Budget time and resources for remediation in the first 90 days. This is an investment in your environment’s health, not a failure of the transition.

The Bottom Line

Switching IT providers is a significant decision, but it shouldn’t be a scary one. The businesses that endure bad IT support because they’re afraid of the transition are paying a higher price in slow response times, recurring problems, security gaps, and missed opportunities than the temporary effort of making a switch.

A structured transition - with proper credential control, thorough discovery, a shadow period, and planned cutover - minimizes risk and typically results in dramatically better service from day one.

If your current provider isn’t serving you well, the best time to start planning a transition is now.


Considering a change in IT providers? Contact us for a no-obligation conversation about what a transition would look like for your business.

Have More Questions?

Our team is here to help. Whether you're evaluating IT services or have a specific question about your technology, we're happy to have a conversation.