Breadcrumbs

FAQ - What are the key differences between CI Sync and the Lansweeper ServiceGraph Connector

Distribution and Disclaimer

This content is not to be redistributed by the recipient without written permission from Syncfish.

The information is accurate at the time it was produced (Q1 2025). While every effort has been made to ensure the accuracy of the information, it is possible for inaccuracies to be present. Readers are encouraged to engage with either Syncfish or Lansweeper to discuss individual topics.

High Level Product Comparision

CI Synchronizer

  • CI Sync is a comprehensive and sophisticated integration solution designed for rigorous alignment of Lansweeper source data and ServiceNow CMDB (and Asset) destination data.

  • CI Sync can cater for any business rule, business requirement, or data anad workflow requirements in the destination ServiceNow instance.

  • CI Sync’s transactional record handling, data mapping and transformation logic and data correlation logic deliver perfect data to meet every customer’s specific ServiceNow requiremetns.

  • CI Sync delivers a large number of Lansweeper assets, child records and CI-to-CI relationships to your ServiceNow CMDB (all OOTB). CI Sync can be extended to include any record type or attribute available from the Lansweeper data.

  • CI Sync does not require ServiceNow ITOM licences.

  • CI Sync works with Lansweeper On-Prem or Lansweeper Cloud.

Lansweeper Service Graph Connector

  • Lansweeper ServiceGraph connector is a simple data transfer solution to move source data largely “as is” between Lansweeper and ServiceNow.

  • The Lansweeper Service Graph Connector provides a limited number of Lansweeper asset types, child records and very few CI-to-CI relationships OOTB.

  • Any tuning or extension of Lansweeper Service Graph data mapping or data transformation is a customer responsibility.

  • Lansweeper Service Graph requires ServiceNow ITOM licences.

  • Lansweeper Service Graph only works with Lansweeper Cloud (it does not support Lansweeper On-Prem).

Detailed Feature Comparison

Feature

Syncfish CI Synchronizer

Lansweeper Service Graph Connector

Supported Lansweeper Discovery Repositories



  • Works with Lansweeper On-Premise (no data in the cloud)

Yes

No

  • Works with Lansweeper Cloud

Yes

Yes

Licence Requirements



  • ServiceNow ITOM Licence

Does not require ServiceNow ITOM Licences

Does require ServiceNow ITOM Licences

  • Works with Lansweeper Professional Edition

Yes

Yes

  • Works with Lansweeper Enterprise Edition

Yes

Yes

Core Archiecture and Data Hosting



  • Dedicated vs Shared Architecture

CI Sync is provided via a dedicated instance per customer

Service Graph integrates with Lansweeper cloud which is a shared hosting model.

  • Physical Location (for Data Soverignty)

Syncfish/customers agree. the hosting location of the customer’s dedicated instance of CI Sync (which can be in almost any Azure Region globally)

LS Cloud storage is held in Ireland or USA only

  • Data Extraction Technology

For Lansweeper On-Prem: SQL

For Lansweeper Cloud: Lansweeper Cloud API.

For both: Robust transactional extraction and synchronization technology with pre-caching engine to support all of the advanced functionality offered by CI Sync.

For Lansweeper On-Prem: SQL

For Lansweeper Cloud: ServiceNow flows calling into Lansweeper Cloud API.

  • Transactional error handling with retry and rollback logic

Yes

To the extent provided by Service Graph.

  • Comprehensive record, attribute, payload logging

Yes

To the extent provided by Service Graph.

Initial Data Sync/Bulk Load and Ongoing Synchronization Capabilities



  • Initial Data Sync method

For Lansweeper On-Prem: Transactional synchronization engine

For Lansweeper Cloud: Bulk Export, File Drop, then transactional synchronization engine

Bulk Export, File Drop, File Load directly into ServiceNow

  • Full re-synchronization method

Simple re-synchronization trigged via a UI option

Repeat of Initital Data Sync

  • Asset/CI delete detection during full re-synchronization

Automatically caters for deleted parent/main CIs (retirement) or deleted child records (deletion).

No OOTB support (does not cater for deleted parent/main CIs or deleted child records - customer responsibility to manage).

  • Delta record synchronization

Natively supported via record level checksum to determine if a record has changed (or not).

Scheduled job based on customer defined “last record update date”.

  • Out of the box recordset and record level filtering options

Yes (UI selectable record sets, OOTB support to filter record subsets on CIDRs, additional filters to meet any critiera can be easily implemented)

Customer responsibility (ServiceNow Admin/Developer involvement)

  • Customer can schedule synchronization jobs

Yes

Yes

  • Customer can execute run-now synchronization jobs

Yes

Yes

  • ServiceNow performance overhead

Low (all transformation and correlation handling is performed within CI Sync and therefore is offloaded from the customer’s ServiceNow instance)

Higher than CI Sync (all transformation and correlation handling is performed within the customer’s ServiceNow instance).

Record and Attribute Mapping Flexibility and Extensibility



  • Quantity of OOTB mappings for Asset Types and Child/Related Records

> 40

~20

  • Method for adding additional record level mappings (additional Asset Types or Child/Related Records)

Syncfish responsibility (no customer overhead)

