• Skip to primary navigation
  • Skip to main content
  • Skip to footer
  • Skip to custom navigation
HaloPSA

HaloPSA

  • Features
  • Pricing
  • Integrations
  • Resources
    • Demo On Demand
    • Roadmap
    • ITIL Alignment
    • Guides
    • HaloPSA Academy
    • Onboarding Partners
    • Distributors
  • Compare Us
    • ConnectWise
    • Datto Autotask
  • Solutions
    • I Need To…
      • Run My Business More Effectively

        Find out which customers and services are profitable and gain the confidence to act on this data.

      • Improve My Customer Experience

        Make all interactions as smooth as possible with a fully thought out end to end experience for your customers.

      • Streamline My Sales Process

        Remove unnecessary processes from your sales and account management and let them focus on their customer relationships.

      • Gain Control Of My Projects

        Visualise your workload and forecast your required budgets to ensure you can deliver on your projects.

    • We Are A…
      • Managed Service Provider
      • Telecommunications Provider
      • Cloud Solution Provider
      • Software Company
      • Consultancy Firm
    • Case Studies
      • nGeneration
      • Centrality
      • Commercial Managed IT
  • Start trial
  • Book demo

HaloPSA Guides

Documentation to assist with the setup and configuration of the HaloPSA platform

Guides > ALSO Integration

ALSO Integration


In this guide we will cover:

- What is the ALSO integration?

- Connecting to ALSO 

- Importing Customers

- Importing Subscriptions

- Importing on a Schedule



Related Guides:

  • Licences/Subscriptions Overview


What is the ALSO Integration?

Halo can integrate with ALSO to import customers and their subscriptions from ALSO into Halo. Customers and subscriptions can be synced on a scheduled basis to bring any customer/subscription changes from ALSO into Halo automatically. 


If using pro-rata billing based on your customer's subscription use this integration allows your invoices to be calculated automatically based on their subscription count in ALSO. 


Connecting to ALSO

First ensure the integration module is enabled, head to Configuration > Integrations > ALSO, enable the module using the '+' icon.

Fig 1. Enable integration module 


Once enabled click into the module to bring up the integration setup screen. 


Fig 2. Integration setup screen


To connect to ALSO enter your Marketplace URL, account username and account password in the details fields. Your 'Marketplace URL' is just the URL you use when accessing/logging into your ALSO marketplace, this is often 'https://cloud.also.com' and should follow this same format.


The 'username' and 'password' entered must belong to a ALSO user that has at least read only permissions for customer and subscription data, they also need the 'Reseller Admin' capabilities role. As this account will be used to authenticate the connection between Halo and ALSO. The ' This account will also need to have 2FA against it disabled, this can be done by ALSO support. If the account has 2FA Halo will not be able to connect to ALSO . If you cannot disable the 2FA against the account, or would not like to use an existing users account for the authentication you can set up an API only user with the appropriate permissions in your ALSO to do this. 


Once you have entered your details you can use the 'Test Configuration' button to test you have connected successfully. 


Importing Customers

Before customers can be imported from ALSO you will need to create customer mappings. Mappings can be set manually or generated automatically. These mappings will determine which ALSO customer the Halo customer is linked to. 


Automatically generated mapping can only be used if your customers in ALSO have the exact same name as your customers in Halo. To generate these mappings use the 'Generate mappings' button. 


Manual mappings are used when your customers already exist in both ALSO and Halo but have different (non exact) names. To create a manual mapping add to the customer mappings table (Fig 3), the customer data in ALSO will then be imported to the mapped Halo customer. 

Fig 3. Customer import configuration


If your customers exist in ALSO but not in Halo you do not need to configure mappings, they will be created in Halo upon import and then added to the mappings table. 


You can also have customers that are created from a ALSO import have a chosen Top Level using the 'Top Level for New Customers' field. 


Update the Customer's main Site address in Halo when an existing Customer is imported from ALSO - When this is enabled the customer in Halo will have their main site address updated to match the address against this customer in ALSO. If disabled address information will not be updated. 


Now you are ready to import your customers, to do this hit the 'Import customers' button then hit 'start. 


Importing Subscriptions 

Subscriptions can be imported for any ALSO customer which has been mapped. The subscription name, status and quantity will be imported. When importing the 'Customer Subscriptions to Import' field can be used to determine which subscriptions can be imported. When this is set use the 'Import subscriptions' button to import the subscriptions. 

Fig 4. Import subscriptions


If you would like cost and price data against subscriptions to be imported, enable 'Set price and cost on imported subscriptions' before you complete the import (available as of v2.179+). When this is enabled cost/price data will be updated each time the halo integrator runs for the integration. 


As of v2.200.1+, the end date of an imported subscription will use the contract end date if there is no subscription end date.


Importing on a Schedule

To have your customer and/or subscription data be imported from ALSO automatically on a scheduled basis enable the Halo integrator for the integration using the setting shown in Fig 5. Once this is enabled you will need to set which entities are imported on a schedule by adding them to the 'Entities to Sync' field.


Fig 5. Enable Halo integrator for integration


The Halo integrator will run the sync on a daily schedule for this integration. 


If using the Halo integrator you will be able to use the setting 'Deactivate Licences in Halo when they are deleted from ALSO (Halo Integrator only)'. 


Deactivate Licences in Halo when they are deleted from WestCoast (Halo Integrator only) - When enabled subscriptions will be made inactive in Halo when they are deleted in ALSO. When disabled subscriptions will still be made inactive in Halo when made inactive in ALSO but if they are deleted their count will be set to 0 but their status will not update.


Popular Guides

  • Asset Import - CSV/XLS/Spreadsheet Method
  • Call Management
  • Creating a New Application for API Connections
  • Creating Agents and Editing Agent Details
  • Departments and Teams
  • Halo Integrator
  • Importing Data
  • Multiple New Portals with different branding for one customer [Hosted]
  • NHServer Deprecation User Guide
  • Organisation Basics
  • Organising Teams of Agents
  • Step-by-Step Configuration Walk Through

Footer

Products

Company

  • Contact us
  • Events
  • Channel Partners
  • Technology Partners
  • Distributors
  • Referral Program

HaloPSA

  • Features
  • Integrations
  • Mobile Apps
  • Blog
  • Pricing

Key Features

  • Service Desk
  • Sales CRM
  • Billable Time Tracking
  • Reporting
  • Contracts
  • Billing
  • Stock Management
  • Projects

Compare PSA

  • ConnectWise
  • Datto Autotask
  • Accelo
  • Harmony PSA
  • Naverisk
  • Top Desk
  • Kaseya BMS
  • Atera
  • Freshservice

Social

  • Terms and Conditions
  • Privacy Policy
  • Security
  • GDPR
  • Modern Slavery Statement
We've moved!

Please visit our new website at USEHALO.COM/HALOPSA