IT Glue fields automatically map into your PSA once an integration is successfully established.
See the articles below for information on how IT Glue fields map to fields in your PSA.
- Autotask field mappings
- ConnectWise field mappings
- Kaseya BMS field mappings
- Pulseway PSA field mappings
- Tigerpaw field mappings (configuration sync is not available for Tigerpaw integrations)
In these articles, you'll also find details on the matching logic that's used to determine whether to match records between the two systems.
Creating organizations and configurations from PSA records
Most organization and configuration fields in IT Glue will sync with your PSA. The types and statuses that are enabled for syncing in IT Glue are integral to PSA sync logic. When a syncing type and status is assigned to an organization or configuration in your PSA, a new record is created in IT Glue after the next full sync.
If a matching organization or configuration is already in IT Glue, the records will sync and the one that is in IT Glue will be changed to reflect the information coming from the PSA. The PSA always wins this data syncing relationship.
Creating contacts from PSA records
If the Enable Contacts sync setting is enabled in your sync settings (Account > Integrations > [PSA] Actions > Sync Settings tab) and a new contact is created in your PSA, a new contact will be created in IT Glue, assuming there is not already a contact in IT Glue with the same name in that organization. As previously mentioned, if there is a conflict between the two systems, the PSA will always win.
If the Enable Contacts sync setting is not enabled, IT Glue will not automatically create new contacts.
For our partners who have Network Glue, you can create contacts from Active Directory data if it was enabled during set up. For instructions on how to do so, refer to our Setting up Network Glue for an IT Glue organization KB article.
If a created contact matches your PSA’s sync requirements, then a PSA badge will appear in the Contact show page and created contacts will be automatically pushed to your PSA. To ensure your created contacts match your PSA’s sync requirements, refer to our Enriching IT Glue Contacts with Active Directory user data KB article for further details.
Creating locations from PSA records
IT Glue syncs with location records (most fields) for ConnectWise, Kaseya BMS, and Tigerpaw. Whenever there is a conflict between the two systems, the PSA will always win.
Two-way syncing is available for Autotask, ConnectWise, Kaseya BMS, and Pulseway PSA. With two-way syncing, IT Glue lets you update field values that are syncing with your PSA directly in IT Glue. These changes will then immediately push to your PSA.
When you enable two-way sync, this does not automatically push to your PSA any organizations, configurations, contacts, or locations that were in IT Glue before the first sync or that are imported later on. You would need to edit and save these as confirmation that you want these new items created in your PSA. See the two-way sync article for more details.
Pushing All Syncable Assets from IT Glue to PSA when switching to or adopting a new PSA
For partners who are switching to a new PSA solution or adopting their first PSA solution, you can request a one-time push to have all your data synced to your PSA. As IT Glue is your single source of truth, this push allows you to quickly sync your well-documented assets in one go rather than having to manually edit, save, and push each one before completing a sync. This feature is available if your PSA integration is capable of two-way syncing.
Refer to our Pushing all syncable assets to PSA KB article for more details.