CMDB ITSM: Using and integrating free solutions effectively

A CMDB connects the documentation of your IT landscape with IT service management. Free solutions can help you record devices in a structured way, process support requests, and exchange information between systems. This article explains which features you need, what to look out for during selection, and what practical integration looks like in everyday operations.

Table of contents

1. CMDB and ITSM: How do they fit together?
2. The CMDB documents your IT landscape
3. Free CMDB & ITSM solutions: What approaches are available?
4. Which features do you really need?
5. Tool integration: How CMDB and ITSM work together
6. Practical example: An application is unavailable
7. Templates simplify getting started
8. Free does not mean zero effort
9. Conclusion: Value is created through reliable data and clear workflows

CMDB and ITSM: How do they fit together?

Practical example: An employee reports that an application is not working. Your support team logs the incident and begins troubleshooting. But which server is the application running on? Which database does it require? Who is responsible for operations?

To answer these questions, support needs reliable documentation. This is precisely where CMDB and ITSM complement each other.

The CMDB provides the information about the affected IT environment. It documents the application, the associated servers and databases, and their relationships. This allows support to understand which components are involved and which other services might be affected by an incident.

ITSM organizes the handling of the incident. It defines how the report is recorded, prioritized, and assigned to the responsible team. A ticketing system supports this workflow and tracks communication, investigation steps, and the resolution.

When the CMDB and ticketing system are connected, the ticket can be assigned directly to the affected application. Support can access the stored information without having to search through multiple lists or ask colleagues about responsibilities first.

Additionally, monitoring provides up-to-date information on the availability and health of the systems involved. This allows support, for example, to check whether the application server is reachable or if the database is reporting an error. The CMDB helps place these alerts into the context of the affected application.

This interaction is also valuable for planned changes: if a server requires maintenance, the CMDB shows the documented dependencies. In ITSM, the review, approval, and execution of the change are organized.

The CMDB provides an overview of your IT. IT service management ensures that your team uses this information within structured workflows.

The CMDB documents your IT landscape

A Configuration Management Database, or CMDB for short, captures vital information about your IT components. These include, for example, servers, laptops, applications, network devices, and locations.

These documented elements are referred to as Configuration Items, or CIs. The CMDB also describes their relationships: Which application runs on which server? Which systems support a business service?

This creates an information baseline that enables your team to understand technical relationships. You can find an overview of structure and deployment options on our page about CMDB solutions and their use cases.

ITSM organizes your IT services

IT service management, or ITSM for short, describes how you deliver, manage, and improve IT services. This includes handling incidents, fulfilling service requests, and planning changes.

A ticketing system supports these tasks. For effective ITSM, you also need clear responsibilities, traceable workflows, and agreed service level targets.

The CMDB describes your IT landscape. ITSM uses this information for day-to-day work. Learn more in our overview of IT service management.

Free CMDB & ITSM solutions: What approaches are available?

Free software can provide an entry point without incurring immediate licensing fees. However, offerings differ in their functional scope and operating model.

To make the right choice, you should first determine which tasks you want to cover.

Shared platform for documentation and service processes

One approach is to manage both CMDB and ITSM within a single application. Device information, tickets, and service processes are then available in a unified environment.

This can simplify implementation because fewer separate applications need to be integrated. Nevertheless, verify whether the platform meets your requirements for documentation, relationships, and workflows.

An integrated CMDB is only helpful if it reflects the information your team actually needs.

Connecting specialized applications

Alternatively, you can connect a standalone CMDB to a ticketing system. In this setup, each application handles a clearly defined task.

The CMDB manages items such as devices, applications, and technical relationships. The ticketing system organizes requests, communication, and resolution steps.

This approach can make sense if you already use a ticketing system or have specific requirements for your IT documentation. However, interfaces, data mappings, and responsibilities must be carefully configured.

Putting free usage into perspective

Distinguish between permanently free software, limited freemium offerings, and time-limited trial versions.

Even within a single offering, additional features, add-ons, or support services may incur costs. Therefore, review the specific edition and its terms carefully.

When searching for ITSM or CMDB software, do not just look at feature overview lists. What matters is which capabilities are actually available to you in the selected edition.

Which features do you really need?

A long list of potential features offers limited help during evaluation. Start with concrete questions from your daily operations:

• Which devices, applications, and services need to be documented?

• Which relationships does support need for troubleshooting?

