IT outsourcing means handing some or all of your IT work to an outside provider. Boston IT Services Group offers two models: fully outsourced IT for organizations with no internal IT staff, and co-managed IT for organizations that have an IT person or team and want extra hands, tools or after-hours coverage. This page explains how to choose, what to keep in house, how the handover works and which contract terms protect you.
The IT outsourcing Boston organizations ask us about usually takes one of two shapes. Either an outside provider runs all of your IT because you have no IT staff, or the provider works alongside an internal IT person who needs more hands, better tools and someone to cover nights and vacations. We do both. The right choice depends on who you already employ and what you want them spending their time on.
This page is for owners weighing whether to outsource at all, and for internal IT staff evaluating a partner. If you are in the second group: we assume you know your environment better than we do on day one, and we write the engagement around that.
Fully outsourced IT vs co-managed IT
| Fully outsourced IT | Co-managed IT | |
|---|---|---|
| Who it fits | Firms with no dedicated IT staff, or one person doing IT on the side of another job | Firms with an IT manager or small IT team |
| Who sets priorities | You and the provider, through regular planning reviews | Your internal IT lead |
| Help desk | Provider handles all user requests | Shared, split by type, or provider covers overflow and after hours |
| Tools (RMM, EDR, backup, documentation) | Provider supplies and runs them | Provider supplies them; your team gets access too |
| Projects | Provider plans and delivers | Your team leads; provider adds specialists as needed |
| Biggest risk | Too little internal knowledge of how IT works at your firm | Unclear ownership, leading to tickets that fall between the two teams |
| How to manage that risk | Name an internal owner for IT decisions | Write a responsibility matrix and review it quarterly |
Neither model is better in the abstract. A 12-person accounting firm with no IT staff and a 90-person engineering firm with a capable IT manager need different things. For a longer explanation of the second model, see our article on what co-managed IT is and when it fits.
Fully outsourced IT: what we take on
When nobody on staff owns IT, the outsourced IT support Boston businesses need has to cover the full stack. In our fully outsourced model that means:
- A help desk your staff can reach by phone, email or portal, run through our IT help desk in Boston
- Monitoring and patching of computers and servers with an RMM (remote monitoring and management) platform
- Endpoint protection, typically EDR (endpoint detection and response), plus email filtering and MFA policies
- Microsoft 365 or Google Workspace administration, including onboarding and offboarding
- Network and firewall management
- Backup monitoring and periodic restore tests
- Vendor management for internet providers, printers, phone systems and line-of-business software
- Hardware lifecycle tracking and purchasing guidance
- Regular planning reviews with budget recommendations
This is close to what we describe on our managed IT services in Boston page. The difference is mostly framing: outsourcing is the decision to hand IT off, and managed services is the way we deliver it once you do. That list is the full version of our IT outsourcing services. Boston firms with an internal IT person usually take part of it instead, as described next.
Co-managed IT services Boston teams use alongside their own IT staff
Co-managed IT is built around the person you already employ. A solo IT manager cannot be on call every night, an expert in firewalls and Intune and backup software, and also the person who sits with the managing partner to plan next year's budget. Something gives, and it is usually documentation and security maintenance.
Typical co-managed splits we see:
- Your IT manager keeps strategy, business applications, user relationships and vendor decisions. We take monitoring, patching, endpoint security and after-hours alerts.
- Your team handles walk-up requests in the office. We take the remote help desk queue during peak times and overnight.
- Your team runs daily operations. We supply specialists for projects such as a Microsoft 365 tenant cleanup, a firewall replacement or a disaster recovery test.
Internal staff get access to our tools: the RMM console, the ticketing system, the documentation platform. Shared visibility is what stops the "I thought you were handling that" problem.
What to outsource and what to keep
The work that outsources well is repetitive, tool-heavy and measurable. Patching is the classic example. It needs software, a schedule, reporting and someone to chase failures, and it is the same work at every client. Monitoring, backup checks, security tool management and first-line help desk fall in the same category.
The work you should keep close is judgment about your own business:
- Who approves spending, access to sensitive data and exceptions to policy
- Which applications and workflows the firm cannot run without
- Industry-specific vendor relationships, such as practice management or CAD software
- Someone internal who can answer "how do we do this here?"
Even fully outsourced clients need a named internal owner for IT decisions. It does not need to be a technical person. It needs to be someone with the authority to say yes or no. If you need help setting priorities and budgets above the day-to-day, that sits with our IT consulting and vCIO service.
Where outsourcing goes wrong
Outsourcing fails in predictable ways, and almost none of them are technical. The scope was vague, so every request turned into a debate about whether it was covered. Nobody inside the firm owned the relationship, so the provider's recommendations sat unanswered for months. The provider held every admin password and all the documentation, so switching felt impossible even when service slipped. Or, in co-managed setups, the internal IT person was never consulted and quietly worked around the provider instead of with it.
Each of those has a fix you can put in writing before you sign: a scope list with exclusions, a named internal owner, credentials and documentation stored where you control them, and a responsibility matrix that both teams helped write. We would rather spend an extra meeting on those at the start than argue about them in year two.
How the transition works
A handover should feel planned. Ours follows the same steps every time, though the timing depends on your size and how much documentation exists.
- Discovery. We inventory users, devices, servers, network equipment, cloud services, licenses and vendors. If an outgoing provider or employee is involved, we schedule a handover meeting with them.
- Credential handover. Admin accounts for Microsoft 365, the domain registrar, DNS, firewall, backup systems and your main business applications move into a vault you own. Shared or orphaned admin accounts get cleaned up.
- Tool deployment. Monitoring, security and backup agents go onto devices, usually in phases so nothing breaks at once.
- Urgent fixes. Common early findings include accounts without MFA, backups that have not succeeded in weeks, unsupported operating systems and former employees with active accounts. These go to the top of the list.
- Documentation. We write it up: network diagram, system inventory, vendor list, procedures for onboarding and offboarding.
- Steady state. Support moves into normal operation with regular reviews.
For co-managed clients, step 5 includes a responsibility matrix: every system and ticket type, with a named owner on each side.
Documentation and knowledge transfer
The biggest hidden risk in IT is knowledge that lives in one person's head. That is true whether the person is your employee or works for a provider. Documentation belongs to you. A provider that keeps it to itself makes you harder to leave, and that is a bad sign.
You should be able to see, at any time, your system inventory, network diagrams, vendor contacts, license list and admin credentials. If you ever leave us, that documentation goes with you. If you have an internal IT person, they get access to the same records we use.
IT outsourcing Boston checklist: contracts and exit terms
Exit terms are the part of outsourced IT services Boston firms most often skim, and the part that matters most when a relationship ends. In 2022, CISA and partner agencies published a joint advisory on cyber threats to managed service providers and their customers. Among its recommendations: customers should verify that their contracts include cybersecurity measures, spell out whether the provider or the customer owns specific responsibilities, and state how and when the provider will notify the customer of an incident. It also recommends requiring MFA on all provider accounts that access customer environments, and disabling provider accounts once they are no longer needed.
That advisory is a good checklist for any Boston IT outsourcing contract. We would add:
- A scope list showing what is included and, just as important, what is excluded
- Term length, auto-renewal language and notice period for termination
- A clear statement that you own your data, documentation and admin credentials
- An exit clause that obliges the provider to hand everything over in a usable form, and to remove its agents and accounts on a set timeline
- How the provider's own access is limited. In Microsoft 365, partners can use granular delegated admin privileges, which Microsoft describes as least-privileged, time-bound access that the customer must explicitly grant
Our article on how to choose a managed service provider has a longer list of questions to ask during evaluation.
When outsourced IT Boston firms hire is the right fit
Handing IT to a provider tends to make sense when one of these is true: nobody on staff owns IT, your internal IT person is overloaded or alone, security and compliance work keeps slipping, or you are paying for repeated emergency fixes instead of maintenance. If you are deciding between models, our comparison of managed IT, break-fix and in-house IT walks through the tradeoffs.
If you are weighing IT outsourcing, Boston firms like yours should talk to more than one provider and compare the answers. The usual first step with us is a discovery call and a short assessment. We will tell you which model fits, what we would take on, what we would leave with your team, and what the first 90 days would look like.
Frequently asked questions
What is the difference between fully outsourced IT and co-managed IT?
With fully outsourced IT, the provider runs everything: help desk, devices, servers, network, security tools, Microsoft 365, vendors and planning. With co-managed IT, you keep an internal IT person or team, and the provider takes on agreed pieces such as monitoring, patching, security tools, the help desk queue or after-hours coverage. The deciding factor is usually whether you already employ someone who knows your systems and business well.
Will co-managed IT services Boston providers offer replace our IT manager?
It shouldn't, and a good provider won't pitch it that way. Co-managed IT exists to support an internal IT person, not to replace them. Your IT manager keeps ownership of priorities, business applications and relationships with staff, while the provider adds tooling, depth on specialties like security or networking, and coverage for vacations and nights. The split is written into a responsibility matrix so nobody steps on anyone.
What IT work should a small business keep in house?
Keep decisions and business knowledge in house: who approves spending and access, which applications matter most, vendor relationships tied to your industry, and someone internal who can answer basic questions about how your firm works. Day-to-day execution such as patching, monitoring, help desk tickets, backups and security tooling is usually cheaper and more consistent when a provider handles it with tools already in place.
How long does a transition to outsourced IT support take?
It depends on the number of users, devices, sites and applications, and on how much documentation already exists. The sequence is consistent: discovery and credential handover, deploying monitoring and security agents, fixing urgent risks, then moving into steady support. We give you a written transition plan before work starts so you know what changes, when, and what staff will notice.
What contract terms should we look for when outsourcing IT?
Look for a clear list of what is in scope and what is excluded, how incidents are reported to you and how quickly, MFA on every provider account that touches your systems, and a statement that you own your data, documentation and admin credentials. Check the term length, renewal and termination notice, and an exit clause that requires the provider to hand everything over in a usable form if you leave.
Is outsourced IT secure? The provider will have admin access to everything.
That concern is reasonable, and CISA and partner agencies published joint guidance in 2022 on exactly this risk. Ask how the provider protects its own accounts, whether it uses MFA everywhere, whether its access is limited to systems it manages, how it logs its activity, and how it will notify you of an incident. In Microsoft 365, partners can use granular delegated admin privileges, which give time-bound, least-privileged access instead of standing global admin rights.