---
title: "SysAid Asset Management via Lansweeper"
slug: "lansweeper-integration-with-sysaid"
updated: 2026-04-06T10:09:10Z
published: 2026-04-06T10:09:10Z
canonical: "documentation.sysaid.com/lansweeper-integration-with-sysaid"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.sysaid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SysAid Asset Management via Lansweeper

SysAid and Lansweeper allow you to effortlessly scan and discover all assets across your network, giving you a broader view and up-to-date hardware and software data at your fingertips.

[Lansweeper](https://www.lansweeper.com/) is an IT Network Discovery tool that automatically scans and inventories devices, software, and user data across an organization. It helps businesses track assets, manage compliance, and gain insights into their IT infrastructure.

Managing IT services without accurate asset data is like navigating without a map. While IT Service Management (ITSM) ensures smooth service delivery, IT Asset Management (ITAM) provides visibility into the assets that power those services. Without effective ITAM, IT teams face outdated asset records, compliance risks, and inefficiencies that slow down service delivery.

This integration eliminates these challenges by bringing real-time asset intelligence into your ITSM workflows, ensuring IT teams have the **right data at the right time** to make better decisions, improve security, and enhance efficiency.

> [!NOTE]
> Available for:
> 
> - SysAid Spaces
> - SysAid Classic
> - Lansweeper [Pro plan](https://www.lansweeper.com/product/go-pro/) or or an on-premise with Cloud Pro Sync turned on

## How it works

Once the Lansweeper and SysAid are connected, all the device data in Lansweeper will be imported into SysAid.

During the import process, SysAid’s system matches assets according to **manufacturer** and **serial number**:

- **Assets already in SysAid’s database** will be enriched with additional information from Lansweeper, but will still retain “Agent” or “WMI” as their source to avoid asset duplication.
- **New assets** will be imported and created only if both vendor and serial values exist. They will show “Lansweeper” as their source, and display all the information imported from Lansweeper.

You also have the option to create a filter so that only assets with specific parameters are imported and synced. SysAid will run a daily scheduled sync to import new and updated data from Lansweeper.

If your account **exceeds its asset quota**, new assets will be created in a disabled state, and existing disabled assets will not be updated.

> [!NOTE]
> Lansweeper on-prem:
> 
> For your integration to work, you'll have to link your Lansweeper to the cloud. To learn how to do that, visit [Lansweeper Community](https://community.lansweeper.com/t5/sites/link-lansweeper-on-prem-with-lansweeper-sites/ta-p/64514).

## Connecting Lansweeper and SysAid

The connection process consists of these main steps:

1. Adding the Lansweeper addon
2. Creating a Lansweeper account. If you already have an account, you can go directly to [step #4](https://documentation.sysaid.com/docs/lansweeper-integration-with-sysaid#step-4-connecting-lansweeper-with-sysaid).
3. Creating scanning credentials
4. Connecting Lansweeper with SysAid
5. Turning on the integration

We’ll walk you through each and every step.

### Step #1: Adding the Lansweeper addon

To add the Lansweeper addon to your SysAid account:

1. In SysAid, go to **Connect**and click **Explore** in the Marketplace banner.
2. Search for **Lansweeper**and click on the card.
3. Click **Setup and manage**. You will be redirected to the **My add-ons** page, where you’ll see **Lansweeper**.
4. Click the **gear icon**.

Next, you’ll need to create an account with **Lansweeper**.

### Step #2: Creating a Lansweeper account

To set up a Lansweeper account:

1. Go to [Lansweeper’s website](https://www.lansweeper.com/), click **Start Free,**and begin the free trial process. If you already have an account, you can go directly to [step #4](https://documentation.sysaid.com/docs/lansweeper-integration-with-sysaid#step-4-connecting-lansweeper-with-sysaid).
2. Fill in your details for the account.
3. Click **Download Scanner** and start the setup process.
4. Select the **Easy install** installation type.

> [!TIP]
> Tip:
> 
> For additional information about the installation process, see Lansweeper’s [Create a Lansweeper Site and Installation video](https://www.youtube.com/watch?v=EGmm_aKkVHc).
5. Lansweeper will run a **Prerequisite check** to make sure your installation is ready to link to the Cloud. For more details, see [Lansweeper Community](https://community.lansweeper.com/t5/sites/cloud-requirement-sync-server-internet-access/ta-p/64525).
6. Click **Finish**.
7. Log in to your account with the details you provided for the trial account.

Once the setup process is finished and you have access to your Lansweeper account, you can click on **Scanning Queue** in the bottom left corner. You will see the scans Lansweeper will be running to detect devices in the selected network.

![](https://cdn.document360.io/52d3cb6c-cc81-43c2-b6f7-cbabcb449271/Images/Documentation/sysaid-asset-management-via-lansweeper-image-wpamia4o.png)

Lansweeper’s discovery technology utilizes a proprietary blend of active, passive, and agent-based discovery technologies for maximum coverage and efficiency.

> [!NOTE]
> Please note:
> 
> The Lansweeper **free trial ends after 14 days**. If you haven’t purchased a Lansweeper license, the integration will stop working once the trial is over. You can reach out to your SysAid representative or our [Sales team](https://www.sysaid.com/support/upgrade-account) to purchase a license as part of your SysAid plan. After purchasing a license, your Lansweeper account will be automatically upated. You can check your Lansweeper license status by navigating to **Settings** > **License status**. ![](https://cdn.document360.io/52d3cb6c-cc81-43c2-b6f7-cbabcb449271/Images/Documentation/image-XA4PG5Y8.png)

### Step #3: Creating scanning credentials

We recommend creating scanning credentials to get as many details as possible to enrich your asset management to the fullest.

To create the scanning credential:

1. In your Lansweeper account, go to **Scanning** > **Credential Vault**.
2. Click **Default Credentials**.
3. Click **Add default credentials +**.
4. Add credentials for Windows, SSH, and SNMP.

You can add credentials for additional systems as needed.

> [!NOTE]
> Please note:
> 
> Credentials are stored securely in an on-premise vault, ensuring that they are never stored in the cloud.
> 
> To learn more about Lansweeper Security, see [Lansweeper’s website](https://www.lansweeper.com/about/trust/security/).

Once the scan is complete, you can go ahead and connect Lansweeper with SysAid.

> [!TIP]
> Tip:
> 
> If you have different sets of credentials for different systems, set them up as **My credentials**:
> 
> 1. Go to **Scanning** > **Targets** and click the scan server you installed.
> 2. Click**Add Scanning target +** and select the scan type.
> 3. Map the credentials you want the scan to use if they are not part of the default credentials you entered
> 
> To learn more, see Lansweeper’s video on [Credential vs. Credential-less Scans Compared](https://www.youtube.com/watch?v=PRQWAFZpbHc).

### Step #4: Connecting Lansweeper with SysAid

To connect your Lansweeper account with your SysAid account:

1. In your Lansweeper account, go to **Settings**in the bottom left corner.
2. Go to **Developer Tools** > **API clients**.
3. Click **Add new API client**.
4. Select **Personal Access Token (PAT)**.
5. In the **API client nam**e field, enter “SysAid”.
6. From the**Integration** drop-down menu, select **SysAid**.
7. Click **Continue**.
8. Under **Which sites do you want to give access to SysAid?**Select your SysAid domain.
9. Click **Allow** and copy the token.
10. In your SysAid account, go to your **My apps** page, where you’ll see **Lansweeper**.
11. Click the **gear icon**.
12. Paste the copied Lansweeper token in the **API Token** field.

### Step #5: Turning on the integration

1. Fill in the **Filter** field if you want to only import assets with specific parameters

**Example filters**

  - Filter that pulls two assets with specified keys: *{conjunction: OR, conditions: [{operator: EQUAL, path: "key", value: "ASSET1_KEY"}, { operator: EQUAL, path: "key", value: "ASSET2_KEY"}]}*
  - Filter that pulls assets that have a non-empty manufacturer and serial: *{conjunction: AND, conditions: [{operator: EXISTS, path: "assetCustom.manufacturer", value: "true"}, {operator: EXISTS, path: "assetCustom.serialNumber", value: "true"}]}*
  - Filter that pulls assets that have been updated after 1st of Jan: *{conjunction: AND, conditions: [{ operator: GREATER_THAN, path: "assetBasicInfo.lastUpdated", value: "2025-01-01T13:16:02.013Z" }]}*
  - *Filter that only loads devices with Windows or Linux OS installed: {conjunction: OR, conditions: [{operator: EQUAL, path: "assetBasicInfo.type", value: "Windows"}, { operator: EQUAL, path: "assetBasicInfo.type", value: "Linux"}]}*
  - Filter that excludes importing devices with Windows or Linux OS installed: *{conjunction: AND, conditions: [{operator: NOT_EQUAL, path: "assetBasicInfo.type", value: "Windows"}, { operator: NOT_EQUAL, path: "assetBasicInfo.type", value: "Linux"}]}*
2. Click **Test Connection** to verify that you are connected to Lansweeper.

> [!NOTE]
> Please note:
> 
> Incorrect syntax in the **Filter** field may cause the test to fail. If you’ve added a filter, try removing it and running the connection test once again.
3. Turn on the integration toggle - the Lansweeper asset data will be **imported to SysAid within 24 hours**.

> [!TIP]
> Run a test import:
> 
> To quickly preview how imported device data appears in SysAid, click**Import Sample** to instantly load up to 40 devices for review.
4. Select the **Scheduled run** checkbox.

Now, the scheduled sync will happen **once every 24** hours to ensure the asset data is up to date. You can check the last time an import ran by checking the “Last Updated” field in the Lansweeper addon page in SysAid.

<editor360-custom-block data-preprocessing="true" data-sanitizationtags="a"><h2 data-block-id="08c4c9c8-5331-497a-9577-46fec394f448"><a id="_rv85ssaq5hkn" display="false"></a>Viewing Lansweeper asset data in SysAid</h2></editor360-custom-block>

Once your Lansweeper integration is up and running, your Lansweeper information is integrated with SysAid asset management. Here are a few places where you can view your Lansweeper data.

#### Asset list

The imported Lansweeper devices are displayed in the asset list.

You can view all the devices that came from Lansweeper by filtering the asset list by “Source is Lansweeper”.

![](https://cdn.document360.io/52d3cb6c-cc81-43c2-b6f7-cbabcb449271/Images/Documentation/sysaid-asset-management-via-lansweeper-image-9dm0cj6a.png)

> [!NOTE]
> Please note:
> 
> This filtering will only show newly added devices. Models and serial numbers that already exist in SysAid’s database will be enriched with additional information from Lansweeper, but still have “Agent” or “WMI” as their source - to avoid asset duplication.

When looking at a specific asset, you’ll see the **Additional data**field****populated with even more data from Lansweeper.

### Device mapping

Various Lansweeper device types will be remapped when imported into SysAid. You can see the full device mapping below:

| Lansweeper device type | SysAid asset category |
| --- | --- |
| Android | Smartphone |
| Apc | Other SNMP Device |
| Apple Mac | Workstation |
| Aws Ec2 Instance | Server |
| Azure Virtual Machine | Server |
| Blackberry | Smartphone |
| Blade Server | Server |
| Cell Phone | Smartphone |
| Chrome Os | Workstation |
| Citrix Guest | Server |
| Citrix Pool | Server |
| Citrix XenServer | Server |
| Computer | Workstation |
| Desktop | Workstation |
| DNS Server | Server |
| Esxi Server | Server |
| Firewall | Firewall |
| Hyper-V Guest | Server |
| Ipad | Tablet |
| Iphone | Smartphone |
| KVM Switch | Switch |
| Laptop | Laptop |
| Linux | Workstation |
| Mail Server | Server |
| Mobile | Smartphone |
| Nas | Other SNMP Device |
| Network Device | Other SNMP Device |
| Power Distribution Unit | Other SNMP Device |
| Power Injector | Other SNMP Device |
| Printer | Printer |
| Proxy Server | Other SNMP Device |
| Router | Router |
| Security Appliance | Firewall |
| Switch | Switch |
| Tablet | Tablet |
| Unix | Server |
| Virtual Machine | Server |
| Vmware Guest | Server |
| Vmware Vcenter Server | Server |
| Webserver | Server |
| Windows | Workstation |
| Windows Ce | Tablet |
| Windows Ce 2 | Tablet |
| Windows Ce 3 | Tablet |
| Windows Ce 4 | Tablet |
| Windows Ce 5 | Tablet |
| Windows Phone | Smartphone |
| Wireless Access Point | Other SNMP Device |
| Wireless Controller | Other SNMP Device |
| Xdsl Router | Router |

### Field mapping

The following table shows how device data from Lansweeper maps to corresponding fields in SysAid. This can help you understand how information is populated and troubleshoot synchronization discrepancies.

> [!NOTE]
> Please note:
> 
> - Some Lansweeper fields map to **multiple SysAid fields**.
> - When multiple mappings exist, SysAid determines which value to use based on availability.
> - Additional or unmapped data may appear under `additionalData`.
> - Field availability may vary depending on the device type and data returned by Lansweeper.

| Lansweeper field | SysAid Field |
| --- | --- |
| assetBasicInfo.name | computerName |
| assetBasicInfo.type | computerType / additionalData.type |
| assetCustom.manufacturer | systemManufacturer |
| bioses.manufacturer | systemManufacturer / bios.smbiosBIOSVendor |
| mobileDeviceManagement.manufacturer | systemManufacturer |
| assetCustom.serialNumber | serial |
| bioses.serialNumber | serial |
| baseboards.serialNumber | serial / bios.smbiosMainBoardSerial |
| mobileDeviceManagement.serialNumber | serial |
| assetBasicInfo.userName | userName / osRegisteredUser |
| assetBasicInfo.mac | macAddress |
| mobileDeviceManagement.wiFiMacAddress | macAddress |
| assetBasicInfo.ipAddress | ipAddress |
| assetCustom.warrantyDate | warrantyExpirationDate |
| assetCustom.model | model |
| assetBasicInfo.model | model |
| mobileDeviceManagement.model | model |
| assetCustom.domain | domain |
| assetBasicInfo.domain | domain |
| operatingSystem.name | osName |
| operatingSystem.version | osVersion |
| operatingSystem.buildNumber | osBuild |
| operatingSystem.servicePack | osServicePack |
| operatingSystem.installDate | osInstallDate |
| operatingSystem.lastBootUpTime | lastBootTime |
| processors.name | cpuName |
| processors.numberOfCores | cpuCores |
| processors.numberOfLogicalProcessors | cpuLogicalProcessors |
| processors.maxClockSpeed | cpuSpeed |
| memoryModules.capacity | memorySize |
| memoryModules.speed | memorySpeed |
| baseboards.product | motherboardModel |
| baseboards.version | motherboardVersion |
| baseboards.manufacturer | systemManufacturer |
| baseboards.installDate | motherboardInstallDate |
| bioses.name | biosName |
| bioses.version | biosVersion |
| bioses.releaseDate | biosReleaseDate |
| bioses.smbiosBIOSVersion | bios.smbiosBIOSVersion |
| bioses.smbiosMajorVersion | bios.smbiosMajorVersion |
| bioses.smbiosMinorVersion | bios.smbiosMinorVersion |
| bioses.smbiosEmbeddedControllerMajorVersion | bios.smbiosEmbeddedControllerMajorVersion |
| bioses.smbiosEmbeddedControllerMinorVersion | bios.smbiosEmbeddedControllerMinorVersion |
| logicalDisks.deviceID | diskName |
| logicalDisks.fileSystem | fileSystem |
| logicalDisks.freeSpace | freeDiskSpace |
| logicalDisks.size | diskSize |
| hardDisks.model | diskModel |
| hardDisks.interfaceType | diskInterface |
| hardDisks.size | diskSize |
| hardDisks.serialNumber | diskSerial |
| displayControllerConfigurations.name | displayName |
| displayControllerConfigurations.horizontalResolution | resolutionX |
| displayControllerConfigurations.verticalResolution | resolutionY |
| graphicsCards.name | gpuName |
| graphicsCards.videoProcessor | gpuProcessor |
| graphicsCards.adapterRAM | gpuMemory |
| networkAdapters.name | networkAdapterName |
| networkAdapters.macAddress | macAddress |
| networkAdapters.speed | networkSpeed |
| networkAdapters.ipAddress | ipAddress |
| networkAdapters.dhcpEnabled | dhcpEnabled |
| networkAdapters.dhcpServer | dhcpServer |
| networkAdapters.defaultIPGateway | defaultGateway |
| printers.name | printerName |
| printers.driverName | printerDriver |
| printers.portName | printerPort |
| warranties.details.endDate | warrantyDetails[].endDate |
| warranties.details.serviceType | warrantyDetails[].serviceType |
| softwares.name | software[].softwareProductName |
| softwares.publisher | software[].publisher |
| softwares.version | software[].softwareProductVersion |
