See NinjaOne in action!
Customer-related issues are generally handled in HaloPSA and device-related issues are handled within NinjaOne. The first step is then to map all client devices, their software, and their associated organizations and locations between the two tools. Mapping and synching is done within HaloPSA with asset matching fields used to ensure there are no duplications.
The HaloPSA Integrator is used to schedule when and how frequently data flows between the solutions, usually determined by how often the data may change — organizations and locations may be imported daily while device alerts will be imported immediately using NinjaOne webhooks
When alerts are imported, they automatically generate a HaloPSA ticket, configured by alert type, device type, and organization in which the affected device resides. The ticket is assigned using the rules defined within HalosPSA. Once the ticket is resolved, its status syncs back to the NinjaOne and appears in the device activity list. Documentation on the integration can be found in the HaloPSA product site and is linked to from the NinjaOne Dojo
Both NinjaOne and HaloPSA are designed to be intuitive, highly configurable, and catalysts for operational efficiency, so it’s not surprising that hundreds of MSPs have chosen both solutions to run their managed service operations. Averaging ratings of 4.8 out of 5 stars on G2, both companies maintain strong leadership positions quarter over quarter.
“NinjaRMM is the best software that
I didn’t know I needed.”
-Dan Reynolds, Director of IT, Mid-Market
“We couldn’t run our business without Halo.”
-Mark Lonnen, Small Business
“I really enjoy working with a vendor that
feels like an extension of my team.”
– Darrell King, Mid-Market
“The application is completely customizable allowing
you to adapt it to suit your requirements.”
-Joel Becker, Small Business
Learn how NinjaOne can help you simplify IT operations.