Documentation for JIRA 4.4. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata

About importing from Pivotal Tracker

JIRA ships with the JIRA Importers Plugin pre-installed, so that you can easily import your bugs from Pivotal Tracker. Version 2.5 or later of the JIRA Importers Plugin is required. If you have an earlier version you can upgrade it via the Universal Plugin Manager.

On this page:

The import process converts Pivotal Tracker data as follows:

Pivotal Tracker


Import Notes



Each Pivotal Tracker project is imported into a new JIRA project. You can optionally import into an existing project if you have used the importer before.



Pivotal Tracker story types are recreated in JIRA.









Attachments are extracted from the Pivotal Tracker database and saved to disk. The dates and user attaching the attachments will be retained.



JIRA will recreate the Pivotal Tracker workflow and statuses during import.



Pivotal Tracker labels with spaces are imported with underscores (JIRA does not support spaces in labels).

Story ID

Story ID and Story URL

JIRA will create these as custom fields.


Fix Version/s

Past iterations in Pivotal are imported as released versions in JIRA.

Story Estimates

Story Points


Order of stories


You will need to configure this custom field in JIRA after the import. If you are using GreenHopper, you may wish to activate issue ranking. This can be done either before or after importing your Pivotal Tracker data.

Time Tracker

Time Tracking

If you use time tracking in Pivotal this data will be automatically imported into a new JIRA issue type called 'Chore' with a Summary field value of "Placeholder for imported time tracking data".



The importer will automatically create JIRA users for any Pivotal Tracker users who do not exist in JIRA.

  • Passwords from Pivotal Tracker are not imported (as they are hashed in the database). Users from Pivotal Tracker will need to get their passwords emailed to them.
  • If you are using External User Management, the import process will not be able to create JIRA users; instead, the importer will give you a list of any new users that need to be created. You will need to create the users in your external user repository before commencing the import.
  • If you have a user-limited license (e.g. personal license), and the number of required users is larger than the limit, then the import will be stopped. A page will be displayed showing a list of users that can't be created.

User Roles

Project Roles

Viewer = User ; Member = Developers ; Owner = Administrators

How to import from Pivotal Tracker

  1. Before you begin, please back up your JIRA data. (If you have none then you can skip this step.)
  2. Log in to JIRA as as a user with the 'JIRA Administrators' global permission.
  3. Select 'Administration' > 'System' > 'Import & Export' > 'External System Import' > 'Pivotal Tracker'.
  4. Enter your Pivotal Tracker login and password credentials and click the 'Next' button. The 'Project Key Mappings' step is displayed:
    Screenshot 1: 'Project Key Mappings'
    • The check box of each Pivotal Tracker project to be imported is selected. To prevent a project from being imported, clear its check box.
    • By default, a new JIRA project for each Pivotal Tracker project you import will be created. (JIRA automatically suggests a name and key for each of these JIRA projects.)
    • If applicable, select 'Project category' for these JIRA projects.
    • To import a Pivotal Tracker project into an existing JIRA project, type in the exact name and key of the existing JIRA project.
      (warning) The existing JIRA project must also use the 'PT Workflow Scheme', which is created with your first Pivotal Tracker import.
  5. The importer will display updates as the import progresses, then a success message when the import is complete.
    Screenshot 3: the 'Success' page

Congratulations, you have successfully imported your Pivotal Tracker projects into JIRA! If you have any questions or encounter any problems, please contact Atlassian support.