The 12 Most Common DCIM CSV Import Errors — and How to Fix Them

Why DCIM Imports Fail

Every DCIM platform has an import wizard. Every import wizard accepts CSV files. And every DC engineer who has used one has experienced the same frustration: a file that looks correct fails with cryptic errors, or worse, imports silently with missing rows.

The good news is that DCIM import failures are almost entirely predictable. The same twelve errors account for the vast majority of failed imports across NetBox, Sunbird dcTrack, and Device42. Once you know what to look for, you can fix them before they reach the import wizard.

Error 1: Manufacturer Slug Mismatch (NetBox)

Symptom: Import fails with "Matching query does not exist" on the manufacturer column.

Cause: NetBox identifies manufacturers by slug, not by display name. The value in your manufacturer column must be a slug — lowercase, hyphens instead of spaces — that exactly matches an existing manufacturer in your target NetBox instance. "Dell Technologies" will fail; "dell-technologies" will succeed, but only if that slug exists.

Fix: Export the manufacturer list from your NetBox instance (Devices → Manufacturers → Export) and use the slugs from that export as your reference. If a manufacturer does not exist yet, create it before running the device import.

Error 2: Device Type Slug Mismatch (NetBox)

Symptom: Import fails with "Matching query does not exist" on the device_type column.

Cause: Same as manufacturer slugs, but for device types. The device_type column must contain the slug of an existing device type, not the model name. "PowerEdge R640" will fail; "dell-poweredge-r640" will succeed — but only if that device type has been imported from the NetBox Device Type Library.

Fix: Import device types from the NetBox Device Type Library before importing devices. Use the manufacturer + model slug as your device_type value.

Error 3: Make/Model Not in Models Library (dcTrack)

Symptom: Rows are silently skipped after import. The imported count is lower than the source row count.

Cause: dcTrack requires every Make + Model combination to exist in its Models Library before a device can be imported. If the combination is not in the library, dcTrack skips the row without an error.

Fix: Before importing, export your unique Make + Model combinations and verify each one exists in your dcTrack Models Library (Administration → Models Library). For missing models, either add them manually or use the dcTrack model request process.

Error 4: Duplicate Serial Number (Device42)

Symptom: Import fails with "Serial number already exists" even though the device appears to be new.

Cause: Device42 enforces global serial number uniqueness — a serial number cannot appear on two devices, regardless of site or building. If your source data contains duplicate serials (common when assets are re-used or when placeholder serials like "N/A" are used), Device42 will reject the duplicates.

Fix: Before importing, identify duplicate serials in your source data. For genuine duplicates, keep only the most recent record. For placeholder serials, clear the serial field — Device42 accepts blank serials.

Error 5: Missing Required Fields

Symptom: Hard import failure with "This field is required" or similar.

Required fields by platform:

• NetBox: name (device name), device_role, manufacturer, device_type, status, site
• dcTrack: Name, Make, Model, Location
• Device42: name, hardware (device type)

Fix: Run a pre-flight check before importing. Identify rows with missing required fields and either populate them or exclude those rows from the import batch.

Error 6: Invalid Status Value

Symptom: Import fails or defaults to a wrong status for some rows.

Cause: Each platform has a fixed set of valid status values. NetBox accepts: active, staged, planned, failed, inventory, decommissioning, offline. dcTrack accepts: Installed, Planned, Storage, Off Site, Archived, Power Off. Device42 accepts: in service, not in service, decommissioned.

Fix: Map your source status values to the platform's valid set before importing. Common source values like "live", "production", "spare", and "retired" all need to be translated.

Error 7: Site Does Not Exist (NetBox)

Symptom: Import fails with "Matching query does not exist" on the site column.

Cause: NetBox requires the site referenced in your import to already exist. The site column must contain a site slug, not a display name.

Fix: Create all required sites in NetBox before importing devices. Export your site list and verify slugs match your import data.

Error 8: Location Hierarchy Not Pre-Created (NetBox)

Symptom: Import fails on the location or rack column.

Cause: NetBox's location hierarchy (Site → Location → Rack) must be pre-created. You cannot import a device into a rack that does not exist.

Fix: Create the full location hierarchy — sites, locations, and racks — before importing devices. For large inventories, use the NetBox bulk import feature for each object type in order.

Error 9: U Position Out of Range

Symptom: Import fails with "Invalid rack unit" or similar.

Cause: The U position in your import data is higher than the rack height in NetBox. A 42U rack cannot have a device at position 43.

Fix: Verify rack heights in your NetBox instance match your source data. For devices with unknown U positions, leave the position field blank rather than entering a placeholder value.

Error 10: Encoding Issues in the CSV

Symptom: Import fails with parse errors, or special characters appear garbled after import.

Cause: DCIM platforms expect UTF-8 encoded CSV files. Files exported from older Windows applications may be encoded in Windows-1252 or Latin-1, which causes parse failures on non-ASCII characters (accented letters, em dashes, trademark symbols).

Fix: Re-save the CSV as UTF-8 before importing. In Excel: File → Save As → CSV UTF-8 (Comma delimited). In Google Sheets: File → Download → CSV (the output is always UTF-8).

Error 11: Formula Injection in Cell Values

Symptom: Import succeeds but some values are wrong, or the platform reports a parse error on specific rows.

Cause: Some asset fields contain values that start with =, +, -, or @ — characters that spreadsheet applications interpret as formula prefixes. When these values are exported to CSV and re-imported, they may be evaluated as formulas rather than literal strings.

Fix: Before importing, scan your CSV for cell values starting with =, +, -, or @. Prefix them with a single quote or wrap them in double quotes to force literal interpretation.

Error 12: Column Header Mismatch

Symptom: Import wizard cannot map columns, or all data lands in the wrong fields.

Cause: DCIM platforms are case-sensitive about column headers. NetBox expects lowercase_with_underscores. dcTrack expects Title Case. Device42 has its own header format. A header like "Device Name" will not map to NetBox's "name" field.

Fix: Use the platform's official import template as your column header reference. Do not modify the headers — only the data rows.

The Fastest Fix: Normalise Before You Import

Running a normalisation pass before import eliminates errors 1, 2, 3, 5, 6, and 12 automatically. A normalisation tool like Struktive standardises vendor names to platform-compatible slugs, maps status values to the correct enum, structures location fields into the required hierarchy, and generates a target-format CSV with the correct column headers for each platform.

For the remaining errors — missing required fields, duplicate serials, encoding issues — the normalisation output includes a quality score and pre-flight report that flags affected rows before they reach the import wizard.

For a complete guide to the normalisation process, see What Is DCIM Data Normalisation. For platform-specific import guides, see How to Import Data into NetBox and Sunbird dcTrack Data Migration Guide.