Considering a different MSP?
Thinking about switching IT providers? Start here.
Changing IT providers should start with what you need to fix and a realistic plan, without pressure to sign.
When trust wears thin
It shouldn’t be your team’s job to chase IT.
Provider relationships usually go sour long before a big outage. Questions go unanswered, the same problems keep coming back, and your people end up chasing IT instead of doing their jobs. Before deciding to switch, it helps to pin down exactly what needs to change.
| What’s going wrong | What we’d agree with you |
|---|---|
| Tickets stay open too long | Someone owns each issue, urgent problems jump the queue, and you can always see what happens next. Response and resolution times go in the service agreement. |
| The same problem keeps returning | We look for the cause, fix it properly and check the fix held, instead of closing the same ticket again next week. |
| Support depends on who answers | Documented procedures and a clear handoff, so everyone gets the same answer. We agree which applications we support and where escalation goes. |
| Your team has to chase every update | Every open issue has a named next step and someone responsible for it. We agree how often you’ll hear from us, and tell you straight away when something is stuck. |
| Communication leaves you guessing | Plain explanations: what’s affected, who’s on it and what happens next. We agree how and when we’ll update you, instead of promising response times we haven’t agreed. |
| Invoices contain unexpected charges | What’s included, what isn’t and who can approve extra work are written down. Monthly service, one-off projects and supplier charges are kept separate, and pricing needs your written approval. |
| Everything starts after something breaks | Monitoring, maintenance and patching are planned work, with someone responsible for each. We review the exceptions and the aging systems with you. Automation only runs where you’ve approved it. |
| You cannot see what your MSP is doing | Regular reviews of what was fixed, what keeps coming back, what maintenance was skipped and what recovery tests showed, in records you can actually read. |
| Your provider does not understand your business | Day-to-day work tied to your business priorities, a roadmap you’ll use, and points where we check progress together. |
This describes how we’d approach each one. Your agreement sets the actual coverage, service levels and pricing.
How a switch works
Five steps, with a decision at each one.
-
Initial technology discovery and assessment
Start with your concerns, your priorities and how your current provider works. The Technology Assessment shows where your technology stands before you commit to anything ongoing.
What you get: A clear statement of the problem, and what to look at next.
-
Review of the existing IT environment
With your permission, we look at users, systems, accounts, vendors, documentation and backups, and note what’s missing. Passwords never go through this website.
What you get: A list of your systems and what they depend on, with the gaps and who owns each piece.
-
Transition planning and coordination
We check notice periods, who owns which accounts, which licences can move and what other suppliers need to do. Then we plan the order, the communication, the sign-offs and a fallback.
What you get: A transition plan, with exclusions, dependencies and commercial terms, for you to approve.
-
Controlled onboarding and implementation
Once you’ve approved the plan, we move access over, set up our tools, brief your people and test as we go. If an approval or a dependency is missing, we pause that step.
What you get: Onboarding checklists, change records and the checks we’ll use.
-
Validation, documentation, and ongoing improvement
We confirm the important workflows work, hand over documentation you can use, and agree what to improve first.
What you get: A record of what was checked, who owns what, and a short improvement list.
Any switch carries some risk. Careful sequencing, a fallback plan and testing keep it manageable, though nobody can promise a change with zero disruption.
Before you decide
You can look closely before you decide.
Start with a conversation or the Technology Assessment, which ends with a summary report of what we found and our recommendations. Anything deeper is quoted separately, and nothing ongoing starts until you approve it.
- Two or three things that keep going wrong, and what they cost you
- Roughly how many people and locations, and what your IT staff handle
- Notice periods, key vendors and timing (nothing confidential)
- What better would look like for you
Questions
What people ask before switching.
Do we have to commit before you evaluate a potential transition?
No. A conversation and the Technology Assessment both come before any commitment, and you approve any transition work before it starts.
Can we switch without disrupting our business?
Careful planning keeps it to a minimum: checking dependencies, piloting changes, using approved change windows and having a way back. Old systems, missing access and an unhelpful current provider can all affect the plan, and nobody can honestly promise zero disruption.
What if our current provider will not cooperate?
We start with your contract, who owns which accounts and what access you’re entitled to, and plan around what’s missing. We can’t force another provider to cooperate or override their contract, but we can help you use the rights you have.
Will our licenses and administrator accounts transfer?
It depends on who owns them and on each vendor’s terms. We check every account, subscription and licence first, then tell you what moves across, what needs replacing and what needs the vendor’s sign-off.
Can you work with our internal IT staff?
Yes. In a co-managed setup your team keeps what it owns and we support the rest. We agree approvals, escalation and access with them before we start.
Will the new agreement stop surprise charges?
Your agreement should separate what’s included, what isn’t, projects and third-party charges, with your approval needed for anything extra. We don’t promise fixed prices or unlimited work, but you’ll know what you’re paying for.
How long does switching MSPs take?
It depends on how well your setup is documented, notice periods, other vendors and what we agree. There’s no standard timeline, and we’ll give you a realistic plan once we’ve looked.
Does changing providers solve all security or recovery gaps?
Not on its own. Security and recovery gaps need their own review, and specialist work, compliance readiness and recovery commitments are agreed separately.
What should we share in the first conversation?
The problems that keep happening, who they affect, who handles IT today and any deadlines. Please leave passwords, client records, contracts and incident details out of the form.
What you’d be switching to
The services behind a switch.
Everyday support
Ongoing support and maintenance, with the work split between us and any IT staff you keep.
Security and recovery
Protection, monitoring and tested backups, set up and agreed as their own part of the service.
Talk to us
What would you want your next provider to do differently?
Tell us what isn’t working. Asking doesn’t commit you to switching, book a meeting or give us permission to contact your current provider.
Please don’t send passwords, contracts, customer records or incident details.
- sales@altivusone.com
- Phone
- (346) 410-0961
- Office address
- 151 FM-407
Suite 200
Argyle, TX 76226
Thank you. Your message has been sent.
Someone from our team will be in touch.