Leaving your MSP, and leaving us, in plain terms.
The part of switching nobody discloses upfront
Search for what it is actually like to leave a managed provider, and a pattern repeats across the stories people tell about it.
Access that waits on an invoice
It is common for administrator credentials or console access to stay with the outgoing provider until a final bill is settled, whether or not the bill is actually in dispute.
Help leaving, sold separately
Transition assistance is often offered as a paid add-on, priced high enough to discourage some customers from asking for it at all.
Documentation with an expiration date
Runbooks, configuration notes, and asset inventories that existed the whole time you were a customer can quietly stop being available in the weeks after you are not.
None of this is in the contract you sign on the way in. It tends to show up later, exactly when you have the least room to push back.
This page assumes you are already partway through leaving somewhere, or seriously considering it. If you are still comparing security partners more broadly, the MSSP onboarding checklist answers the standard buyer questions in writing.
What a clean exit looks like
Ask your current provider for these four things in writing before you agree to a transition date. How they respond tells you almost as much as what they hand over.
Full administrator access
Every admin account, service account, and console login touching your environment, transferred or reset under your control. Not summarized. Not partial.
Complete documentation
Network diagrams, configuration notes, runbooks, and asset inventories, handed over in a form you can actually use, not a verbal walkthrough on the way out the door.
Your data, exported
Full exports of your data and records in an open, portable format. Not a summary report, and not a file locked to a tool you are leaving behind.
A defined transition window
A written date range for the handoff, with both sides' responsibilities spelled out, not an open-ended commitment to get to it eventually.
If a provider will not commit any of this to writing, that itself is useful information, before you sign anything else.
The shape of our first 30, 60, and 90 days
The exact pace depends on what discovery finds and the size of your environment. This is the shape of it, not a fixed script.
Days 1 to 30
Discovery, read-only
We start by looking, not touching. Read-only access across identity, devices, and cloud, checked against whatever documentation exists, so we are working from what is actually there.
Days 31 to 60
Standing up controls
We close the gaps discovery turned up, one at a time, in an order we agree with you first. Nothing changes in your environment without a heads-up before it happens.
Days 61 to 90
Steady-state operation
Monitoring, requests, and reporting settle into a regular cadence. You see the environment running the way it is actually running, in the portal, not in a quarterly summary.
This describes the shape of onboarding, not a substitute for the order form, which governs the actual engagement and its timelines.
How you would leave us
We would rather you judge this section skeptically than take it on faith. Here is our stated position: what you keep, what we hand back, and how the handoff runs if you ever decide to leave.
None of it is buried in fine print or held back until you ask. These are the principles we hold to on the way out, stated plainly so you can hold us to them.
What we commit to
- Your data and your documentation are yours. We do not treat either as leverage.
- We design for portability, not lock-in: standard formats and documented configuration, not tooling built to be hard to leave.
- We will not hold credentials or access hostage, for any reason, including a disputed invoice.
- If you ever decide to leave, you get a clean, documented handoff instead of a countdown.
Wherever you are in the decision, get a straight answer.
See the plan structure, or walk the full operated partnership before you decide anything.
Published pricing tiers and a written annual escalator cap, so you always know what staying looks like too.
The full scope of the operated partnership: what we run, what you can see, and the engagements we do not take on.