Do we need to replace our entire service desk first?

No. Agree the scope you want to evaluate and use representative data before deciding on a wider rollout. If you plan to replace an existing tool, verify its workflows, integrations and historical-data requirements separately.

Does the import include every old ticket and attachment?

The import covers the agreed data you provide. It is not a promise to recreate every historical record, attachment, integration or workflow from another system. Agree what to import and what to retain separately.

Will the CMDB stay current automatically?

Ongoing accuracy depends on maintained sources, configured connections and people responsible for updates. Importing records does not remove the need to review ownership and relationships.

What happens after the free pilot?

The pilot lasts two weeks, includes a real data import and up to 3 operators, and can be extended by agreement. A paid subscription starts only with explicit consent. ITLedger costs EUR 69 per agent per month excl. VAT, with a minimum of 3 agents and annual billing.

Set up a CMDB from your existing data

Bring your spreadsheets, exports and documents. We'll agree a starting scope, import the data you provide and review the result together. A free two-week pilot lets your team assess ITLedger with familiar records.

Discuss your free pilot Explore the product

From scattered records to a usable CMDB

Agree the first scope

Choose the applications, assets and service questions that matter first. Identify the source records and who can confirm ownership and relationships.

Import and review together

Onboarding includes processing and importing the data you provide. Review the records, dependencies and missing information before using them for daily work.

Use it and keep it current

Try the records during an incident, request or change. Agree who updates owners, assets and relationships as the environment changes, then decide whether to continue.

See pricing and onboarding terms →

What should you bring?

Start with what you already have. You don't need a perfect dataset. Agree which sources to include and which information still needs a colleague's review.

An asset or application spreadsheet, or an export from your current tool.
Available owner, team, supplier and location information.
Documentation that explains systems and their dependencies.
A named person who can resolve conflicting or missing information.

What is included in onboarding?

Onboarding and import of the data you provide are included. Very large or unstructured datasets may need extra processing. We explain the work and agree any extra cost before starting. Additional help with workflows, API or SSO setup can fall under the consulting pack; see the pricing terms.

What could your first CMDB scope look like?

Illustrative starting point: one business application and the records your team needs to support it. Your scope can cover different systems and relationships.

Application: The application, its purpose and the team that uses it.
Infrastructure: The servers, databases or other systems it depends on.
Responsibility: The owner, support team and relevant supplier.
Service work: A linked incident or change, with relevant knowledge and history.

How do you know the result is useful?

Can a colleague find the application's owner and supporting systems?
Can the team identify the relationships that matter during an incident or change?
Are missing or conflicting facts visible and assigned for review?
Is it clear who will keep the records current?

Questions about setting up a CMDB

Do we need to replace our entire service desk first?: No. Agree the scope you want to evaluate and use representative data before deciding on a wider rollout. If you plan to replace an existing tool, verify its workflows, integrations and historical-data requirements separately.
Does the import include every old ticket and attachment?: The import covers the agreed data you provide. It is not a promise to recreate every historical record, attachment, integration or workflow from another system. Agree what to import and what to retain separately.
Will the CMDB stay current automatically?: Ongoing accuracy depends on maintained sources, configured connections and people responsible for updates. Importing records does not remove the need to review ownership and relationships.
What happens after the free pilot?: The pilot lasts two weeks, includes a real data import and up to 3 operators, and can be extended by agreement. A paid subscription starts only with explicit consent. ITLedger costs EUR 69 per agent per month excl. VAT, with a minimum of 3 agents and annual billing.

Discuss your starting scope

Tell us what information you have and which service question your team needs to answer. We'll discuss a suitable pilot scope and how to assess the result.

Plan an introduction →