Migrating historical tickets into SuperOps is essential for preserving critical context, such as recurring issues, past resolutions, and long-term service patterns. To simplify this process, SuperOps provides a guided CSV importer that validates your data, maintains relationships between records, and ensures historical accuracy for your IT team.
Prerequisites for Ticket Import
To ensure all ticket data is linked correctly, you must import or create related information before migrating tickets. We recommend following this order:
Importable items (in this order):
Sites
Requesters
Technicians
Service Catalog (only if referenced)
Tickets
Worklogs, Notes, Conversations (optional, after tickets)
Manual setup:
Departments must be created manually, as they cannot be imported. Create them first if your ticket CSV references department values.
Understanding the Ticket Reference ID
The Ticket Reference ID is the unique identifier that connects all your historical ticket data. When importing tickets, you must map your old system’s ticket ID to this field. SuperOps will assign its own internal ID but will retain your original ID as the Ticket Reference ID. This ensures that any future imports, such as ticket notes, conversations, or worklogs, are correctly matched to the original ticket record without creating duplicates.
Migrating Your Tickets
Follow these steps to import your tickets using the CSV importer:
Begin from your main dashboard. Click on your profile icon in the bottom-left corner to open the user menu.
In the user menu, select Product Onboarding.
On the Product Onboarding page, click the Migrate data button to see the available import options.
On the data migration page, locate the Import Tickets section and click the CSV Import button to launch the import wizard.
Upload your CSV file. You can either drag and drop the file or click Choose a file to browse your computer. Supported formats include .csv, .tsv, .txt, .xls, .xlsx, and .xml.
Next, map the columns from your file to the corresponding fields in SuperOps. The system automatically maps columns with matching names, but you should carefully verify key fields like Ticket Reference ID, Priority, Status, Site, and any custom fields.
After mapping, SuperOps validates the file for issues like missing required fields, incorrect data types, or formatting errors. You can correct these problems inline or choose to exclude the affected rows from the import.
Once you confirm the import, a notification will appear indicating that the process is in progress. You will receive a summary report via email after the import is complete.
This email will detail the number of successful and failed entries, along with a downloadable CSV file explaining any errors.
Importing Ticket Notes, Conversations, and Worklogs
After your tickets have been successfully imported, you can proceed to import associated ticket notes, conversations, and worklogs. When preparing your CSV files for these items, ensure that each row contains the same Ticket Reference ID that was used during the main ticket import. This guarantees that all historical activity is attached to the correct ticket record.


