You can import CSV (comma-separated values) files for Epics, Features, User Stories, Tasks, Bugs, Requests, Requesters, Test Cases, Impediments in Targetprocess.
CSV files are commonly used to mass-update Targetprocess data using spreadsheet editors (e.g. Microsoft Excel) or to transfer data between Targetprocess and third-party tools such as bug trackers etc.
Import from CSV files is just one method of batch data update in Targetprocess. Find other available methods in dedicated article: How to migrate or import data to Targetprocess from other project management system
Let’s say, we’re looking to create a simple project backlog. Stories can be added one by one, but it’d be faster to import them. For that, create a simple list with several user stories in Excel and save the file as a .csv. You can download and use this template.
Now go to
As a first step, you should Upload CSV file to Targetprocess. Then specify which entities you’re going to import, the entity type column (for the dynamic entity type definition), the location of your CSV file and select the column delimiter.
Targetprocess currently accepts 4 delimiters:
- , (comma)
- ; (semicolon)
- the Tab character
- | (the vertical bar character)
Entity Type selection
In the Entity Type column, choose “UserStory” if you want to import User Stories, or e.g. “TestCase” for Test Cases.
To define the imported entities dynamically, do the Select Type to Import step. Various entity types are imported separately. After importing the entities of one type, the wizard will return you to this step again. If some entity type has been selected at Step 1, the wizard will forward you on to Step 3.
At Step 3, you should Map CSV columns.
It’s a must to map the Project and ID columns for CSV files and Targetprocess entities, mapping the other columns is optional.
If the ID property is not mapped, all the entities will be inserted as New. If the ID column is mapped but empty, the entities will also be inserted as New. If the ID column is mapped and not empty, Targetprocess will try to update IDs for the entities with values specified in the CSV file.
When only one Project is selected in the project context menu, you can leave off the ‘Project’ field from the CSV file. In this case, only entities from the currently selected project will be imported/updated.
When two or more Projects are selected, or if entities from multiple Projects need to be updated, the ‘Project’ column should appear in your CSV file. With the Project ID columns mapped, you can update entities from any Project you have access to, even if these Projects are not currently selected. You can use either Project ID or Project Name in the Project Column.
You can not change Project for an Entity within the Import feature.
The Team and Role access permissions remain intact for Import. Administrators can import entities to any project and team, even to the ones they are not members of.
Entities and fields mapping
List of entities and fields that can be imported from CSV files and used in columns mapping is available in the dedicated article: Entities and fields supported for import from CSV files
You can map a Targetprocess entity field with a certain CSV column, or choose the ‘Skip’ option. For example, User Story may have the “Effort” property while in the CSV file you may have the “Estimated Effort” column, and you can map them. Custom fields can be imported as well.
Usually Targetprocess tries to define the mapping by itself, but in some cases it may fail with the resolution.
It is not possible to map two or more columns from a CSV file to one Targetprocess entity field.
First line of the CSV file can be skipped because usually it contains the header and the column names, not the data itself.
When you’re done mapping columns, click Next and Targetprocess will either do the import (that’s the Perform Import step) or will display a warning for possible mapping issues so they can be fixed manually.
As a last step, you can View Log of the completed import.
Import of hierarchical backlog
It is possible to import Features, User Stories and Tasks into your backlog altogether within single CSV file. Find detailed step-by-step guide in dedicated article.
Entity type must be spelled without spaces
When you are able to pass through columns mapping step but no entities are still imported, please check that entity type names are spelled correctly without spaces in between (e.g. UserStory, TestCase) and all mandatory fields are mapped and filled in.
Line breaks in Descriptions
To preserve line breaks when Importing from a CSV file, please use the <br /> HTML tag.
Fields not available for mapping
When some Entity Types or Custom Fields are missing in the mapping dialogs, check the context of currently selected Projects and that your user is a member of those Projects.
Set Creation Date during import
Creation Date field in Targetprocess entities is important for history tracking. Other dates such as Start Date and End Date depend on it. These fields are used when data is displayed on Timelines and in charts. It is not possible to modify creation date for existing entities. It also not possible to set start or end date to the moment before creation date for existing entities. However you can set custom creation dates for your new entities at the moment when you import them. More information: How to set Creation Date during import
Local symbols in names
When CSV file contains data other than in English, it should be encoded in UTF-8 with BOM format. Find more details here.
Huge files and performance
Importing of massive files with thousands of lines is slow. It may take several hours until the import finishes. Moreover, sometimes with large files it can stuck in the middle. Therefore, in order to increase stability and provide additional control over importing, we recommend you to split your input files into multiple batches having 500-1000 entities in each one.