Migrating from Other Issue Trackers
When migrating from another issue tracking application to JIRA, you may wish to take your data with you. Depending on what issue tracker you are migrating from, we recommend using the relevant instructions (linked below) to import data from your other issue tracker into JIRA.
Our website highlights some top reasons why people migrate from other issue trackers to JIRA.
On this page:
Built-in importers
The JIRA Importers plugin, which is bundled with JIRA, allows you to import data from the importers listed below.
Note: Not all of these importers are available for JIRA OnDemand.
- Bitbucket
- Bugzilla
- FogBugz for Your Server
- FogBugz On Demand (SaaS)
- Mantis
- Pivotal Tracker (SaaS)
- Trac
- Redmine
- JSON (beta)
CSV importer
If you are migrating from a system for which JIRA does not provide a built-in importer, you may be able to import your data into JIRA via CSV format instead. Your system must be able to export your data into a CSV (comma-separated value) file. You can then import the CSV file into JIRA using JIRA's CSV importer:
There is also a workaround for importing comments.
Third-party import tools
Third-party tools created by Atlassian Experts are also available for the following:
HEAT
- HP Quality Center
- IBM ClearQuest
- IBM DOORS
- Microsoft Team Foundation Server
- Rally
- Redmine (now supported)
Remedy
- SeaPine
SILK Test
- Serena’s TeamTrack PVCS and Business Mashups
SalesForce issue tracking
StarTeam
Go2Group’s Migration scripts and Go2Group’s BBI (Base Branch Importer)
SugarCRM issue tracking
- VersionOne
Requests for non-supported importers
We are also tracking requests to add other systems to our built-in importers. We encourage users to vote and comment on the systems they are interested in:
Other non-supported methods
- Write a Jelly script that will import your data. JIRA ships with some Jelly tags that make operations like creating issues in JIRA easy.
- Create your own scripts to move issues into JIRA,some examples are: Importing data from Trac into JIRA; Migrating Trac to JIRA; and yet another Trac 2 JIRA import.
JIRA ships with an RPC plugin which enables limited remote access to JIRA. It is available through REST, SOAP and XML-RPC interfaces. We recommend using the REST interface when possible as it will be our primary focus in the future. The JIRA RPC Services page provides a starting point for all your remote procedure call needs. The full source of the plugin is available and you are free to modify and the extend the source. We'd also be happy to accept code contributions to the project, as Simon Mittag has done in the past. Check out the RPC Endpoint Plugin Module for more information.
- It is possible to use whatever tools you feel comfortable with, to import the data directly into JIRA's database. JIRA's database schema is described in XML format in the
WEB-INF/classes/entitydefs/entitymodel.xmlfile under the JIRA web application. When using this approach please take care to maintain database integrity. - Finally as a last resort our built-in importer can be extended to support other systems, there is a very limited starting guide for those interested in taking this avenue.
Other references
- Commercial migrations by Atlassian Experts. A number of partners (e.g. ServiceRocket, formerly Customware and others) have provided custom migrations from Remedy, TeamTrack, ClearQuest, GNATS and Bugzilla in the past.
- Ask for help on the JIRA Development Forum.
- ClearQuest Import Forums Discussion
- Migrating Unfuddle tickets to JIRA
- Comparison of JIRA with other issue trackers