Nexthink to ServiceNow Integration – Data Mismatch & Performance Optimization

[Ballela Siva Te]

Hi Team,

We are currently working on an integration where Nexthink sends approximately 5.6 million records to ServiceNow daily. This data first lands in a staging table, and then gets transformed into the Software Installation (cmdb_sam_sw_install) table.

To manage the volume, Nexthink sends the data in four sequential batches, with each batch containing data in multiples of 1,000 records.

However, we are facing two major challenges:

1. Performance Issue:
   The entire data load process is taking around 7–8 hours to complete.

2. Data Mismatch:
   The record count in Nexthink and ServiceNow is not matching, and we suspect some data might be getting missed during the transfer or transformation.

Additionally, please note:

• Nexthink does not support incremental data loads; it sends the entire dataset every day.
• We are using normal transform with 3 different colose fields

---

Our Questions:

• Is there a recommended way to ensure no data is missed during the transfer from Nexthink to ServiceNow?
• Are there any best practices or suggestions to optimize the data load time for such high-volume integrations?

Any guidance or shared experiences would be greatly appreciated!

Thanks,
Siva Teja

[dreinhardt]

Hi @Ballela Siva Te ,

did you already checked the supported store app by ServiceNow to integrate with Nexthing?

https://store.servicenow.com/store/app/7a22ff2e1ba46a50a85b16db234bcb51#linksAndDocuments

Best, Dennis

[Ballela Siva Te]

Hi Dennis,

Thanks for your response. But the use case is only importing the Software installation data here.

Let me talk with my Nexthink team and see if we can only import Software installation data keeping remaining data aside

Regards,

Siva Teja

[dreinhardt]

The incremental import is not a feature of source it’s part of the import logic. I would recommend to take a look into the SG-SCCM logic and try to adapt it.

One challenge for you is the increment, this can be covered the importing only record having a source updated date > the last import run date

second is the cleanup of remove software, for this please check the ScCM remove software step

What are the concerns of having a multi source cmdb for CI records including Nexthing? The integration supports IRE rules and following the CMDB data model etc.

best, Dennis