Streamlining CMDB Ingestion with IntegrationHub ETL in ServiceNow

[Prasad Dhumal]

Managing and populating a clean, accurate Configuration Management Database (CMDB) is critical for IT operations. With ServiceNow's IntegrationHub ETL (Extract, Transform, Load), organizations can efficiently ingest and normalize external data into the CMDB — without writing complex transform maps or scripts.

IntegrationHub ETL bridges the gap between raw third-party data and CMDB class structures using a low-code, guided mapping interface.

🧠 Why Use IntegrationHub ETL?

Common Use Cases:

• Ingesting server data from inventory tools like NewCon, Flexera, or SCCM.

• Normalizing application/service data from enterprise architecture tools like LeanIX or Apptio.

• Loading assets from external spreadsheets or APIs into hardware/software tables.

• Merging multi-source data into CMDB with conditional class logic (e.g., server OS-based mapping).

🛠️ Step-by-Step: Setting Up IntegrationHub ETL

1. Create a Data Source

• Go to System Import Sets > Administration > Data Sources.

• Choose type: Import Set API, File, or REST Integration.

2. Navigate to IntegrationHub ETL

• Go to IntegrationHub ETL > Data Sources.

• Select your data source to create a Guided ETL pipeline.

3. Define Source Columns

• Run preview to let ServiceNow identify columns.

• Optionally rename source fields for clarity.

4. Configure Classifier Logic

• Based on rules like OS contains Windows, map data to correct CMDB class.

• Example:

  • Windows Server → cmdb_ci_win_server

  • Linux Server → cmdb_ci_linux_server

5. Map Fields

• Drag-and-drop source fields to target CMDB attributes.

• Add transforms (e.g., split string, extract domain, convert date).

6. Run ETL Job

• Preview the transformation.

• Activate and Run the Job.

• Monitor via the Run History tab.

---

✅ Best Practices

• 🔄 Always Normalize Data before ingestion.

• 🧩 Use Classifiers effectively to reduce hardcoding.

• 🔐 Restrict field-level access to sensitive data.

• 📦 Build reusability by templating mapping logic for similar sources.

• 🧪 Test in sub-prod environments before prod rollout.

---

⚠️ Common Pitfalls & Troubleshooting

Issue	Cause	Solution
Records not created	Source field mismatch	Ensure correct column headers in preview
Wrong CI class	Misconfigured classifier logic	Refine conditional mapping rules
Missing mandatory fields	Skipped during mapping	Use "Set Value" to add defaults
Overwriting data	Duplicate source keys	Add unique identifier logic in source setup

---

📘 Real-World Scenario: NewCon Server Import

In one of our projects, we used IntegrationHub ETL to ingest server inventory from NewCon. With custom classifier logic based on OS patterns and mapped fields like u_short_name and u_einsatzart_inhalt, we generated target CI names like: nginx

SI - u_short_name - u_einsatzart_inhalt

This completely eliminated manual classification efforts and ensured clean CMDB population.

---

🎯 Conclusion

IntegrationHub ETL is a powerful tool for streamlining data ingestion into the CMDB — no need for heavy scripting or transform maps. Its intuitive interface, flexible classifier logic, and built-in transformation functions make it ideal for ServiceNow developers and admins aiming to build clean, automated, and scalable CMDB pipelines.

---

📣 Want More?

If you're passionate about mastering IntegrationHub ETL or have questions about CMDB practices, feel free to connect or drop your thoughts in the comments! Let’s grow together 🚀

Follow for more: https://www.servicenow.com/docs/bundle/washingtondc-servicenow-platform/page/product/configuration-m...

[SAM230]

Very helpful.