The following table outlines how we map LCI Asset Fields to our support integrations.  Specifically, we outline mappings for: Connectwise Manage, Autotask, IT Glue, Syncro and Halo.

 

Notes that apply to the mapping tables below: 

  • When multiple fields are listed, we attempt to map the first field listed.  If that does not exist, we then attempt to map to the next field listed, and so on...   
  • The source mappings are identified by API field name unless preceded by an asterisk (*).  If the source field is preceded by an asterisk, then the source mapping is identified by the UI field
  • We are currently using the Autotask SOAP API.   Any API field names listed refer to that API (Not the REST-based API)


Important -

In order for any specific data field to come over to LCI, it must actually exist as data in one of the sources below (and not simply be a link to an RMM or similar from that source).  To persist the data in your source, there are generally mapping instructions from RMM to your PSA or IT Documentation system.  It is common for some PSAs/IT Documentation Systems to have the mappings automatically set up for certain integrations, but at times you are required to perform the actual mapping.


Connectwise Manage

 

LCI Field
Connectwise Manage API
Device Namename
Asset Statusstatus
Last User (RMM)lastLoginName
Asset Usercontact/id
Locationsite/id
Asset Typetype
Make/Vendormanufacturer
Model NumbermodelNumber
Serial NumberserialNumber
Operating SystemosType
OS InfoosInfo
Purchase DatepurchaseDate
Warranty Expiration DatewarrantyExpirationDate
RAMram
IP AddressipAddress
Comments
Tag NumbertagNumber
CPUcpuspeed
RMM Last Seen/Sync



Override Settings

We have several settings that can be implemented by our support team that will override the default mappings as they are documented above.  The following lists those override settings.


Connectwise Manage - Operating System

The default behavior is for us to load API field osType to LCI Operating System.  We have two other options here that can load Operating System.

  1. We can load Operating System from API field osInfo
  2. We can load Operating System from API fields osType + osInfo


If you would like for us to change the default behavior for Connectwise Manage -> Operating System mapping, please open a ticket with support.


Autotask


LCI Field
Autotask API (SOAP)
Device Name
  • *UDF: Name
  • RMMDeviceAuditHostname
  • DattoHostname
  • *Reference Name
Asset Status*Status
Last User (RMM)
  • *UDF: Last User
  • RMMDeviceAuditLastUser
  • *Contact
Asset UserContact
Location*Location
Asset Type
  • *Configuration Item Type
  • *Configuration Item Category
Make/Vendor
  • *Vendor
  • RMMDeviceAuditManufacturerID
  • *Product: Manufacturer
  • *Product: Vendor
  • *UDF: Manufacturer
Model Number
  • *UDF: Model Number
  • *UDF: Model
  • *UDF: Make & Model
  • RMMDeviceAuditModelID
  • Product: Vendor Product Number
  • *Reference Number
Serial Number
  • *Serial Number
  •  DattoSerialNumber
Operating System
  • *UDF: OS
  • *UDF: OSType
  • RMMDeviceAuditOperatingSystem
  • DattoOSVersionID
OS Info
Purchase DateAT does not have a field for this.   Have requested this from Datto
Warranty Expiration Date*Warranty Expiration Date
RAM
  • RMMDeviceAuditMemoryBytes
  • DattoDeviceMemoryMegabytes
IP Address
  • *UDF: IP Address
  • RMMDeviceAuditIPAddress
  • DattoInternalIP
Comments*Description
Tag Number*Reference Number
CPU
RMM Last Seen/SyncDattoLastCheckInDateTime

Override Settings

We have several settings that can be implemented by our support team that will override the default mappings as they are documented above.  The following lists those override settings.


Autotask - Operating System

The default behavior is for us to load API field UDF/OS or the RMM OS value to LCI Operating System.  We have seen some AT implementations where the RMM is feeding the Operating System value into the Autotask Description field.  As such, we have an override setting that allows for mapping the API Description field to LCI Operating System


If you would like for us to change the default behavior for Autotask -> Operating System mapping, please open a ticket with support.


Autotask - Purchase Date

Autotask does not currently have Purchase Date as an out of the box field available.  Some of our partners are using Installation date as the Purchase Date.   By default, we do not load Installation Date as the Purchase Date b/c it typically represents the date the RMM agent was installed on the asset.


If you would like for us to change the default behavior for Autotask -> Purchase Date mapping, please open a ticket with support.


Autotask - Asset Type

