Software Integration Guide for IT Managed Services Providers
QuickBooks Online is the busiest hub in an MSP stack. The PSA/RMM/BCDR ecosystem split is the second. Here's where the real gaps are — including a few integrations that are claimed on only one side of the connection.
Two hubs carry most of the integration load in an MSP stack — and at least three claimed integrations aren't reciprocated
Based on the current integration map for an 18-person MSP's tool stack.
Ask which tools in an MSP stack "integrate" and the honest answer has two parts: QuickBooks Online is the finance hub almost everything money-related plugs into, and a security/endpoint cluster around Microsoft 365, 1Password, NinjaOne, and Huntress covers everything else. Outside those two, several claimed integrations exist on paper but only from one vendor's side — worth knowing before you build a workflow assuming a sync that isn't actually there.
The two hubs
QuickBooks Online and the security/endpoint cluster are the two nodes almost everything else connects through.
QuickBooks Online connects directly to ConnectWise Manage, Gusto, Ramp, and Bill.com — four ties, the widest reach of any single tool in this stack, and the reason it's the place cosmetic-sounding line items like CSP renewals and technician expense reports are all supposed to land before the books close each month.
Microsoft 365 Business Premium, 1Password, NinjaOne, and Huntress form a tighter security mesh: Microsoft 365 ties to 1Password and Huntress, NinjaOne ties to 1Password and Huntress, and 1Password ties to both. It's not one central hub so much as three mutually-reinforcing nodes — which is normal for a security stack, since credential management, endpoint detection, and device policy are supposed to reference each other constantly.
Direct connections per hub tool
The ecosystem split still runs through Core Operations
PSA and RMM choice still gates which BCDR and documentation tools sync natively.
The PSA/RMM ecosystem split covered elsewhere in this series shows up here too: ConnectWise Manage ties to NinjaOne and IT Glue; Autotask PSA ties to Datto RMM, which in turn ties to Datto SIRIS. Pick tools across the split and IT Glue's documentation and ScreenConnect's remote-support sessions both run standalone, disconnected from your actual ticketing system.
Claims that aren't reciprocated
Not every listed integration is a two-way street. Veeam Backup & Replication lists NinjaOne and ConnectWise Manage as integrations — neither of those tools lists Veeam back. Autotask PSA lists a QuickBooks Online integration; QuickBooks Online's own connection list doesn't include Autotask. And Calendly lists Google Workspace, which is simply irrelevant here since this stack's productivity suite is Microsoft 365, not Google Workspace — a claim that's true in general but dead weight for this specific vertical.
Claimed integration vs. reciprocated
| Claimed integration | Listed by | Reciprocated? |
|---|---|---|
| Veeam ↔ NinjaOne / ConnectWise Manage | Veeam only | No |
| Autotask PSA ↔ QuickBooks Online | Autotask PSA only | No |
| Calendly ↔ Google Workspace | Calendly only | N/A — not in this stack |
| ConnectWise Manage ↔ NinjaOne | Both | Yes |
In practice, a one-sided claim usually means the integration exists as a manual export/import or a third-party connector rather than a native, bidirectional sync — not that it's fake, just that it needs more setup than the vendor's own marketing page implies.
Questions to ask before you assume two tools 'integrate'
- Does the integration move ticket or asset data, or is it just single sign-on?
- Is the connection listed on both vendors' side, or only one?
- If you switched PSA or RMM platforms tomorrow, which of your other tools would silently lose their sync?
- Who currently owns closing the gap when a sync doesn't happen — a technician, the ops manager, or nobody?
None of this changes the sticker price of the stack — the optimized MSP stack still runs $3,223-3,698/mo either way. It changes how much staff time that number actually buys, which is the real cost of a 'good default' that still needs configuration.
Good default doesn't mean zero configuration. The one-sided integration claims and the standalone documentation/remote-support tools on the Datto/Kaseya side are the two places an MSP loses the most hours to friction nobody priced in.
Run the free audit to see the full stack we'd build for your shop, with these integration gaps already factored into the recommendation — not discovered six months after you've signed.