Import & Export

Asset Import

Starting fresh or migrating from another help desk? If migrating, import in this order to keep everything connected: Users Assets (below) Tickets 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 i...

How do I import knowledge base articles?

Migrating from another help desk? Agents with a manager or admin role can import existing tickets, users, assets, and knowledge base articles. The recommended import order is Users Assets Tickets Knowledge Base Articles (details below) Importing knowledge base articles Importing a large numbe...

How do I import tickets?

If you are migrating from another help desk, then you may have existing tickets, users and assets you may want to move. The recommended order of importing is as follows. Click on each of the items for more information on how to best import. Users Assets Tickets (below) Knowledge Base Articles ...

How to export ticket data

Exporting ticket data can be useful for: Analyzing trends or performance outside of Mojo Helpdesk Backing up ticket records for internal archives or audits Sharing specific ticket data (including custom fields) with stakeholders who don’t have Mojo Helpdesk access When exporting tickets, the fo...

Import Linked Assets and Tickets

Assets and tickets can be imported while preserving their association. 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 ...

User Import Overview

Migrating from another help desk? Import in this order so records link up correctly: Users (this article), then Assets, Tickets, and Knowledge base articles. Before you start File must be .csv, encoded as UTF-8 Up to 3,000 users per import Any custom user fields must already exist in your accou...