Datto RMM problems MSPs actually run into in 2026
Datto RMM holds a 4.5/5 on G2 across 757 verified reviews. By any reasonable measure, it's the incumbent in the MSP RMM market - deep Autotask PSA integration, solid patching, 99.99% uptime, 24/7 support. The community has been largely positive for years.
Since Kaseya acquired Datto in 2022, the tone has shifted. Not a mass exodus. But the complaints on r/msp have gotten sharper, the contract terms have changed, and the feature gap between Datto and faster-moving competitors has widened. If you're on Datto RMM or actively evaluating it, here's what the MSP community actually says - grounded in 757 G2 reviews and years of Reddit threads, not vendor copy.
Remote access that makes techs wait
The single most-cited complaint in Datto RMM's G2 reviews - 42 mentions - is remote access reliability. The specific pain: connections that take one to two minutes to establish.
For a tech who has an end-user on the phone, 90 seconds of spinning is a genuinely bad experience. Several reviewers note the web console can feel sluggish, and the remote session itself sometimes lags in ways that slow down the actual troubleshooting once you're connected.
The irony here is that remote access also shows up in Datto RMM's strengths - 49 G2 mentions credit it as a positive. The same feature lands on both lists, which usually signals: works well under good conditions, falls apart when conditions change. If you're managing endpoints across regions or clients on slower connections, you'll hit this more often than the "powerful, easy-to-use" reviewers did.
"Web UI is fast and fluid - everything feels instant, whereas Datto could sometimes feel a bit sluggish depending on what you were trying to do." -- r/msp, switching to NinjaOne after 5 years on Datto
Two UIs, one product
Datto has been rolling out a redesigned interface alongside its legacy one. The problem: some tasks still require switching back to the legacy UI to complete them.
This isn't cosmetic. Techs who've built muscle memory around one interface hit unexpected dead ends when the new UI doesn't cover a workflow they need. G2 reviewers flag it consistently - the new interface "feels clunky," some parts "feel old," and the overall experience reads as inconsistent rather than modern. 25 G2 mentions specifically call out slow performance, a number that's partly tied to this transition.
A platform asking techs to context-switch between two generations of UI mid-task is adding friction that compounds across a shift. In a busy NOC, that's not a minor inconvenience.
Alert noise by default
Out of the box, Datto RMM generates a lot of alerts. That's not a product flaw - comprehensive monitoring is the point. The friction is in tuning those alerts down to a usable signal-to-noise ratio, especially across large multi-tenant environments.
G2 reviewers note that "alert tuning can be tedious in large environments," and the advanced scripting and policy configuration takes real time to learn. The depth of the automation engine is genuinely powerful - hundreds of free scripts in the ComStore, flexible policy-based controls, custom components that are reportedly easy to build and deploy. But getting there means weeks of configuration that isn't obvious from the initial setup.
The experience diverges sharply depending on whether your team has the bandwidth to tune the platform properly. Shops that do report strong results. Shops that can't spare the time end up managing alert noise as a side job.
The contract lock-in
This one is less about the product and more about the commercial terms - but it's appearing frequently enough in recent r/msp discussions that it belongs here.
Before the Kaseya acquisition, Datto offered month-to-month flexibility. That's changed for many partners. Multiple threads from 2024 and 2025 cite the shift toward 3-year minimum contracts as the reason they're actively evaluating alternatives. A longer contract isn't inherently bad - but it changes the calculus when you're weighing whether to stay.
Datto doesn't publish per-endpoint pricing. You get a custom quote via their pricing page. G2 reviewers report an average 12% discount from list, and the all-inclusive model (no separate fee for support) has been a positive. But the lock-in shift is a new variable that didn't exist two years ago. Some users report escalating licensing costs as well, though exact figures aren't public.
Development pace since Kaseya
The community concern about development pace is real, even if it's hard to quantify precisely. The r/msp thread from seven months ago captures the mood: users feel Datto has slowed down since the acquisition while competitors like NinjaOne are shipping faster.
The comparison numbers are at least indicative. NinjaOne sits at 4.7/5 on G2 with 4,263 reviews - younger platform, faster-growing adoption. Datto RMM's G2 implementation data shows an average of 2 months to get live and 10 months to ROI. That's not unusual for a mature enterprise RMM, but it's longer than the onboarding timelines newer platforms are putting in front of buyers.
If Autotask is your PSA, the integrated Kaseya/Datto ecosystem has real depth and the switching cost is genuine. If you're not on Autotask, the case for Datto over a more agile alternative gets thinner with each platform that catches up on endpoint counts and monitoring features.
What Datto actually does well
Fair is fair.
Patching is the most consistently praised capability across years of community discussion. One r/msp user who'd been on it for two years put it plainly: "Datto RMM is very good, patching is extremely good." Another noted it "has nearly all of the server and workstation monitors you could possibly need pre-configured." That's a real advantage coming out of the box.
The M365 management module is genuinely useful for MSPs running Microsoft stacks - reset passwords, manage tenants, offboard users from one place. The Autotask PSA integration feeds real-time asset data directly into tickets, which meaningfully shortens triage time.
24/7 support gets consistent praise too, despite the noise online. One r/msp poster who'd switched to Datto put it directly: "Datto RMM is great. What's best about this stack though is the people. We get great support despite what people say on this sub."
And the uptime track record is solid. 99.99% platform uptime on a cloud platform managing production endpoints is not something to wave off.
"Datto RMM has advantages over Ninja. We had an extensive custom components library and it has great visual management of deployments." -- r/msp, honest opinion thread on Datto Autotask and RMM
The problem no RMM solves
Here's something that doesn't show up in any Datto RMM review thread, because it's not actually a Datto problem: the L1 ticket backlog.
Your RMM monitors, alerts, patches, and detects ransomware. When an alert fires and triggers a ticket in your PSA, the ticket still needs a human to close it. Password reset from a client employee. Account unlock at 11pm. New hire onboarding. Departing user offboarding. None of that happens inside the RMM - it lands in the queue, and your techs handle it.
A well-tuned Datto RMM makes endpoint management faster. It doesn't touch the 200 to 400 automatable tickets per month that eat tech time regardless of which RMM you're on. Most MSP owners know this already. The question is what to do about it.
Try Rallied
Rallied is an AI technician for MSPs that connects to Datto RMM, your PSA (ConnectWise, Autotask, Halo), and your M365 tenant to resolve L1 and L2 tickets end-to-end. Password resets, account unlocks, onboarding, offboarding - Rallied handles those without a tech opening the ticket.
The RMM fires the alert. The PSA creates the ticket. Rallied closes it. MSPs using Rallied recover an average of $7,000 to $15,000 per month in tech time on automatable work. It's live the same week you sign up, with a 30-day free trial and no implementation fee. If Datto RMM's platform issues are making your techs slower, freeing them from the automatable queue at least makes the slow parts matter less.
Frequently Asked Questions
Is Datto RMM good for small MSPs?
Datto RMM can work well for small MSPs, especially if you're already on Autotask PSA - the integration between the two is genuinely one of the best in the market. That said, the shift toward 3-year minimum contracts and opaque pricing makes it harder for shops that need flexibility. If you're just starting out, tools like Atera or NinjaOne offer per-tech pricing models that scale more cleanly at lower endpoint counts.
How does Datto RMM pricing work?
Datto RMM pricing is partner-customizable and not publicly listed. You'll need to contact Datto directly for a quote. G2 reviewers report an average 12% discount from list price, and the platform operates on a monthly recurring revenue model designed for MSP billing. Since the Kaseya acquisition, many users report that contracts have shifted from month-to-month to 3-year minimums.
What's the difference between Datto RMM and NinjaOne?
Both are cloud-based RMMs for MSPs, but they diverge on a few dimensions. NinjaOne holds a 4.7/5 on G2 (vs Datto's 4.5/5) and gets higher marks for UI speed and modern UX. Datto RMM's main strength is its Autotask PSA integration and patching reliability. NinjaOne tends to win on onboarding speed and more frequent feature releases. If you're deep in the Kaseya/Datto ecosystem, switching carries real friction.
Can I use Datto RMM without Autotask PSA?
Yes - Datto RMM works as a standalone RMM and integrates with other tools via its Open REST API. That said, the Autotask integration is Datto RMM's biggest differentiator. Without it, you're running a solid but not exceptional RMM competing against platforms with more modern UIs and faster release cycles.
What should I do if my L1 ticket volume isn't being solved by my RMM?
RMMs monitor and alert - they don't resolve tickets. Password resets, account unlocks, onboarding, and offboarding requests still need someone to close them regardless of how good your RMM is. Rallied connects to Datto RMM (plus your PSA and M365) and resolves those tickets autonomously, freeing your techs for the work that actually needs them.
