If You Switch IT Providers, What Comes With You?

Here’s a question many business owners never think to ask their IT provider: if this relationship ended tomorrow, what would walk out the door with you?

Many people assume the answer is nothing. The equipment is in the building. The accounts have the company’s name on them. So it’s all theirs, right? Not always. Depending on how the agreement is structured, some of the technology a business depends on every day may actually belong to the provider.

Take the firewall. It sits between the office network and the internet, and everything the business sends or receives passes through it. At some providers, that device is theirs. The business pays for it every month, relies on it every minute, and doesn’t own it.

That arrangement is invisible right up until the day a business decides to switch providers. Then it matters a lot.

Picture that transition. The incoming provider runs discovery before the switch date, and that’s where it turns out the client doesn’t own their own firewall. The losing provider is ripping it out at cutover. Now the timeline slips. A replacement has to be quoted, ordered, and configured before the handoff can happen. Suddenly, the business is buying a firewall it thought it already had, on short notice, in the middle of a transition it wanted to keep simple. Nothing about the switch gets easier, and the outgoing provider is the reason.

None of this requires anyone acting in bad faith. It’s what happens when nobody decides up front where the line between yours and theirs should sit. So here’s a clear way to draw it.

Fixtures and tools

Think about hiring a plumber. The water heater they install is yours. The wrench they used to install it is not. Nobody expects the plumber to leave the wrench behind, and nobody expects to keep paying for a wrench after the plumber is gone.

Most of what’s in an IT relationship falls on one side of that line, and the test for sorting it is simple: if you would want it to come with you to your next provider, you should own it.

The firewall is a water heater. So are your Microsoft 365 licenses, your password manager, and your domain name. You may pay for some of these through your provider’s monthly bill, and that’s fine; convenient billing and ownership are two different things. These are fixtures of your business. They should be in your name, and if you leave, they go with you.

The monitoring platform, the security operations center, the documentation system, the ticketing system: those are wrenches. They belong to the provider, because you’re paying for a service and those tools are how the service gets delivered. You shouldn’t own them, and you shouldn’t want to. What you should expect is that when the relationship ends, they unplug cleanly and disappear without causing a single problem.

Fair questions

What if the next provider standardizes on a different firewall brand? Most businesses don’t care what’s on the shelf, only that they’re protected. Ownership still works out better. Owning the hardware doesn’t lock the new provider into it; it means any change happens on a planned schedule instead of at cutover. If the equipment conflicts with their preferred stack, they can transition it at its natural refresh point. Nobody should be ripping out a two-year-old firewall just because the new provider likes something else.

What about the things that don’t sort neatly? There are some. Spam filtering and application controls spend months getting tuned to how a particular business actually works, and a replacement starts that learning over from zero. Backups are gray for a different reason: they accumulate history, and no new system can recreate the restore point from a year ago. Whoever owns these, replacing them has a cost that changing the name on the account wouldn’t fix. The test doesn’t settle every case. It gives you the right question to start with.

What about businesses that just want one bill and zero equipment to think about? That’s a reasonable way to buy IT, and it’s why the everything-included model exists. The objection isn’t to bundling. It’s to arrangements where the convenience enjoyed while staying becomes a penalty for leaving. Those are two separate things, and they can look identical on a proposal. Before signing an all-inclusive agreement, it’s worth asking which one you’re getting.

And leasing is its own case. If a provider is financing equipment to spread out a large cost, that’s a different arrangement, and a fine one, as long as everyone understands the terms up front. The problem isn’t leases. The problem is ownership surprises discovered during a breakup.

Why this matters

Switching IT providers is already hard. There’s history, there’s institutional knowledge, there’s the simple disruption of change. Even when everyone behaves well, it’s a heavy lift.

A provider shouldn’t add artificial weight to it. When the main reason a client stays is that leaving would hurt, that pain is covering up a problem the provider should be fixing. The exit should be easy, and the service should be the reason clients stay.

So here’s a practical takeaway. Ask your provider one question: “If we left, what stays and what goes?” A good provider can answer quickly, specifically, and without getting uncomfortable. If the answer is vague, or if the list of things that leave with them includes equipment your business depends on, you’ve learned something important about the relationship before you needed to.

You should own your fixtures. Let the provider own the wrenches.

Stay updated! Get tips and insights delivered to your inbox weekly by subscribing to our newsletter.