• Which requests and changes do you want to process?

• Which interfaces to third-party solutions will we need?

• What information should be exchanged between applications?

• Who will be allowed to view or modify data later on?

Your requirements can be derived directly from these answers. For a CMDB-ITSM connection, unambiguous object mappings, appropriate interfaces, and traceable changes are especially relevant.

Additionally, check whether existing data can be imported and later exported again. This simplifies both the initial setup and any potential system migration in the future.

Tool integration: How CMDB and ITSM work together

Connecting two applications does not improve a process on its own. First, define which information is maintained where and how your team should use it.

1. Define the leading data source

It should be clear for each type of data which system is authoritative. A potential breakdown looks like this:

This mapping is an example. It must fit your specific environment.

Avoid having team members maintain the same information in multiple applications. Otherwise, conflicting information can arise and maintenance overhead increases.

2. Link tickets to devices and services

To ensure a ticket is assigned to the correct device, you need a reliable identifier. A device name alone can be unsuitable because it can change or appear multiple times.

A unique object ID facilitates permanent linking. This ensures it remains traceable which components were affected by an incident or change.

3. Transfer only required information

Not every field needs to be synchronized between the CMDB and the ticketing system. Often, it is sufficient to display relevant information and link the affected object.

For transferred data, define the direction in which the exchange occurs. Also specify what should happen in case of conflicting values.

This keeps the integration manageable and easier to maintain.

4. Automate a clear workflow

For example, start with device selection during a support request. Additional steps can follow, such as updating a status following an approved change.

Account for missing data and unavailable interfaces. A failed exchange should be recognizable and allow for targeted manual follow-up.

Practical example: An application is unavailable

An employee reports an incident. In the ticket, the affected application is linked to the asset from the CMDB.

Support can then check which server the application runs on, which database it uses, and which team is responsible. If the corresponding business services are documented, potential impact can also be assessed more accurately.

After resolution, the record remains linked to the application. If another incident occurs, the team can review previous measures and resolve issues faster.

This example illustrates the practical value of an ITSM-CMDB integration: technical information is readily available in context with the respective support case.

Templates simplify getting started

Templates for CMDB and ITSM help record information consistently. For a server, the following details might be included:

• Unique ID and name

• Location and operational status

• Responsible team

• Operating system

• Assigned applications and services

• Date of last review

Organizations should also adapt such templates to their own requirements. Include only fields whose purpose and maintenance responsibilities are clearly defined.

If procurement, contracts, and lifecycles also need to be considered, IT Asset Management complements the documentation.

Free does not mean zero effort

Even without license fees, implementation and operations require effort. This includes installation, data migration, interface configuration, updates, backups, and training.

Ongoing maintenance must also be factored in. New devices must be logged, decommissioned systems flagged, and changed relationships updated.

Therefore, compare the total effort required for a solution. Consider your team's working hours and the need for external support as well.

A free CMDB-ITSM solution makes sense if it meets your requirements and can be sustainably maintained over the long term.

Conclusion: Value is created through reliable data and clear workflows

Free solutions can make getting started with CMDB and ITSM easier. Whether you use a shared platform or connect specialized applications depends on your requirements and existing systems. What matters most is that the solution supports your team in their day-to-day work.

A CMDB creates the informational foundation for this: it documents devices, applications, responsibilities, and technical dependencies. By connecting it with ticketing, inventory, and monitoring systems, this information can be leveraged when resolving incidents and planning changes.

However, the real value only emerges when data is reliable and workflows have been tested in practice. Interfaces facilitate data exchange, but they do not replace clear responsibilities. Therefore, define which system manages which information, who maintains it, and how changes are planned and applied.

Start with a manageable use case, such as linking support tickets to affected devices. Verify data quality and test the workflow in daily operations. Building on this foundation, you can document additional services and automate further processes.

When evaluating options, also consider the effort required for setup, operation, and maintenance. An appropriate CMDB-ITSM solution not only saves licensing costs, but also streamlines troubleshooting, visualizes dependencies, and eliminates duplicated effort.

Further information on CMDB solutions, use cases, and interfaces will help you find the right approach for your IT environment.

Test i-doit group software productively now.

The i-doit group is the leading software manufacturer for IT documentation, CMDB, ITSM & cabling management, as well as for ISMS, emergency management & data protection. Over 2,000 active customers trust us for their digital resilience.

Test for 30 days!