# How to integrate HaloPSA with Endpoint Central MSP

**Last Updated On**: 31 Jul 2026  
**8 minutes read**

## Overview

HaloPSA is a professional services automation (PSA) software designed primarily for managed service providers (MSPs). It is a centralized platform for managing all business operations within an MSP or IT department. Kindly note that this integration is available from build 11.4.2535.0.

## Benefits of Integrating HaloPSA with Endpoint Central MSP

- **Automated Workflows & Faster Resolution** — Requests from Endpoint Central MSP flow directly into HaloPSA as tickets, ensuring no issue is missed and resolution is quicker.
- **Accurate Client Mapping** — Device management data syncs with HaloPSA customers/sites and compliance reporting without manual effort.
- **Scalability & Client Trust** — Integration streamlines operations, reduces engineer workload, and delivers transparent endpoint health reports, helping MSPs scale efficiently while strengthening client confidence.

> **Note:** HaloPSA supports integration with Endpoint Central MSP On-Premises and Endpoint Central MSP Cloud. To complete the integration, follow the steps outlined in this [document](https://www.usehalo.com/guides/2295).

## Customer Mapping

After the integration is set up, you will need to map each client in HaloPSA to its corresponding customer in Endpoint Central MSP.

### On the HaloPSA side

1. **Create a custom field**

   - Navigate to: *Configuration → Asset Management → Asset Fields*.
   - Create a custom field named `customer_name`.

   ![Customer mapping in HaloPSA](https://www.manageengine.com/desktop-management-msp/images/halo-2.png)

   - Ensure these options are selected:
     - Show on Ticket-Asset relationship Edit Screen
     - Assign to all Asset Types

   ![Customer mapping options](https://www.manageengine.com/desktop-management-msp/images/halo-3.png)

2. **Set up site mapping rules**

   - Navigate to *Configuration → Integrations → ManageEngine Endpoint Central → Select Integration Profile → Sites* tab.
   - Add site rules to define where asset data should be posted.
   - Use the criterion: *Customer Name equals HaloPSA Customer Name*.

   **Example:**  
   The Endpoint Central MSP's customer "My Org" would be mapped to the HaloPSA client named "My Org".

   ![Site mapping rules](https://www.manageengine.com/desktop-management-msp/images/halo-4.png)

### Configure asset mapping

- Navigate to the **Assets** tab and map your Endpoint Central MSP fields to the corresponding Halo PSA fields.
- The `customer_name` field is sufficient to fetch and map computer details. Optionally map `serial number`, `computer name`, and `IP address` for easier identification and reference during import. This ensures assets from Endpoint Central MSP are correctly synced and mapped to the customer in Halo PSA.

![Configure asset mapping](https://www.manageengine.com/desktop-management-msp/images/halo-5.png)

3. **Create a new application for integration**

   - Navigate to *Configurations → Integrations → HaloPSA API → View Applications → New*.
   - Create a new application and set **Authentication Method** to *Client ID and Secret (Services)*.
   - Save the Client ID and Client Secret as they will be required during the integration setup in Endpoint Central MSP.

![Create application](https://www.manageengine.com/desktop-management-msp/images/halo-6.png)

4. **Set application permissions**

   - In the Permissions section for the application you just created, enable the following:
     - Customer Read
     - Tickets Read and Write
     - Assets Read

![Application permissions](https://www.manageengine.com/desktop-management-msp/images/halo-7.png)

### Map serial number for ticket creation

- In the Asset Mapping section of the Endpoint Central MSP integration, map the *Serial Number* field. This allows Endpoint Central MSP to create tickets and link them to the corresponding asset using its serial number.

![Serial number mapping](https://www.manageengine.com/desktop-management-msp/images/halo-8.png)

> **Note:** Ticket creation is not supported for Endpoint Central MSP Cloud.

## On the Endpoint Central MSP Side

1. Navigate to **Admin → Integrations → Halo PSA Settings**.
2. Enter the **Server URL, Client ID, and Client Secret** obtained from the HaloPSA side.
3. Click **Validate**. The integration name, which is the name given in the HaloPSA console when creating the Endpoint Central MSP integration, will be fetched only after successful validation of the Client ID and Client Secret. This action fetches the integration details created in HaloPSA for asset sync.
4. Click **Save and Next**.

![Halo PSA settings](https://www.manageengine.com/desktop-management-msp/images/halo-9.png)

### Features to be integrated

Once the integration is saved, to configure the asset sync kindly follow the steps mentioned in the document.

### Ticket Settings

Select the checkbox **"Log helpdesk requests from agent tray icon to HaloPSA"** such that help desk tickets raised from Endpoint Central MSP automatically flow into HaloPSA.

This helps unify service requests so technicians can track, respond, and resolve issues from a single console.

![Ticket settings](https://www.manageengine.com/desktop-management-msp/images/halo-10.png)

### Customer Mapping Sync

Once integrated, customer mapping from HaloPSA will now automatically sync with Endpoint Central MSP. You can also trigger a manual sync from the Endpoint Central MSP's HaloPSA Integration Summary page using the "Sync now" option.

You can update the URL, Client ID, and Client Secret in the "Modify" section if needed.

Once these steps are completed, the integration will allow for customer mapping and asset posting, as well as ticket creation (for on-premises setups).

![Customer mapping sync](https://www.manageengine.com/desktop-management-msp/images/halo-11.png)

## Troubleshooting

If you face any issue while integrating HaloPSA with Endpoint Central MSP, [refer here](https://www.manageengine.com/desktop-management-msp/kb/halo-psa-integration-errors.html).