How to Migrate Data from a CSV file
To import your data, you will need to provide three files that contain Tickets, Comments, and Knowledge Base articles. Each file should be formed and uploaded separately. In this article, you will find guidelines for migrating your data from CSV.
CSV file requirements
First and foremost, each file must possess a heading row with a summary column. The heading row is necessary to identify and map data objects. The header row should:
- Avoid any punctuation (apart from commas separating the columns).
- Be written in English (the language of the content in the second and other rows does not matter).
- Have each column begin with a capital letter.
Additionally, you should also consider the following:
- The size of each file should not exceed 1 GB.
- Fields should be separated by commas.
- Use double-quote marks (") to capture data that spans multiple lines. Typically used for tags, attachments, and descriptions.
- To attach files you need to provide a URL following which our service will be able to access the attachment. You may add multiple attachments. To do this, separate them by commas and quote the values in the field. Note that URLs for attachments support both HTTP and HTTPS protocols.
Preparing the file with Tickets (download sample)
To import tickets to the help desk of your choice, you should have a CSV file which contains a heading row with the following columns:
| Column | Example | Import notes |
| TicketId | 468985 | Required |
| Subject | Test subject | Required |
| Tags | "tag 1, tag 2" | Optional |
| DepartmentName | Support | Optional |
| Description | "Test Description" | Required |
| Type | Task | Required |
| Status | Open | Required |
| Priority | Low | Required |
| AgentEmail | a.lewis@yourcompany.com | Required |
| AgentName | Adam Lewis | Required |
| ContactEmail | s.gibbson@mail.com | Required |
| ContactName | Stacey Gibbson | Required |
| ContactPhone | 1234567890 | Optional |
| CompanyName | Faux Mart | Optional |
| CreatedTime | YYYY-MM-DD HH:MM:SS | Required |
| UpdatedTime | YYYY-MM-DD HH:MM:SS | Required |
| ClosedTime | YYYY-MM-DD HH:MM:SS | Optional |
| Attachments | "https://site.com/attachment1.jpg, https://site.com/attachment1.pdf" | Optional |
Importing custom fields
To migrate custom fields you need to add tags to field values so that the Migration Wizard could identify them as such. Here are the tags you need to use:
_select- dropdown (e.g.product_select)_date- time (e.g.due_date)_integer- number (e.g.TicketInternal_integer)
You can migrate and map other custom fields as text fields using the _textArea tag.
Preparing the file with ticket comments (download sample)
Your CSV file with ticket comments should possess a heading row with the following columns:
| Header | Format | Field |
| CommentId | 468985 | Optional |
| TicketId | 485853 | Required |
| AuthorEmail | jeremy@yourcompanydomain.com | Required |
| Public | 0-private, 1-public | Required |
| Body | "Test comment" | Required |
| CreatedTime | YYYY-MM-DD HH:MM:SS | Required |
| Attachments | "https://site.com/attachment1.jpg, https://site.com/attachment1.pdf" | Optional |
You should gather all ticket comments in one file. For tickets that have multiple comments, the formatting should look like this:
Preparing the file with knowledge base articles (download sample)
To import knowledge base articles, provide a CSV file that contains a heading row with the following columns:
| Header | Format | Field |
| Title | Creating discount codes | Required |
| Category | Discounts | Required |
| Folder | Offering discounts and setting sale prices | Required |
| Description | "The body of the article" | Required |
| Status | Published | Required |
| Tags | "account, setup" | Optional |
| Attachments | "https://site.com/attachment1.jpg, https://site.com/attachment1.pdf" | Optional |
IMPORTANT
- The body of the article can contain HTML formatting if you need to keep it.
- Article statuses can differ. We accept all statuses, just make sure to map them when configuring your migration.
- Your CSV file cannot contain folders with identical names, even if they belong to different categories. Rename such folders to be able to import them
Importing your CSV files
Once your CSV files have been prepared, log into Help Desk Migration and start the import process.