Data to be pulled from Nexthink to ServiceNow, for Dashboard creation

[AbdurRahmanSnow]

Good evening
We have a requirement to create a Dashboard, but before that, we need to pull data from Nexthink to ServiceNow.
We have got a documentation link to implement this. 

Will you please check what is the estimated time to implement this?

Dashboard creation - Data to be pulled from Nexthink to ServiceNow through below Integration setup

Exporter to ServiceNow CMDB | Nexthink Documentation

Please help and guide me on this. Is it easy to implement this?
@Ankur Bawiskar @Dr Atul G- LNG @Viraj Hudlikar 

[Dr Atul G- LNG]

Hi @AbdurRahmanSnow 

Implementing an integration primarily depends on the technical team, process team, and client support. If the API is ready and there are no data-messaging issues, it can be completed quickly. Generally, I’ve seen it take around 2–3 weeks to set up the process.

Steps to follow:

• Check API availability

• Map Nexthink to ServiceNow tables

• Define field-level mapping

• Define value-level mapping

• Build the flow (one-way or two-way integration)

• Handle state/stage-level data changes

• Ask the technical team to build the solution

• Perform thorough testing

[Ankur Bawiskar]

@AbdurRahmanSnow 

it all depends on who is implementing in terms of experienced/average developer.

Also how complex the integration is

are you planning to use custom table for this?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Viraj Hudlikar]

Hello @AbdurRahmanSnow 

Implementing the Nexthink HTTP API Exporter to CMDB is a Moderately Complex integration, requiring custom Import Set/Transform Map configuration.

Estimated Time for Initial CI Class (e.g., Workstations): 5 to 8 focused business days.

The critical path is designing the Coalesce Strategy and implementing Custom Transformations (e.g., unit conversions like Bytes to GB) to maintain CMDB data integrity. Start by defining the NQL payload and mapping it to a single target table, using the Serial Number as the primary coalesce field.

I strongly recommend a phased rollout, prioritizing data quality checks over rapid deployment.

If my response has helped you, hit the helpful button, and if your concern is solved, do mark my response as correct.

Thanks & Regards
Viraj Hudlikar.