Troubleshoot CSV import

When a CSV import does not produce the expected result, the issue usually comes from formatting, matching by name, or column mapping.

Use this page when the import technically runs but the result is wrong, incomplete, or surprising.

If you need to restart from the full workflow, go back to Prepare your CSV file or Import a CSV file.

Common problems

Problem	Likely cause	What to check
Preview looks broken	Wrong delimiter or encoding	Change delimiter or encoding before import
Rows are skipped	Empty or invalid Name values	Check the Name column values
Assets are duplicated	Name values are not stable or not unique	Recheck the Name values used for matching
Properties are empty	Wrong column mapping	Review property mapping
List values are ignored	CSV values do not match Boldo values	Review list or yes/no mappings
Relationships are missing	Wrong relation mapping or wrong separator	Review relation mapping and cell format

If characters look corrupted

Try another encoding, such as:

• UTF-8
• ISO-8859-1
• Windows-1252

If too many new assets are created

This usually means Boldo could not match rows to existing assets.

Check:

• the Name column used for matching
• the exact spelling of the Name values
• whether names changed between imports

If list or yes/no values do not match

Review the manual mapping for:

• single-choice values
• multi-choice values
• yes/no values

The CSV values must be matched explicitly to the values defined in the metamodel.

If relationships are not created correctly

Check:

• the target relation column
• the related asset names used in the cells
• the separator when several related assets are stored in one cell

If one cell contains several related values, use the expected separator consistently.

How to debug

Check problems in this order:

1. file format
2. Name values used for matching
3. property mapping
4. value mapping
5. relation mapping

If the result is still unclear:

1. stop the full import
2. reduce the file to a small sample
3. fix one issue at a time
4. rerun the sample import
5. only then rerun the full file

This is almost always faster than debugging a large broken import after the fact.