Customer responsibility (ServiceNow Admin/Developer involvement)

  • Quantity of OOTB mappings for Attributes (fields)

~200

~40

  • Method for adding additional field level mappings

Syncfish responsibility (no customer overhead)

Customer responsibility (ServiceNow Admin/Developer involvement)

  • Quantity of CI-to-CI Relationships (CI dependencies) automatically generated

> 100

~5

  • Method for adding additional CI-to-CI Relationships (CI dependencies)

Syncfish responsibility (no customer overhead)

Customer responsibility (ServiceNow Admin/Developer involvement)

Data Transformation Capabilities



  • Data transformation engine

Sophisticated rules engine

ServiceNow transform maps (ServiceNow Admin overhead)

  • Split-Transform Support
    (dynamically different behaviours between CI Insert & CI Update operations)

Natively and comprehensively supported OOTB.

Nothing provided/supported OOTB

  • CI Status value mapping/transformation

OOTB default value maps with flexible overrides

Nothing provided/supported OOTB

  • CI Category and Sub-Category value management

OOTB default value maps with flexible overrides

Nothing provided/supported OOTB

  • Asset/CI Location determination

Comprehensive and flexible OOTB defaults that can be override with sophisticated rules based logic.

Nothing provided/supported OOTB

  • CI Assigned_To support

Intelligent OOTB defaults to populate Assigned_To and link with the User table in ServiceNow. OOTB defaults can be overridden with sophiticated rules/logic to read any attributes/data in Lansweeper and transform the data as it is persisted into ServiceNow.

Static support for Last Logged On and Assigned_To using Name attribute matching only.

Changes to location data handling is the Customer responsibility (ServiceNow Admin/Developer involvement).

  • CI Most_Frequent_User support

Supported

Not Supported

Asset Source Systems Supported



List of Source Systems supported

  • Lansweeper On-Prem (using data sourced from Lansweeper scanner)

  • Lansweeper Cloud (using data sourced from Lansweeper scanner)

  • InTune

  • SCCM

  • JAMF

  • VMware

  • Azure (Unlimited record types and attributes supported)

  • AWS (Unlimited record types and attributes supported)

  • GCP (Unlimited record types and attributes supported)

  • Microsoft 365

  • Microsoft Defender for Endpoint

  • Microsoft Defender for Cloud Apps

  • WorkspaceOne (AirWatch)

  • Nutanix

  • Vmware vSphere

  • Vmware SD-WAN

  • Palo Alto SD-WAN

  • BeyondEdge SD-LAN

  • SolarWinds Orion

  • LeanIX

Coming Soon in 2026

  • SentinelOne

  • Maraki

  • Lansweeper Cloud (using data sourced from Lansweeper scanner)

  • InTune

  • SCCM

  • JAMF

  • VMware

  • Azure (Approximately 8x common attributes supported)

  • AWS (Approximately 8x common attributes supported)

  • GCP (Approximately 8x common attributes supported)

Advanced Record Types Support



  • Operational Technology (OT) Assets and Relationships

Lansweeper On-Prem: OOTB Support

Lansweeper Cloud: OOTB Support

Lansweeper On-Prem: Not Supported

Lansweeper Cloud: Not Currently Supported (no current roadmap to support)

  • Depth of support for virtualisation record types

Comprehensive (management and hypervisor objects, hosts and guest)

Limited/basic (Host/Guest)

  • SQL Server Instances and Databases (including relationships)

Recognised

Not recognised

  • Installed Software synchronization

Yes

Yes

  • Windows Patch and Hotfixes synchronization

Yes

No

  • Registry Keys synchronization

Yes

No

  • Mapped Network Drives synchronization

Yes

No

  • Windows Services synchronization (targeted list defined by customer)

Yes

No

  • Digital Certificate synchronization (targeted list defined by customer)

Yes

No

  • Child record deletion management (e.g. Installed Software)

Automatically caters for deleted child records (such as Installed Software, Storage, Memory Modules, Network Adapters and so on).

Not supported (obselete records remain in place).

CI-to-CI Relationships (CI Dependendency) Support



  • Virtualisation CI-to-CI Relationships (CI dependencies)

Comprehensive

Limited

  • SQL CI-to-CI Relationships (CI dependencies)

Comprehensive

None

  • Network equipement CI-to-CI Relationships (CI dependencies)

Comprehensive

Limited

  • Digital Certificate CI-to-CI Relationships (CI dependencies)

Supported

Not Supported

Management of ServiceNow Master Data and Reference Data



  • ServiceNow Master Data Management (e.g. manufacturers, models, etc)

Dynamically inserts new Master Data

Dynamically prunes unused Master Data records (when no longer referenced from CI records)

Above rules can be suppressed for the main/parent asset or child records (CPUs, Disks, NICs, etc)

No OOTB update/management of ServiceNow Master Data tables.

  • ServiceNow Reference Data Management (e.g. choice lists)

Dynamically inserts new Choice values (can be suppressed)

No OOTB update/management of ServiceNow Reference Data.

Control Information

Created

Reviewed

Data Classification

PUBLIC
Classified in accordance with the Syncfish Data Classification Framework