How to Import Tickets in BoldDesk
BoldDesk provides a seamless way to import tickets, enabling quick ticket creation and efficient workflow management. This guide explains the process in detail, covering UI navigation, supported formats, and field mapping.
Check out this video tutorial for more details.
Why Use BoldDesk Ticket Import?
Importing tickets in BoldDesk helps teams:
- Migrate data from other systems.
- Bulk-create tickets for faster onboarding.
- Maintain accurate records with custom field mapping.
- When tickets are imported, the ‘created_at’ field is automatically set to the system’s current date and time. This value cannot be modified before or after the import.
- During ticket import, the Requester field in a ticket import file does not need to be a hyperlink. You can provide it as plain text, typically the requester’s email address. BoldDesk uses this email to match an existing contact or automatically create a new one if no match is found.
Step-by-Step Workflow for Importing Tickets in BoldDesk
BoldDesk allows importing tickets, enabling quick creation of tickets. Follow the given steps to import tickets.
- Access Import Data
-
Navigate to Admin > Import Data under the General section.
- Select Module and Brand
-
From the Modules dropdown, choose Tickets.
-
Select the preferred Brand based on your access permissions.
The brands shown in the dropdown menu are dependent on the current user brand access.
- Configure Email Notifications
-
Leave the Don’t send an email checkbox unchecked to ensure notifications are sent.
-
If checked, no email alerts will be sent to agents or customers.
-
- Upload Your File
-
Click Browse and select the file to import.
-
Supported formats: XLS, XLSX, CSV.
-
File size limit: 5MB, max 50 records.
-
Tags, watchers, and CC can be separated using ||.
-
Date format for resolution due: mm:dd:yyyy hh:mm:ss.
-
- Map Columns to BoldDesk Fields
-
Align source file columns with BoldDesk fields.
-
Required fields (marked with *) must be mapped.
-
- Fields marked with an asterisk (*) are required and must be mapped to a column from your source file.
- If the ‘Visible in Customer Portal,’ ‘Priority,’ and ‘Status’ fields are not mapped, the default values shown below will be applied.
- To use a Custom field during data import, ensure that the “Visible while creating the ticket” option is enabled in the field configuration as shown below.
| BoldDesk Fields | Default values |
|---|---|
| Status | Open |
| Visible in Customer Portal | True |
| Priority | Low |
-
Review and Confirm.
-
Preview mapped fields.
-
Click Import to start the process.
-
Option to Cancel Import if needed.
-
-
If the field mapping is configured according to your request, click the Import button. The imported ticket will be listed as indicated below.
You can cancel the import by clicking the Cancel Import button.
The request will be queued, and you will receive an email once the import is complete. After the automation process finishes, the corresponding user will receive an email for the respective tickets.
-
Once the ticket import is complete, click the View Details option to view the report.
* Added - Indicates the records that were successfully added.
* Failed - Indicates the records that could not be imported due to invalid values. -
Additionally, you can access the failed records along with the reasons for their failure. You have the option to download these records, correct the issues, and upload them again.
BoldDesk ticket import supports only structured ticket data (such as subject, description, and fields) through CSV/XLS files. It does not support importing inline images, attached images, videos, or file attachments as part of the import process. While these media types are supported within tickets after creation, they must be added manually, via email, or through APIs post-import.
Frequently Asked Questions
-
Can I import tickets with attachments in BoldDesk?
No, attachments are not supported during bulk import. They must be added manually after ticket creation. -
What happens if I skip mapping a required field?
The import will fail for those records. Ensure all mandatory fields are mapped. -
Is there a limit on the number of imports per day?
BoldDesk does not enforce a strict daily import limit. However, there are limits on the number of tickets that can be imported per file when using the Import Data option:- Momentum (Legacy) plan: Up to 25 tickets per file
- Enterprise plan: Up to 50 tickets per file
To import a larger number of tickets, you must split the data across multiple CSV files and import them separately.
-
Can I import tickets for multiple brands in one file?
No, imports are brand-specific. You must run separate imports for each brand. -
How do I handle failed records?
Download the failure report, correct invalid values, and re-upload the file. -
Can I import activity in BoldDesk?
No. BoldDesk does not support importing activities. -
Can I import a file to open multiple activities?
No. You cannot upload a file (CSV/XLS/XLSX) to create multiple activities. Importing is available for other modules like Tickets, Agents, and Groups—but not Activities. -
What is the default date for imported tickets?
The default date for imported tickets in BoldDesk is the system’s current date and time at the moment of import. -
When importing tickets, can the created date of the tickets be bound or adjusted?
No, you cannot change the created date of imported tickets in BoldDesk. The system sets the “created at” timestamp automatically at import time and it cannot be altered. -
How can I import tickets using the BoldDesk REST API?
No. BoldDesk does not provide a dedicated ticket import API. Instead, you can use the Create Ticket REST API to programmatically add tickets one at a time. For bulk migration, you must send multiple API requests to recreate tickets individually, as there is no native bulk import or batch upload endpoint in BoldDesk.
