The DCIM migration problem
Without Struktive
- Vendor names in 15 different formats — 'dell inc.', 'DELL', 'Dell, Inc.' — all need manual reconciliation
- Location strings like 'A-12-24', 'NYC-DC1-A-R03-U24', 'Rack 3 Row B' can't be imported without parsing
- NetBox requires device type slugs that must exist in the DeviceType Library — unknown models fail silently
- Duplicate assets from multiple source systems create import conflicts
- No way to know what will fail before running the import
With Struktive
- All vendor names normalised to canonical form using 250+ alias rules and acquisition history
- Location hierarchy parsed from any format — Site, Rack, and U position extracted and structured
- NetBox DeviceType Library validation: matched devices get the correct slug, unmatched flagged
- Duplicate detection across serial number, IP address, and vendor+model+rack+U composite key
- Pre-flight report shows exactly what to create in your DCIM before running the import
Supported platforms
NetBox
Slug-based CSVMatched against the NetBox DeviceType Library. Pre-flight validation for custom roles, missing device types, and site slugs.
Field mapping →Device42
3-row-header CSVAuto-creates manufacturers, hardware models, buildings, and racks on import. The most turnkey of the three profiles.
Field mapping →Sunbird dcTrack
Multi-sheet XLSXHierarchical location strings in dcTrack format. Companion 'Models Not Found' sheet for Models Library verification.
Field mapping →Pre-flight validation report
After every DCIM export, Struktive generates a pre-flight summary showing exactly what needs to be created in your target platform before running the import. No more discovering failures mid-import.
Custom roles
Roles that must be created before import
Missing device types
Models not in the DeviceType Library
Site slugs
Sites that don't exist in the target instance