What It Actually Costs to Switch MSPs (And How to Keep the Bill Down)

Home
/
Blog
/
What It Actually Costs to Switch MSPs (And How to Keep the Bill Down)

Your CFO asks what the switch will cost, and nobody in the room can answer. 

Switching MSPs costs more than the figure in your termination clause. The full bill has four parts: the early termination fee, overlap billing while both providers run in parallel, licenses and subscriptions that cannot transfer, and the hours your own team spends on the transition. Your Master Services Agreement covers the first part. Nothing documents the other three, which is why most estimates come in low. 

You have three candidate providers, a help desk queue that proves the current one is not working, and a contract clause mentioning liquidated damages and pass-through commitments without producing a single number. Every guide says check your termination clause. You checked it. You are no closer. 

So the project stalls. Not because leaving is technically hard, but because finance will not approve a cost nobody can size, and the only people who could size it are the two providers with a stake in the answer. 

Here is what is actually in the bill. 

Put a number on it first

Book a 30-minute call and we will walk your contract terms and environment with you, then give you a realistic range for the exit fee, the overlap and the licence exposure. You leave with a figure you can take to finance, whether or not you switch to us.

What does it cost to switch MSPs?

Switching MSPs generates four costs. An early termination fee applies if you leave mid-term. Overlap billing runs for two to eight weeks while both providers operate in parallel. Licenses bought through your provider may have to be repurchased rather than transferred. And your own team absorbs 60 to 90 days of project work. Only the first appears in your agreement. 

That asymmetry is the whole problem. Finance budgets the number it can find and absorbs the rest as a surprise, usually two months in, when the duplicate invoice arrives and nobody remembers approving it. 

The four costs of switching managed IT providers

CostWhen it landsWhat drives the size
Early termination feeAt notice, or on the final invoiceMonths remaining, and how the clause is written
Overlap billingAcross 2 to 8 weeks of transitionLength of the parallel run, and whether partial months are prorated
Licence and subscription changesAt cutover and the following renewalCSP terms, partner alignment, annual commitments
Internal hoursDiscovery through stabilizationEnvironment complexity and the quality of existing documentation

Work through them in that order. The first two are negotiable. The second two mostly are not. 

Early termination fees: the structures you will actually find

Managed services agreements use one of five termination structures: a percentage of the remaining term, the full remaining balance, a flat cancellation fee, a clawback of discounted onboarding, or nothing beyond the notice period. 

Five early termination structures, and what each one means for you

StructureWhat you payRoom to negotiate
Percentage of remaining termA share of the months left on the contractModerate. The percentage and the months counted are both arguable.
Full remaining balanceEvery month left, in fullHigh. You receive nothing for those months, which weakens the clause.
Flat cancellation feeA fixed sum, regardless of timingLow. Usually a round number nobody revisits.
Onboarding clawbackDiscounts or free months granted at signing, recoveredModerate. Often prorated against time served.
Notice period onlyThe remaining notice, and nothing elseNone needed.

A percentage of the remaining term is the most common structure, and the percentage itself varies widely between providers. The clawback is the one that catches people out. Your provider waived onboarding, or gave you three months free at signing. Terminate before the term ends and that discount becomes recoverable. It will not sit in the termination section. It sits wherever the discount was granted, which is usually the schedule nobody reread. 

Then there is the wording, and here most buyers draw the wrong conclusion. A clause reciting that the fee is liquidated damages and not a penalty looks authoritative. It carries less weight than it appears to. 

Under the Restatement (Second) of Contracts, section 356, damages can be fixed in advance only at an amount that is reasonable in light of the anticipated or actual loss and the difficulty of proving that loss. A term setting an unreasonably large sum is unenforceable as a penalty. Courts apply that test to the substance of the number, not the label attached to it, and reviews of California and New York decisions have found clauses struck down as penalties despite reciting the standard “reasonable estimate, not a penalty” wording. 

The practical read: proportionality is what decides enforceability, not drafting language. A fee that recovers a real, hard-to-measure loss sits on solid ground. A demand for 100 percent of a remaining three-year term, for service you will never receive, is the kind of number that invites a challenge. That is useful leverage, and it is also a reason to take legal advice rather than act on a blog post. 

Knowing why the fee exists helps you negotiate it. Provider costs land up front. Onboarding, documentation, discovery and tooling all hit in the first few months, and year one often runs at break-even or worse. The exit fee recovers an investment rather than punishing a decision. Open on those terms and you will get further than treating it as a hostage situation. 

This article offers practical guidance, not legal advice. Have counsel read any clause before you act on it.

Can you leave an MSP contract without paying a termination fee?

Sometimes. Termination for convenience means you are leaving because you want to, and you pay whatever the contract says. Termination for cause means the provider materially breached the agreement, and the fee usually falls away. Cause requires documented evidence and, in most agreements, a written cure notice giving the provider around 30 days to fix the problem first. 

