When your IT provider gets acquired, it is natural to start watching for changes. Will the people you know stay? Will response times change? Will you be moved to different systems? Will your business still get the same level of attention?
Those are reasonable questions, but an acquisition can also expose something that was harder to see before: Your IT provider may have been supporting your technology without anyone truly managing technology for the business.
The old relationship may have worked because you knew who to call. A longtime technician understood your environment. The owner was accessible. Your office manager knew how to get something escalated when necessary.
Those relationships can make a traditional IT support model work remarkably well.
When an acquisition changes them, the limitations of that model can become much easier to see.
So if your IT provider has been bought, do not evaluate the new relationship only by asking whether service has gotten worse.
Use the transition to look at the relationship more closely.
1. Did You Lose the People Who Know Your Environment?
Technology environments develop history. Someone knows why a particular application was configured a certain way. Someone remembers the issue you had two years ago. Someone understands which employees work remotely, which vendors require access and which systems are especially important to the business.
That institutional knowledge has real value. After an acquisition, you may begin working with a larger pool of technicians, different account contacts or a centralized support team. None of those changes is inherently bad.
The question is whether the knowledge that used to live in a few trusted relationships has been successfully transferred into documentation, process and a team that understands your environment.
Pay attention if you are:
- repeatedly explaining the same environment to new technicians;
- experiencing more handoffs before an issue reaches the right person;
- getting recommendations that do not seem connected to how your systems actually work;
- discovering that important history existed primarily in one person’s head.
Losing a familiar technician is inconvenient. Losing the accumulated understanding of your environment is a business risk.
2. Have You Become a Smaller Fish in a Much Bigger Pond?
Another post-acquisition change is less technical but just as noticeable: You may stop feeling like a client that matters.
Before the acquisition, you might have known the owner, account manager or engineers supporting your business. They recognized your employees. They understood when something was genuinely urgent even if it did not fit perfectly into a ticket category.
As the provider grows, the relationship can become more standardized. That does not automatically mean worse service. A larger organization may bring additional resources, capabilities and depth, but scale can change the client experience.
Watch for signs that:
- you rarely speak with the same people twice;
- unusual issues require several layers of escalation;
- account conversations feel increasingly generic;
- the provider understands the ticket but not the business behind it;
- it has become harder to reach someone empowered to make a decision.
The goal is not to have an IT company where everyone knows your name. The goal is to work with a provider that knows your business well enough to understand what matters and respond accordingly. There is a difference between personal service and simply being treated like an account number.
3. Are You Discovering How Much Your Own Team Was Always Managing?
Even before the acquisition, someone inside your company may already have been filling gaps in the IT relationship. Often it is an office manager, firm administrator or operations leader.
They may have been:
- following up on unresolved tickets;
- coordinating the IT provider with other technology vendors;
- deciding what needed escalation;
- keeping track of recurring issues;
- translating technology problems for leadership;
- figuring out who needed to do what next.
When the MSP relationship is familiar and responsive, this internal work can feel like normal coordination.
An acquisition can make the burden more visible because the shortcuts disappear. There are new processes to learn, unfamiliar contacts and more effort required to get the right people involved.
That does not necessarily mean the acquisition turned your office manager into the IT manager.
It may reveal that technology-management responsibility was never truly outside the business in the first place.
Your office manager should be an important point of contact. They should not have to manage the company that is supposed to manage your IT.
4. Are Problems Still Getting Resolved?
One of the easiest things to measure after an acquisition is whether support still works, but do not look only at response time. A ticket can receive an immediate acknowledgment and remain unresolved for days.
A better question is: Is someone taking ownership of the problem until it is actually fixed?
Watch for:
- recurring issues that keep coming back;
- tickets moving repeatedly between technicians;
- temporary workarounds replacing real resolution;
- long waits for escalation;
- employees adapting their work because the underlying problem persists.
This is where support quality becomes visible. Good IT support should solve problems efficiently and thoroughly. If that capability deteriorates after an acquisition, you have a service problem regardless of who owns the provider.
5. Are Technology Decisions Still Being Made Around Your Business?
Acquiring companies often standardize tools, platforms and processes across their client base.
That can be entirely reasonable. Standardization may improve consistency, simplify support or strengthen security.
The issue is not whether your provider has preferred technology. The issue is whether the decisions being made still make sense for your business.
If you are being asked to change a security platform, backup solution, network technology or another important system, you should understand:
- what problem the change solves;
- why it fits your environment;
- what risk it reduces;
- what disruption it creates;
- what value the business receives from making the change.
“We use this across all of our clients” explains the provider’s operating model.
It does not, by itself, explain why the decision is right for you.
6. Who Is Responsible for the Whole Technology Picture?
This is the bigger question an acquisition gives you an opportunity to ask.
Most traditional MSP relationships are centered on important functions such as:
- help desk support;
- device management;
- infrastructure;
- backups;
- security tools;
- patching and maintenance.
But as a business grows, those services do not answer every technology question leadership faces.
- Who looks across all of the systems, vendors and business priorities?
- Who identifies recurring problems that cross multiple technologies?
- Who determines what needs attention first?
- Who helps leadership understand risk and investment decisions?
- Who coordinates internet, phones, applications, cybersecurity, infrastructure and other technology vendors?
- Who owns an issue when it falls between two providers?
If the answer is your office manager, a partner, an owner or whoever happens to have enough time to deal with it, you may not have an IT support problem.
You may have a technology-management gap.
And changing from one traditional MSP to another may simply recreate it.
Your IT Provider Was Acquired. Should You Leave?
Not automatically. An acquisition may bring more resources, new capabilities and stronger processes. It may also create disruption.
Evaluate what is actually happening in your business.
The relationship may still be working well if:
- the people supporting you understand your environment;
- your business still receives meaningful attention;
- issues are being resolved;
- technology recommendations make sense for your organization;
- accountability remains clear.
It is worth looking more closely if:
- you are constantly starting over with unfamiliar people;
- your business increasingly feels like a small account inside a large system;
- your internal team is spending more time coordinating the provider;
- recurring problems are not being resolved;
- technology decisions feel driven by the provider’s standardization rather than your needs.
Then ask one question that goes beyond the acquisition itself: Who is actually responsible for making technology work for the business?
A smaller company may operate perfectly well with responsive IT support and a few knowledgeable people internally filling the gaps.
As the business grows, the technology environment becomes more complex. There are more employees, applications, vendors, security requirements and investment decisions.
At some point, the question is no longer simply: “Who fixes IT when something breaks?”
It becomes: “Who is responsible for making all of this work together?”
Use the Acquisition as a Reason to Reevaluate
If your IT provider has been acquired, you do not need to replace them simply because ownership changed.
But you should use the transition to examine what you are actually getting.
Has the acquisition changed the quality of the relationship?
Has your business become less important to the provider?
Has more responsibility shifted onto your own staff?
And, perhaps most importantly, was anyone ever truly managing technology for the business beyond keeping systems running and responding to support requests?
Total Technology Resources was built around the belief that growing businesses need more than good IT support. They need a technology partner that understands the business, coordinates the moving pieces and takes responsibility for helping leadership make better technology decisions.
An acquisition may be what causes you to reevaluate your IT provider. The more important question is whether the relationship you choose next solves the problem you actually have.
When you call us, you speak directly with experienced, dedicated engineers who understand your network infrastructure in Philadelphia, your regulatory challenges, and your long-term business goals. Contact Total Tech Resources today!
About the Author: Justin Colantonio
Justin Colantonio is the Managing Partner and Co-Founder of Total Technology Resources. With more than two decades of experience in IT and systems management, including consulting for the City of Philadelphia’s 911 system, Justin helps businesses make better decisions about technology, infrastructure and cybersecurity. He is the co-author of Managing Your Business Risk in the Cybersecurity Minefield and frequently speaks on technology and digital security.