The default behavior is for us to load Configuration Item Type or Configuration Item Category to LCI Asset Type.  Some of our partners have their AT set up in such a way where the Product Name is configured as Asset Type.  As such, we have an override setting that allows for mapping the API Product Name to LCI Asset Type


If you would like for us to change the default behavior for Autotask -> Asset Type mapping, please open a ticket with support.


Autotask - Model Number

LCI looks at a number of fields to try and pull Model Information.  We have run into a circumstance of a partner that has a Continuum/Autotask set up where Model information is loaded into the Product Name.  We will not load this by default, but if your Autotask set up is like this, we can accomodate


If you would like for us to change the default behavior for Autotask -> Model Number mapping, please open a ticket with support.


Autotask - Parent Accounts

Assets are by default, are associated with a single Autotask Account (LCI Company).  We understand that Autotask supports Account hierarchies and we have had partners request that the parent account be available as an LCI Company so they can view all assets of the child accounts/companies in a single view.

We have an override setting that will allow you to select a parent account as an LCI Company.  Note that if you enable this option, and select the parent account as an active company in LCI... this will count against your subscription company count.


If you would like for us to change the default behavior of our Autotask integration... and support parent account hierarchies, please open a ticket with LCI support.


IT Glue


LCI FIeld
IT Glue API
Device Nameattributes/name
Asset Statusattributes/configuration-status-id
Last User (RMM)

rmm-records/attributes/last-login-user

Asset Userattributes/contact-id
Locationattributes/location-id
Asset Typeattributes/configuration-type-id
Make/Vendor
  • rmm-records/attributes/manufactuer-name
  • attributes/manufacturer
Model Number
  • rmm-records/attributes/manufactuer-model-name
  • attributes/model-name
Serial Number
  • attributes/serial-number
  • rmm-records/attributes/serial-number
Operating System
  • rmm-records/attributes/operating-system
  • attributes/operating-system-name
OS Info
Purchase Dateattributes/purchased-at
Warranty Expiration Dateattributes/warranty-expires-at
RAMrmm-records/attributes/memory-total
IP Address
  • rmm-records/attributes/ip-addresses[0]
  • attributes/primary-ip
Comments
Tag Numberattributes/asset-tag
CPUrmm-records/attributes/cpu
RMM Last Seen/Syncrmm-records/attributes/last-seen-online


**  Note, effective 2021-04-21 -- LCI is now reading the archived attribute (introduced by IT Glue in late 2020).  If an asset is archived in IT Glue, it will no longer show in LCI.


Syncro


LCI Field
Syncro API Mapping
Device Namename
Asset StatusAlways set to Active
Last User (RMM)properties/kabuto_information/last_user
Asset User
Locationproperties/address/name
Asset Type
  • properties/form_factor
  • asset_type
Make/Vendor
  • properties/Make
  • properties/kabuto_information/general/manufacturer
Model Number
  • properties/model
  • properties/kabuto_information/general/model
Serial Numberasset_serial
Operating Systemproperties/os/name
OS Info
Purchase DatePurchase Date ** Custom Field format mm-dd-yyyy
Warranty Expiration DateWarranty Expiration Date * Custom field format mm-dd-yyyy
RAMproperties/kabuto_information/ram_gb
IP Addressproperties/kabuto_information/general/ip
Comments** See override settings below
Tag Number
CPUproperties/cpu_name
RMM Last Seen/Syncproperties/kabuto_information/last_synced_at


Override Settings

We have several settings that can be implemented by our support team that will override the default mappings as they are documented above.  The following lists those override settings.


Syncro Asset Notes

By default the Notes data from Syncro is not loaded into the LCI Asset / comments field.  If you would like for us to change the default behavior and load the Notes data from Syncro in LCI Asset/comments field, please open a ticket with support.


Halo



LCI Field
Halo API Mapping
Device Name
  • name
  • inventory_number
  • id
Asset Statusstatus_id
Last User (RMM)User
Asset User**We have requested that this field be included in their base /Asset endpoint (without includedetails option).  Until this happens, we will not load this data from Halo
Locationsite_id
Asset Type

assettype_name

Make/Vendor
  • manufacturer
  • vendor
  • make

** At the time we wrote this, Halo does not have a system field for Vendor.  We will load this however if you create a custom asset field and call it either manufacturer or vendor

Model Number

model

Serial Numberserial number
Operating System
  • os version
  • os
  • operating system
OS Info
Purchase Datedate purchased
Warranty Expiration Datewarranty_end
RAMram memory
IP Addressip address
Comments
Tag Numberinventory_number
CPUprocessor
RMM Last Seen/Sync