Cause is where the money sits. It is also where most companies discover they have undermined themselves. 

A material breach has to be demonstrable: repeated missed response targets, an unaddressed critical outage, a security obligation the provider never met. Eighteen months of frustration with nothing in writing gives you a feeling, not a case. Your service level agreements define what counts as a miss, so start there, then pull the ticket history from your provider’s PSA platform to prove it. 

Most agreements also set a cure period, commonly 30 days. You give written notice of the breach, the provider gets that window to fix it, and only then can you terminate for cause. Skip the cure notice and the claim weakens regardless of the underlying facts. 

Find the auto-renewal date before anything else. Plenty of agreements renew for a full term unless you give notice inside a narrow window, often 60 or 90 days before expiry. Miss it by a week and the mid-contract question returns for another year.

How long should the overlap period between MSPs be?

Plan on two to eight weeks of parallel running, and expect to pay both providers for part of it. During the overlap the incoming provider builds an asset inventory, deploys RMM and monitoring agents and shadows live tickets, while the outgoing provider still answers the phone. Complex or poorly documented environments need the longer end of that range. 

This is the line item that gets cut, and cutting it is how transitions fail. End the overlap early and you find out what nobody documented at the worst possible moment, with no one contractually obliged to help.

When we take over an environment mid-transition, the gap is almost never the thing the client flagged. It is the undocumented dependency: a scheduled task on a server nobody owns that moves a nightly export into the finance system, or a line-of-business application still authenticating against a service account the outgoing provider created and never wrote down. Nobody is hiding these. They accumulate over years and live in one engineer's head. Four weeks of parallel running surfaces them while someone is still there to explain them. Two weeks usually does not.

The partial month is the awkward part. Many providers do not prorate, so a mid-month handover means a full month’s billing from both sides. 

That duplicate month buys you something. A provider paid through month end has no reason to rush you out, and some will leave their monitoring in place read-only as a safety net until the billed period ends. The same provider, cut off on the 14th, has every reason to be unavailable on the 15th. 

Set the handover date near a billing boundary if you can. If you cannot, treat the duplicate month as project cost rather than something to argue about. 

Know your handover before you commit

Send us your current contract terms and a rough picture of your environment. We will tell you which licenses transfer, which do not, and what your outgoing provider is obliged to hand over, in a written summary you can use in your own negotiation.

Licenses that do not transfer

Licenses you bought through your provider’s CSP agreement do not automatically follow you, and the window to cancel them is far shorter than most buyers expect. 

Microsoft 365 causes most of this. Under the New Commerce Experience, Microsoft’s own cancellation policy gives licence-based subscriptions a prorated refund only within seven calendar days of purchase, and that window does not reopen until the subscription renews into a new term. Seven days, counted in calendar days. After that, the seats are committed for the rest of the term regardless of who manages your IT. The same logic applies to EDR tooling, backup platforms and anything else folded into your monthly rate. 

Partner alignment decides how much it hurts. If your incoming provider holds the same vendor partnerships, most subscriptions move across, though your pricing shifts because the new provider sets their own margin. If they do not, you are cancelling on one side and buying fresh on the other, sometimes with a fee for the privilege. 

Granular Delegated Admin Privileges deserve their own look. GDAP relationships between a partner and your Microsoft Entra ID tenant have defined durations and have to be ended individually. They do not disappear when the contract does, and a relationship left standing is a live administrative path into your environment. 

Put the same question to both providers before you sign: which of our current subscriptions can you take over, and which have to be repurchased? Get it in writing. It belongs alongside the other questions to ask before hiring a managed services provider, and most buyers only think of it on the way out rather than on the way in. 

Bundled hardware needs the same treatment. The firewall included in your monthly fee may be leased rather than owned, and the buyout figure is a cost nobody put in the budget. 

The hours your own team spends

Budget 60 to 90 days of elapsed time and a significant share of your IT lead’s capacity. Thin documentation makes that share bigger. 

Your people run discovery sessions, verify credentials, approve gates, test restores and answer questions from two providers at once. Someone has to own the timeline and hold the authority to pause it when a step fails. Whatever else that person was doing slows down. 

Six months left on your contract sounds comfortable and is not. Running a selection process, giving contractual notice and completing a handover inside six months works, but it leaves no slack for a provider who drags their feet on documentation. Start earlier than feels necessary. 

This cost never reaches an invoice, which is exactly why it gets left out of the business case. Put a rough figure on it so the comparison against staying is honest. 

How to bring the total down before you give notice

The highest-leverage move costs nothing: secure ownership of your own environment before anyone knows you are leaving. 

Auditors already expect this. The NIST Cybersecurity Framework 2.0 includes a subcategory, GV.SC-10, requiring that supply chain risk management plans cover activities after a partnership or service agreement concludes, with implementation examples that name terminating supplier relationships and mitigating the data and system risks that termination creates. Its control-level counterpart, SA-9 in NIST SP 800-53, requires you to define and document oversight and user roles for external system services. In both cases, the inventory you need for an orderly exit is the one you were supposed to be keeping anyway. 

