What is our primary use case?
We use Datto for several things, one of which is to automate services. One of the primary uses is to automate upgrading and patching computers to roll out new software. We do all the Windows patches using Datto. It also has a monitoring component to look at the various services running on our servers. If the monitor shows a service is no longer running, you can set up a script and have it automatically restart that service. You can be proactive on a random problem to prevent outages that keep the staff from working.
How has it helped my organization?
We support nine different nonprofits, and the billing took the manager three or four days working on spreadsheets. When I finished automating everything with Datto, we cut everything down to a couple of hours. That's a substantial cost savings on the billing side. It has also helped us track tickets, so stuff doesn't get lost, and we're spending a lot less time on PC maintenance and patching.
We originally had around three techs supporting probably about 150 or so PCs. We're currently supporting 600 PCs with the same amount of techs. The bottom line is you can do a lot of extra work without increasing your staffing.
What needs improvement?
Integration between Datto and PSA solutions could be a little more seamless. They are working towards that, but they're not quite there yet. Datto integrates already well with Outlook and other products. My most significant criticism is Datto is a complex product that takes a while to understand, but that could be said of almost any solution at the same level. It depends on where you're starting from. You have to rework all your workflows, and it's some heavy lifting if you want to get it right.
Also, there are a couple of other little quirks with the interface design. For example, you would think we could find everything on the main tab bar at the top, but you need to dig through another menu system to see all the stuff. If you're just a tech who is limited in what you can see, it's probably not such an issue. However, in smaller organizations like ours, everybody can see everything. When you're searching for one of the clients where you think they should be, you will not find anything or see any of the clients, and you'll have to go to a different area. It's okay once you get used to it, but it's not intuitive or straightforward when you first start working with it.
For how long have I used the solution?
We've been using Datto for about three years.
What do I think about the stability of the solution?
We had zero issues with Datto in terms of reliability or anything else. However, like all cloud solutions, it's not quite as snappy as something on-premise. And the output of the information is only one page at a time, so you can have 50 or 100 lines displaying, but there are 200 or 500 lines of information total. You need to go down and click to get the next page.
I can understand this because it's a cloud solution, so you don't want to dump everything unnecessary. But at the same time, when you're starting with the product, you're wondering where all the information you're expecting under this search. You have to go down a couple of pages. A couple of things like that are just inherent to the cloud to some degree. Every software package has its little quirks that you have to learn and understand.
What do I think about the scalability of the solution?
Scalability isn't an issue. We have about 600 people and nine organizations on the system, and that's a tiny installation compared to some of the ones they have. We're already using Datto extensively, but there are a lot more things we would like to do with it. It's just a matter of time and effort to integrate some of those other automation type things that we'd like to do.
How are customer service and support?
We've used Datto support before. In most cases, they've been excellent. In a couple of instances, it took a little longer to resolve stuff than I would've liked. They're pretty responsive, so no issues there. Everything got resolved eventually, and in some cases, the problem was on their end. There were a couple of minor bugs, and they had to put that into their system. It doesn't necessarily get resolved right away, but they're pretty good at responding to anything urgent.
How was the initial setup?
Deploying Datto took us a few months, and we mostly handled it ourselves, but the package we got included training and support. You can get them to help more if you want, but we were doing it from the ground up, so there was a lot of stuff that we had to figure out in terms of workflows and how we wanted to do it. I did a sample system and figured out what we liked. The company didn't like it on the first try, so we restructured it based on what we learned. In total, it was probably two or three months before we went live with it. We don't have to do any maintenance. That's all included, so all we have to do is use the product.
What about the implementation team?
A training package came with it, and we had an engineer from the vendor who was available to answer questions and help us, but we mostly did the integration ourselves.
What's my experience with pricing, setup cost, and licensing?
The license typically depends on the number of endpoints. On the RMM side, I think we're paying around $2,250 per endpoint. Then there is also a license per user and tech, so that comes out to about a hundred bucks per tech, give or take. The licensing is pretty straightforward. There aren't any additional fees.
Which other solutions did I evaluate?
We started with about 30 different products and shortlisted seven. Then we narrowed it down further to three. At that point, we eliminated one because it didn't have a mobile component at the time. Datto offered a much better price, and we got Webroot antivirus at a discount as part of the package.
What other advice do I have?
I would rate Datto RMM nine out of 10. It's a good product depending on what your resources are. You may want to get more support on the implementation. You certainly want somebody who has a good grasp of workflows and things like that. It could be someone from Datto or someone on your team. Depending on your starting point, you may want to seriously consider modeling all your flows and tickets in Visio or something before deploying because it works differently than some of the other stuff you may be used to.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)