Enabling Kaseya BMS two-way sync

For partners subscribed to Select or Enterprise Plans

If you are integrated with Kaseya BMS, you will want to take advantage of the BMS two-way sync. Two-way sync allows you to update changed asset types, such as Organizations, Configurations, Contacts, and Locations that are syncing with Kaseya, directly in IT Glue. With one-way sync, selected synced fields were read-only because data coming from Kaseya was prioritized over the data in IT Glue.

Prerequisites

  • You must have Manager or Administrator access to IT Glue
  • An integration with Kaseya BMS

Instructions

  1. Log in to your IT Glue account and navigate to Account > Integrations. Click on Actions > Sync Settings.


    Integrations___IT_Glue-2.png

  2. In the Sync Settings tab, select the Account and Asset Types you wish to sync.


    Kaseya_BMS___IT_Glue-2.png

  3. In the Two-Way Sync Settings tab, review the Enable two-way sync setting. Uncheck this function if desired. For partners with Network Glue and Active Directory enabled, configure your contact attributes so that new contacts created from Active Directory are automatically pushed to your PSA (learn more here).


    Kaseya_BMS___IT_Glue-3-2.png

  4. In the Contacts section, select the contact attributes from your PSA that will be applied to new contacts you create. If the email type is not selected, contacts will not pushed.


    BMS___IT_Glue.png

  5. Click Save. The sync will be automatically queued.

After you turn on two-way sync, updates made to synced asset types and statuses selected on the Sync Settings page are pushed to Kaseya BMS.

Note 1a: If you had existing Organizations, Configurations, Contacts, or Locations populated in Kaseya BMS that also exist in IT Glue, you must edit and save each asset individually to trigger the two-way sync. Enabling the two-way sync alone will not automatically push these assets.

Note 1b: If you are switching to Kaseya BMS or adopting it for the first time, you can complete a one-time push to have all your IT Glue data synced at once. As IT Glue is your single source of truth, this push allows you to quickly sync all your well-documented assets in one go rather than having to manually edit, save, and push each one before completing a sync. Refer to our Pushing all syncable assets to PSA KB article for more details.

Common Questions

How will data be pushed to Kaseya?

If you currently have Kaseya BMS and it is populated:

Turning on two-way sync is what allows any new IT Glue data in mapped fields to be pushed to Kaseya BMS. However, as a precautionary measure, two-way sync will not automatically push existing data in IT Glue in to Kaseya BMS until it has been individually edited and saved. Items not yet pushed will display the following message: "Record not yet pushed to Kaseya BMS. To trigger a push, try updating the record." Edit and save these items one-by-one, which will then queue them to sync per our standard sync behavior. Make sure that each organization or configuration's type and status are ones that are set to sync.

Remember, assets must meet the sync settings specified on the Account > Integrations > Action > Configuration screen (i.e. these assets must have a synced type and/or status). When an asset is queued for sync, the message "Queued for push to Kaseya BMS" will appear.

If you are switching to Kaseya BMS or adopting it for the first time:

You can complete a one-time push to have all your IT Glue data synced to Kaseya BMS. As IT Glue is your single source of truth, this push allows you to quickly sync all your well-documented assets in one go rather than having to manually edit, save, and push each one before completing a sync. For details on how to complete a one-time push all of your syncable IT Glue assets into Kaseya BMS, refer to our Pushing all syncable assets to PSA KB article for more details.

How do I make imported data push to Kaseya?

If you currently have Kaseya BMS and it is populated:

Two-way sync is not intended for data imported from external sources or that's added to your account via the IT Glue API. Such data will need to be edited and saved one by one to work with two-way synchronization and push to Kaseya BMS. The primary reason for pushing such data automatically is to ensure that the integrity of the data stored in Kaseya BMS is not affected by bulk changes made in IT Glue. That could easily result in hundreds or thousands of records being duplicated or incorrectly updated.

If you are switching to Kaseya BMS or adopting it for the first time:

Since your new PSA is not populated, you can complete a one-time push to have all your IT Glue data synced at once. Please refer to our Pushing all syncable assets to PSA KB article for more details on how to complete this action.

What is the sync frequency and duration?

After enabling two-way sync, any updates to a mapped field in IT Glue will be immediately pushed to Kaseya.

Updates from Kaseya sync regularly, and the time taken to complete depends how many items have changed since the last sync. You can use a manual sync anytime (from Account > Integrations) to prioritize the sync to start sooner.

Was this article helpful?
1 out of 2 found this helpful
Have more questions? Contact us