Your leverage peaks the day before you give notice and drops the moment you do. So do this quietly, and do it first. 

  • Confirm your own people hold Global Administrator in Microsoft Entra ID. Microsoft recommends two cloud-only emergency access accounts permanently assigned that role, which is a reasonable standard to hold your provider to. 
  • Log in to your domain registrar directly. Check the registrant is your company and that you can edit DNS without calling anyone. 
  • Get backup console access, a list of what is covered, and the date of the last successful test restore. Then run one. 
  • Export the shared password vault, and request the documentation set from whatever platform your provider uses, typically IT Glue or Hudu. 
  • Collect firewall credentials and a current configuration export. 
  • Get an itemized licence list showing what is billed through the provider and what you hold directly. 
  • In regulated environments, collect the compliance evidence too: the signed BAA, SOC 2 reports, and any control documentation your auditor will expect to see without a gap. 

If asking for all this feels awkward, you have a ready-made justification. Cyber insurance applications increasingly ask for an inventory of privileged accounts and who owns them, with evidence of how they are controlled. A provider has a hard time arguing against a question their client’s underwriter is already asking. 

When you give notice, put the handover expectations in the notice itself: documentation, network diagrams, asset inventory, open tickets, vendor contacts, licence schedules and a named technical contact for the transition. A provider who agreed in writing behaves differently from one you are chasing afterwards. 

After cutover, removal matters as much as handover. Uninstall the outgoing provider’s RMM and remote access agents from every endpoint, revoke GDAP relationships, remove connected applications from your tenant, and rotate every shared credential they held. Expect EDR tamper protection to slow this down, since agents are built to resist exactly this kind of removal. It is worth the effort: CISA, the NSA and MS-ISAC warned in joint advisory AA23-025A that legitimate RMM software generally does not trigger antivirus or antimalware defenses and is used by attackers as a backdoor for persistence and command and control. A forgotten agent is a standing exposure, not untidiness. 

Getting this sequence right is most of what separates a clean switch from an expensive one. Some organizations work through it and conclude the answer is not a different provider at all, but a different scope of managed IT services than the one they are buying today. That is a legitimate outcome of finding the right IT outsourcing partner rather than a failure of the process.

What changes across multiple sites

Everything above holds at 40 users. At 800 across several locations, three things shift. 

You will have more than one tenant, more than one circuit provider, and GDAP relationships that unwind one at a time. Building the access map alone usually runs a week or two longer than the single-site version. 

Your cutover becomes a sequence rather than an event. Move low-risk sites first, leave identity and DNS until last, and lower DNS TTL values several days ahead so records propagate inside your maintenance window instead of after it. Give each site its own go or no-go rather than betting the estate on one decision. 

Change control applies too. Anything touching identity or DNS across locations goes through your change advisory process. That adds calendar time and prevents the one failure that takes every site down together. 

Frequently asked questions

Can we switch MSPs mid-contract?

Usually yes. Your agreement sets the cost and the timing. Check the notice period, the early termination structure and the auto-renewal date, then work out whether leaving now or at term end costs less. 

What migration costs apply when switching providers mid-contract?

The early termination fee, overlap billing while both providers run, any licenses or subscriptions you have to repurchase rather than transfer, and your own team’s time. Some providers also bill offboarding as a separate project. 

What data export and contract exit terms should we require?

That your credentials, documentation and data belong to you. That the provider hands over administrative access and documentation within a defined window. And that transition assistance is either included or quoted up front rather than invented at the end. 

How long does an MSP switch take?

Most run 60 to 90 days from signed agreement to full cutover, with two to eight weeks of parallel running. Larger or poorly documented environments take longer. 

What if our current provider stops cooperating after we give notice?

This is why you secure admin access, domain control and backup ownership before giving notice rather than after. A written exit cooperation clause gives you something to point at. Credentials you already hold give you something better. 

See the whole picture first

Tell us what is going wrong with your current setup and we will map what a transition would involve: the sequence, the realistic timeline, and where every cost lands. No obligation to switch, and you keep the plan either way.

Recent Posts

Essential Guides, Insights, and Case Studies for IT Solutions

Executive considering floating icons for cost, timeline, systems, and staffing, illustrating what it costs to switch MSPs

Your CFO asks what the switch will cost, and nobody in the

Illustration of a managed IT services RFP with proposal checklists, vendor scoring tables, and icons representing cybersecurity, infrastructure, and IT support.

Choosing a managed service provider (MSP) is a multi-year decision. The provider

Two IT professionals reviewing server upgrade graphic on monitor in data center, illustrating Windows Server 2016 end of life migration options

Windows Server 2016 receives its last security update on January 12, 2027.