Documentation for JIRA 5.1.x. Documentation for other versions of JIRA is available too.

When migrating from another issue tracking application to JIRA, you may wish to take your data with you.

(info) Our main website highlights some top reasons why people migrate from other issue trackers to JIRA.

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.

1. Built-in importers

The JIRA Importers plugin, which is bundled with JIRA, allows you to import data from Bugzilla, FogBugz, Mantis, Pivotal Tracker, or Trac.

  • Bugzilla  

    Version 4.1 or later of the JIRA Importers Plugin is compatible with Bugzilla 2.20 to 4.0.2. Users of older Bugzilla versions will need to first upgrade the Bugzilla database tables to a supported version, using Bugzilla's checksetup.pl script. The JIRA Importers plugin requires your Bugzilla database to be MySQL or PostgreSQL.

     

  • FogBugz for Your Server  

    Version 4.2 or later of the JIRA Importers plugin is compatible with Fogbugz for Your Server versions 7.3.6 to 8.7.60. The JIRA Importers plugin requires that your FogBugz for Your Server database is MySQL, Microsoft SQL Server or Microsoft SQL Server Express.

     

  • FogBugz On Demand (SaaS)  

    Version 3.1 or later of the JIRA Importers Plugin is required.

     

  • Mantis  

    Version 4.2 or later of the JIRA Importers plugin is compatible with Mantis versions 1.1.8 to 1.2.8. The JIRA Importers plugin requires that your Mantis database is MySQL, PostgreSQL or Microsoft SQL Server. We have also received reports that the JIRA Importers plugin works with Oracle and DB2 databases. However, we have not tested this plugin against these databases.)

     

  • Pivotal Tracker (SaaS)  

    Version 2.5 or later of the JIRA Importers Plugin is required.

     

  • Trac  

    Version 2.6.1 or later of the JIRA Importers Plugin is compatible with Trac version 0.12.2.

     

On this page:

(warning) Some functionality described on this page is restricted in JIRA OnDemand.

2. 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.

3. Third-Party Import Tools

Third-party tools created by Atlassian Experts are also available for the following:

4. 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:

5. Other Non-Supported Methods

There are also a few other non-supported options to get your data into JIRA:
  1. Write a Jelly script that will import your data. JIRA ships with some Jelly tags that make operations like creating issues in JIRA easy.
  2. 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.

  3. 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.

  4. 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.xml file under the JIRA web application. When using this approach please take care to maintain database integrity.
  5. 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

 



See our Getting Help page for details.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.