12 Warning signs that it may be time to change IT providers
Changing IT providers is not a decision most organizations make enthusiastically.
The relationship touches users, administrative passwords, licences, backups, servers, networks and sometimes years of history. Even when service is disappointing, concern about a difficult transition often causes the business to wait.
Waiting too long creates its own risk. The weaker the documentation and the less clear the ownership, the harder the transition becomes when an incident finally forces the issue.
These are common signs that an organization should at least reassess its IT relationship.
Before changing providers: confirm what must move with you
A transition is safer when ownership and dependencies are visible before access is revoked. Use this short list to separate what should remain under your control, what needs verification and what should transfer in an agreed order.
- Keep under your control: the domain, Microsoft 365 tenant, emergency administrator accounts and change approvals.
- Verify before the transition: DNS, backups, encryption keys, firewalls, network, vendor portals, licences, renewals and available documentation.
- Transfer in an agreed order: users and data, applications, devices, cloud services, vendor access and recovery responsibilities.
You do not need to sign a full IT relationship to start this clarification. A bounded independent review can establish the facts, unknowns and next decision.
01The same problems keep returning
An isolated incident is normal. A problem that returns every week often means the symptom is being handled while the underlying cause remains.
Examples include:
- Outlook or Teams repeatedly stops working;
- Wi-Fi remains unstable in the same areas;
- user profiles keep becoming corrupted;
- a critical printer repeatedly disappears;
- server storage is always nearly full;
- the same accounts keep locking;
- patching causes the same interruption each time.
A useful provider should distinguish immediate troubleshooting from durable correction.
02Nobody clearly knows who owns administrative access
Domains, DNS, Microsoft 365, firewalls, backups, hypervisors, applications and provider portals need clear ownership.
Warning signs include:
- accounts tied to a personal email address;
- a former technician remains the only administrator;
- nobody knows where passwords are stored;
- the customer has no emergency-access path;
- shared accounts have no owner;
- MFA methods belong to an unknown device.
The provider may manage access day to day, but the organization must retain governance and a recovery path.
03Documentation exists only in one person’s memory
Useful documentation does not need to become a novel. It should make it possible to understand quickly:
- core systems;
- dependencies;
- suppliers;
- contracts and renewals;
- administrative identities;
- backups;
- network addressing;
- onboarding and departure procedures;
- known risks;
- pending decisions.
When every question must wait for “the person who knows that,” the environment is fragile.
04Tickets are closed without explanation or follow-through
A closed ticket is not necessarily a resolved problem.
The user and manager should be able to understand:
- what happened;
- what was corrected;
- whether the problem may return;
- what preventive action is required;
- who still owns the next step.
Technical communication does not need to be long, but it must be useful.
05Backups are green, but no restoration is proven
A green status shows that a job completed. It does not prove that a server, VM, file or Microsoft 365 mailbox can be restored within an acceptable timeframe.
Ask:
- which recovery point was tested;
- what was restored;
- how long it took;
- who owns the required access and keys;
- where copies are stored;
- whether a copy is protected from deletion or encryption.
Our article about restore testing explains what a useful exercise should prove.
06Security is reduced to “antivirus is installed”
Modern security also involves:
- identities and MFA;
- administrative privilege;
- unmanaged devices;
- patching;
- phishing;
- unauthorized applications;
- logs and alerts;
- backups;
- response when an endpoint is compromised.
The tool matters, but the ownership around the tool matters more.
07Employee onboarding and departures are improvised
A new employee should receive only the access required. A departure should remove access promptly, preserve needed data and document transfers.
Weaknesses include:
- accounts left active;
- unused licences;
- mailboxes without an owner;
- phones still connected;
- OneDrive data that is difficult to transfer;
- groups and sharing permissions that are never reviewed.
The process should be repeatable rather than reinvented each time.
08Recommendations arrive only after a failure
A good IT partner should not replace equipment unnecessarily, but should not discover every risk during an emergency either.
The organization should have a practical view of:
- equipment age;
- storage capacity;
- systems approaching end of support;
- important renewals;
- single dependencies;
- projects that should be planned;
- risks consciously accepted.
Planning does not require a massive budget. It mainly avoids preventable surprises.
09The provider avoids questions about licence and contract ownership
Microsoft 365 licences, domains, certificates, subscriptions, telecommunications and backup services should have understandable ownership.
A transition becomes dangerous when the customer does not know:
- what it owns;
- what is rented;
- what expires;
- what depends on the provider’s account;
- what can be transferred;
- what must be replaced.
Those answers should exist before separation, not be discovered during it.
10The internal team cannot get the escalation it needs
An organization may have a capable internal technician and still require help with:
- a complex outage;
- Microsoft 365 and identity;
- a firewall or VPN;
- a server or hypervisor;
- a migration;
- a security investigation;
- disaster recovery.
A co-managed IT model should strengthen the internal team rather than remove control or add another queue.
11Billing is unpredictable because scope is unclear
IT work will never be perfectly uniform. Projects, emergencies and acquisitions create variation.
The customer should still understand:
- what is included;
- what is a project;
- what requires approval;
- how on-site travel is handled;
- what belongs to another supplier;
- which responsibilities remain internal.
Clear scope reduces conflict and speeds decisions.
12Trust has been replaced by avoidance
The simplest sign may be human: managers delay calling because they expect a defensive response, responsibility transfer or unexplained invoice.
The IT relationship must allow honest discussion of errors, risks and limits. A serious provider does not need to pretend everything is perfect.
How to prepare a transition without creating a crisis
A controlled transition begins with inventory, not the immediate removal of the former provider’s access.
Collect:
- domains and DNS;
- Microsoft 365 and other cloud services;
- administrative identities;
- licences and renewals;
- telecommunications;
- firewalls, switching, Wi-Fi and VPN;
- servers, hypervisors and storage;
- backups and encryption keys;
- line-of-business applications;
- available documentation;
- contracts and suppliers;
- open incidents and known risks.
Then define the transfer order and the date when former access will be revoked.
What not to do
Avoid:
- disabling every account before recovering essential access;
- changing DNS without an inventory;
- deleting old logs or tickets;
- moving backup systems without proving restoration;
- announcing separation before a continuity plan exists;
- allowing two providers to send problems back and forth without one owner.
The transition needs an accountable lead.
A second opinion may be enough
A review does not always lead to a full replacement.
You do not need to sign a full IT relationship to get help at this stage. A bounded review can clarify the situation before any provider-change decision.
Sometimes the right result is to:
- clarify responsibilities;
- document access;
- correct a backup weakness;
- strengthen Microsoft 365;
- add senior escalation;
- establish a plan over several months.
UNITECH can provide a second opinion or own a complete transition, depending on what the organization discovers.
Request an MSP second opinion
If you want clarity before changing anything, our MSP second-opinion assessment reviews governance, access ownership, documentation, licensing, backups and lifecycle risks. The result may confirm the current relationship, clarify the corrections to request or help plan a controlled transition.