Import Tickets from CSV File

Transferring your existing ticket data from one platform to another can be quite a task, especially if you’re creating and inputting each record one by one. Our Accelo user are able to mass import Tickets or make a mass edit update to your existing Tickets via our Import Tickets CSV functionality.

To import a sample Tickets CSV file, click here.

Reviewing and Preparing your CSV File for Import

Before you import, you’ll want to check that your CSV is properly formatted and that fields from your CSV exist in Accelo.

• Your CSV file must contain the asset’s Issue Title, Issue Type, Issue Status, Company Name, and Contact First Name and Last Name fields at a minimum.

• Your CSV should be limited to 1000 rows to optimize import performance. Files with more rows of data may stall out so that the import process does not complete.
  
  

1. Make sure your CSV is correctly formatted:

   1. For any cell with multiple values, eliminate all spaces between delimiters (commas, ampersands, etc) and values. For example, “Staff, Accounting” NOT “Staff, Accounting".

   2. The Ticket type refers to the type title that is set up in Settings > Tickets > Types, Progressions & Fields.

   3. The Ticket status should be the exact status title particular to the specific type.

   4. It is recommended that the Ticket Manager field contains the ID number of the user who will be managing the asset in Accelo (if applicable).

   5. Be consistent with the date format. Pick one format and stick to it (MM/DD/YY or DD/MM/YY, etc.).

   6. Please note that you can only import resolution values when the ticket is already closed or will be imported as closed/statuses with “inactive” standings.

2. Set up custom ticket fields from your CSV into Accelo: As part of the import process, you’ll have the opportunity to select the CSV fields that you wish to import into Accelo. If certain fields contain no data or aren’t as critical for the import, they can be ignored.

   1. The custom ticket field will use the same title and value options found in the specific column in your spreadsheet.

   2. To add a custom ticket field, click the Configuration gear, go to Ticket then Custom Profile Fields and click the Add profile button.
      
      

3. Make sure all values for Types, Status and Manager from your CSV exist in Accelo before import. If these values are not already added, Accelo cannot match them to Tickets.

Running the Import

After reviewing the format of your CSV and configuring Accelo to have fields matching your import file, it’s time to start the import.

1. Upload your CSV file:

   1. From the Import & Exports section in Configuration, click the Import button under CSV Import: Ticket. Browse for the .csv file by clicking Upload CSV File.

2. Drag column values from your CSV (on the left) to the correct space on the right.

   1. You also have the option to Add an Additional Ticket or Contact, which will just allow you to map separate fields to this area.
      

3. Map your CSV Fields:
   

   1. Your CSV column names will be on the left, and you’ll map the import to the appropriate Accelo fields it will populate from the dropdown. Once completed, mapping the fields should look something like this:
      
      
      

4. Choose your Matching and Merge Options:

   1. You may have already created assets into your deployment. Because of this, we offer a number of Matching & Merge Options should we find any Ticket that already exists in your Accelo account and will cover these details below:

• • Matching Ticket: Choose what Accelo looks for to find a duplicate/matching Ticket. By default, we will identify it based on the Ticket Title, Type and Status, by the Company Name, and by the Contact Firstname and Lastname values, and you can require a match to involve multiple fields from your CSV import as well.

  • When a match is found:

    • Do Nothing - Skip: We will not touch the existing match in Accelo and not import any values in the corresponding row of the CSV import.

    • Do not overwrite: Only update empty fields: We won't overwrite any existing data but will populate any blank Accelo fields with values from the import. This is the default.

    • Overwrite - Update all fields: Every mapped and matching field in the CSV import will overwrite any existing Accelo field.

• When multiple matches are found:

  • • Match most recently created: Match the one that has the most recent creation date within Accelo. This is the default.

    • Match first created: Match the one that has the earliest creation date within Accelo.

    • Match most recently edited: Match the one that most recently has had an edit to its key fields, such as Type or Status.

• Certain required fields will need a Fallback value associated with them as they cannot be left blank on the import. Please set a fallback value, even if you’ve confirmed all fields have values, before proceeding to the final step of the import process.

Preview your Import:

• • Check the Preview in Accelo to make sure it looks similar to your CSV file. The only difference is that column names are now named after the Accelo field it will be going under.

  • If everything looks correct, hit Complete at the bottom right, then Proceed to begin the import.

Import Results & Viewing the Log

The import process may take a few minutes depending on the depth of your CSV. During this time, you’ll find a View Logs option available where you initiated your Import.

The log will give you a very detailed breakdown on what was successfully imported, and what wasn't, and can even be expanded to show you the details and logic behind each field being mapped.

If you find you still have a lot of duplicate assets, contacts or companies in the system after importing, you can manually clean them as you discover them through merging.