Skip to main content

Allow Asset Link fields to resolve relationships by Asset Name or Lookup Field during CSV import

When importing interconnected assets into Hudu, Asset Link fields currently require internal Hudu Asset IDs.

For larger environments this creates a complex and time-consuming workflow:

  1. Import Physical Servers.

  2. Export assets to obtain generated Asset IDs.

  3. Modify CSV files and replace names with IDs.

  4. Import Virtualization Platforms.

  5. Export again to obtain new IDs.

  6. Modify CSV files again.

  7. Import Virtual Machines.

For infrastructures containing physical servers, virtualization hosts, clusters, VMs, applications, and dependencies, multiple import/export cycles are required before relationships can be established.

The process becomes particularly difficult when migrating data from another CMDB, documentation platform, or asset management system where Hudu IDs are not available beforehand.

Suggested Solution

Provide additional matching options for Asset Link fields during CSV import:

Option 1: Match by Asset Name

Allow imported values to match existing assets using the Asset Name instead of internal Asset IDs.

Example:

VM Name

Hosted On

APP01

ESX01

APP02

ESX01

During import, Hudu would automatically resolve "ESX01" to the corresponding asset.

Option 2: Select Lookup Asset Type

For Asset Link fields, allow administrators to specify:

  • Asset Type to search in

  • Matching field

    • Name

    • Serial Number

    • Hostname

    • Custom Field

    • External ID

Example:

Hosted On

  • Asset Type: Virtualization Platforms

  • Match Field: Name

Hudu automatically links APP01 to the Virtualization Platform named ESX01.

Option 3: Mixed Import Mode

Allow both:

  • Direct ID matching (current behavior)

  • Name/Lookup matching (new behavior)

This preserves backward compatibility while offering a simpler onboarding and migration experience.

Benefits

  • Faster onboarding of new Hudu customers.

  • Easier migration from IT Glue, Confluence, CMDBs, spreadsheets, and other documentation systems.

  • Reduced manual import/export cycles.

  • Fewer CSV preparation errors.

  • Better support for large environments with complex asset relationships.

  • More intuitive behavior for administrators who typically know asset names, not internal database IDs.

Business Impact

Organizations migrating hundreds or thousands of assets can spend significant time exporting data solely to retrieve Hudu-generated IDs required for relationship imports.

Supporting lookup-based relationship resolution would dramatically reduce migration effort and improve the overall data import experience, particularly for MSPs and enterprise environments managing physical servers, virtualization platforms, and large numbers of virtual machines.

Log in to comment and vote

No comments yet

Be the first to share your thoughts.