Asset Import

Starting fresh or migrating from another help desk? If migrating, import in this order to keep everything connected:

  1. Users
  2. Assets (below)
  3. Tickets
  4. Knowledge base articles

A few things to know before importing

  • Asset Name is required. Map a CSV column to it: rows with a blank Asset Name are not imported and are reported as errors. Every other field is optional. (Exception: if you check "update existing assets" and match on a unique identifier, Asset Name is not needed, since those assets already have one.)
  • The import can create new asset types, locations, and departments but only at a single level. Nested locations and departments can be organized manually after import
  • If assets are linked to existing tickets, assets must be imported before tickets
  • The following fields are available for mapping:
    • Asset Tag
    • Serial Number
    • Legacy Reference Number
    • Asset Name (required)
    • Description
    • Asset Type
    • Location
    • Department
    • Manager's Email
    • User's Email
    • Notes
    • Purchased Date (yyyy-mm-dd)
    • Cost
    • Purchase Order Number
    • Vendor
    • Replaced Date (yyyy-mm-dd)
    • Warranty Info
    • End of Contract Date (yyyy-mm-dd)
    • Contract Notes
    • Status
    • Condition
    • Birth Date (yyyy-mm-dd)

Linking assets to tickets

Asset-to-ticket relationships can be preserved during import. Import assets first, then tickets.

When importing tickets, map the CSV columns to the ticket fields, including the asset field. Mojo uses the value in that field to find a matching asset, checking in this order and moving to the next if a field is blank:

  1. Legacy reference number
  2. Asset name
  3. Asset tag

If a match is found, the asset is linked to the imported ticket.