Prepare your import file

A clean import file makes the import much faster and safer.

Most import problems are preparation problems before they become Boldo problems.

Basic format rules

Your file should follow these rules:

• use the .csv or .xlsx format
• put column names on the first line
• use one row per asset
• for CSV files, keep one consistent delimiter in the whole file

For CSV files, Boldo can usually detect common delimiters:

• comma
• semicolon
• tab
• pipe

Choose a good import key

Before importing, decide how Boldo should match each row to an existing asset.

Boldo supports three matching modes:

• By name - Boldo matches rows using the Name column. The name must be stable, non-empty, unique, and consistent across imports.
• By Boldo ID - Boldo matches rows using the Boldo ID column. This is the internal identifier included when you export from Boldo. It is the most reliable matching method for round-trip workflows.
• By unique key - Boldo matches rows using a unique key property defined in the metamodel, such as a product code or external reference. This option appears only when the target asset type has a unique key property.

If your file comes from an earlier Boldo export, it already contains a Boldo ID column. Boldo detects it automatically during import.

If you are importing data from an external source and the asset type has a unique key property, matching by unique key is the safest choice. The unique key stays stable across systems, unlike names that can vary in spelling or formatting.

If the asset type has no unique key, use the Name column. Make sure names are stable enough to avoid accidental duplicates.

Clean your data

Before importing:

• remove empty duplicate rows
• normalize spelling for statuses and lists
• remove accidental extra spaces
• check date formats. Boldo accepts YYYY-MM-DD, YYYY/MM/DD, DD/MM/YYYY, and DD-MM-YYYY during import.
• confirm numeric values are really numeric

If a property can contain multiple values in one cell:

• use one consistent separator
• document it before mapping

Example:

Java, React, PostgreSQL

A relationship column should contain the value used to find the related asset.

Examples:

• a team name
• an application name
• a server name

When a cell contains several related assets, use the separator expected during mapping.

Keep related names consistent, otherwise Boldo may create several near-duplicate related assets.

Watch out for these common mistakes

Problem	Why it causes issues
Missing header row	Boldo cannot map columns correctly
Duplicate identifiers	Update and create behavior becomes ambiguous
Mixed separators	Rows are read incorrectly
Wrong encoding	Characters appear corrupted
Inconsistent list values	Mapping becomes unreliable

Recommended method

For a first import:

1. test on a small sample
2. validate the result in Boldo
3. correct the mapping if needed
4. import the full file

If your import file uses the same filename as the asset type, Boldo can preselect that asset type automatically.

If your import file uses the expected column names, Boldo can also prefill the matching properties and relationships automatically.

In practice, the easiest starting point is often to export a small file from the target inventory with Actions > Export, then edit that file instead of starting from scratch. The exported file includes a Boldo ID column that makes re-importing reliable.

Before starting the real import, make sure:

• the preview is readable
• the key column is complete and stable
• the important properties are clean enough to map confidently
• relationship columns use consistent names

Continue with Import a file when the file is ready. If the result still looks wrong, use Troubleshoot import.