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.

(info) 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 Cloud.

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:

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

There are also a few other non-supported options to get your data into JIRA:
  • JIRA ships with an RPC plugin that enables limited remote access to JIRA. It is available through RESTSOAP 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. We'd also be happy to accept code contributions to the project, see 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.xml file 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

Was this helpful?

Thanks for your feedback!

46 Archived comments

  1. User avatar

    Bob Swift [Bob Swift Atlassian Add-ons]

    Another tool is the JIRA Command Line Interface. With a little SQL and scripting this can either do one time loads or continuous imports from other systems.

    23 Oct 2009
  2. User avatar

    Michael Vorburger

    FYI: At http://kenai.com/projects/issuezilla-to-jira/pages/Home we have a tool & instructions how to migrate from an IssueZilla / java.net project tracker.

    29 Oct 2009
  3. User avatar

    Anonymous

    has anyone done an integration with test track pro?

    21 Aug 2011
    1. User avatar

      Anonymous

      You might like to contact ClearVision, based in the UK. They do all kinds of integrations and if they do not have it, they certainly have the skills to create something. I found them on the Atlassian partners page.

      22 Aug 2011
  4. User avatar

    Anonymous

    ClearQuest users - Appreciate the new Jira importer makes importing easier however the new product Affinity from Clearvision makes moving from ClearQuest to Jira a whole lot easier and you waste allot less time as the product is tuned specifically for this migration. You might also like to know this product will soon allow ClearQuest and Jira users to synchronise tickets across any geographical distance.

    22 Aug 2011
  5. User avatar

    Anonymous

    An HP Quality Center importer would be HIGHLY useful.  I see many requests for it, but other than third-party sync tools and the CSV approach there's no seamless way to migrate from QC.

    05 Oct 2011
  6. User avatar

    Simon Tower [Atlassian]

    At the moment, the JIRA Importers Plugin does not retain the worklog history of an issue (E.G. when certain transitions or assignments took place). If you would like this feature included, please visit studio.atlassian.com and check out the JIRA Importers Plugin project to create/vote on feature requests.

    29 Dec 2011
  7. User avatar

    Anonymous

    I want to integrate Jira with Easit Case Management system. Easit Case Management system will provide xml files and i wish to import this xml file into Jira. Also after successful import when i update issues in Jira, the same should be reflected back in Easit Case Management system and Vice versa.

     

    Please suggest how this can be implemented in Jira

    07 Feb 2012
  8. User avatar

    Anonymous

    i need to migrate data from a took tracking called " Version one"  to JIRA , to switch from versionone to JIRA

    any help on an easy wat to how to migrate my data ?

    22 Mar 2012
    1. User avatar

      Anonymous

      Hi,

       Did you figure this out?

      I also need to migrate from Versionone to JIRA Agile.

      Thanks,

      Tina

      06 Dec 2013
      1. User avatar

        Susan Paulson

        I also am looking for information on how to migrate from VersionOne to JIRA Agile.

        10 Jan 2014
        1. User avatar

          Justin

          AppFusions has performed large VersionOne to JIRA migrations and would be happy to help you. info@appfusions.com to discuss more. 

          29 Nov 2014
  9. User avatar

    Stefan Broda

    For migrations from IBM Rational ClearQuest to JIRA, Atlassian just released a cookbook that guides evaluators through the prototype setup. It includes best practices on Proof-of-Concept planning and execution, data migration, production approval process and points to relevant add-ons and Experts that can help. 

    16 May 2012
  10. User avatar

    Rob Kearey

    Man, an RT3/RT4 importer would be grand. Finagling with CSV is clunky.

    09 Oct 2012
    1. User avatar

      Matt Doar (ServiceRocket)

      Agreed. The new json (beta) is better than CSV

      09 Oct 2012
  11. User avatar

    Anonymous

    Didn't see anything on this specific question: Is there a way to migrate or link an old instance of JIRA to a new instance of JIRA? We are upgrading to a newer version of JIRA and overhauling our work flows, and there is no clear path to get the old JIRA tickets into the new instance of JIRA.

    10 Oct 2012
    1. User avatar

      Boris Berenberg [Atlassian]

      You could export to Excel from your issue navigator, and then import via CSV? 

      Also, possibly do a project import?

      I think the best solution would simply be to import your entire old instance and then replace the workflows there. This way you would be loosing none of your historical data.

      10 Oct 2012
    1. User avatar

      Matt Doar (ServiceRocket)

      That sounds like a regular upgrade, probably using an XML backup. I would do the upgrade, then create a staging JIRA and change the workflows there. Then make the same changes in the new production JIRA.

      If you are actually splitting a JIRA instance then Restoring a Project from Backup is another place to start but assumes that both JIRA instances are the same version of JIRA.

      10 Oct 2012
  12. User avatar

    Anonymous

    Why is the onDemand JIRA not compatible with Bugzilla imports?

    11 Oct 2012
    1. User avatar

      Pawel Niewiadomski [Atlassian]

      If you'd like to have it supported please create a feature request at https://studio.atlassian.com/browse/JIM. We decided not to support it initially but if we see demand for it we may reconsider supporting it on OnDemand. OnDemand is a different environment than JIRA installed locally, the biggest issue is having a direct access to Bugzilla's database which is usually installed in a company behind a firewall. 

      12 Oct 2012
  13. User avatar

    Alexander Goehring

    another tool for the Third-party import tools list:
    For migrations from issue tracking system Scarab (http://scarab.tigris.org/) to JIRA we have written a scarab2jira java tool: https://bitbucket.org/elaxy/scarab-to-jira-migration-tool

    15 Apr 2013
  14. User avatar

    Anonymous

    Hi -

    I am trying to import issues (history, comments, attachments) in bulk from Collabnet Teamforge into my local JIRA instance. The only options appear to be by using CSV which is cumbersome. Alternatively using the REST is another option. 

    Has anyone perhaps built some scripts that could be reusable?

    Thanks,

    CTF User.

    10 May 2013
  15. User avatar

    Bob Swift [Bob Swift Atlassian Add-ons]

    JIRA Command Line Interface is an enabler for writing custom import scripts or to augment other approaches.

    10 May 2013
  16. User avatar

    Lisa Reilly

    Has anyone got experience moving from Zendesk to JIRA? We are interested in moving but don't want to lost comment history or attachments

    04 Sep 2013
    1. User avatar

      Matt Doar [ServiceRocket]

      ServiceRocket has a lot of experience migrating data into JIRA, and we're also Zendesk experts. We have a connector product for the two products that synchronizes data. The basic approach is to extract the data from Zendesk, modify it to the CSV or JSON format expected by JIRA, then use the appropriate standard JIRA importer.

      04 Sep 2013
  17. User avatar

    Lisa Reilly

    Hi Matt, I got in contact with ServiceRocket on the 4th... still waiting for some human interaction and a quote! 

    I want to maintain attachments so I am worried about using the CSV/JSON format to do the transition?

    06 Sep 2013
    1. User avatar

      Matt Doar [ServiceRocket]

      CSV and JSON support attachments, though I sometimes use a separate script to upload them to make it easier to run.

      31 Oct 2013
  18. User avatar

    Juliane Di Lascio

    Has anyone got experience moving from Kayako to JIRA? We are interested in moving but don't want to lost comment history or attachments

    31 Oct 2013
    1. User avatar

      Matt Doar [ServiceRocket]

      Not specifically Kayako but I see some useful looking libraries at http://wiki.kayako.com/display/DEV/REST+API+Libraries+and+SDKs that should allow a script to retrieve the data you want. I'd probably use the JIRA CSV Importer to import the data into JIRA, though maybe I'd tried the JSON (Beta) Importer

      31 Oct 2013
  19. User avatar

    Rose Cooper

    What about the migration from Web Help Desk (by solarwinds)?

    31 Jan 2014
  20. User avatar

    Pankaj Jaju

    We are evaluating Jira as our issue management system and would like to move all issues from the current issue tracker (TargetProces) to Jira. I don't see any plugin for TP to import the existing issues from TP. Can this be done without resorting to CSV import/export. We need to import everything from the existing issues - like images, attachements, etc.

    What is the most suitable method to do this?

    02 Apr 2014
    1. User avatar

      Matt Doar [ServiceRocket]

      The CSV importer is probably the easiest approach to take. Atlassian Experts can also help with the process too.

      02 Apr 2014
      1. User avatar

        Pankaj Jaju

        Thanks for the reply Matt.

        But CSV route would mean loosing all rich text formatting (like tables and images in issue details ), attachments. (sad)

        02 Apr 2014
        1. User avatar

          Matt Doar [ServiceRocket]

          In that case I would write a script that extracts the data from TargetProcess including the formatting, convert the content to the JIRA Wiki markup to preserve the tables, create a CSV file that includes references to attachments and then use the CSV importer

          02 Apr 2014
          1. User avatar

            Bartek Gatz

            In fact I'd recommend using JSON importer for that purpose. We are actually going to declare its official GA version pretty soon, but even the current Beta version is more powerful and gives better flexibility than CSV. The current documentation can be found here.

            02 Apr 2014
            1. User avatar

              Matt Doar [ServiceRocket]

              Glad to hear it's going to make it out of beta soon!

              02 Apr 2014
          1. User avatar

            Pankaj Jaju

            Eventually I went the CSV route and it worked for the most part. The import was good and useful.

            03 Jun 2014
  21. User avatar

    Julia Wester

    I would like to see a supported connector/migrator to ServiceNow, AtTask and BugHerd

    22 May 2014
    1. User avatar

      Przemyslaw Borkowski [Atlassian]

      Hello Julia,

      thank you very much for your imporvement requests, we are tracking new importer ideas under Epic:  JIM-1169 - Support additional external issue tracking systems Open . Make sure that you vote for your issue trackers.

      Unfortunately, we are not planning to implement any new importer in the near future, but we could change our priorities, if we see a lot of requests under any of the missing importers.

      15 Sep 2014
  22. User avatar

    Nkau Kgasane

    Hi

    Is it possible to import data from IBM RequisitePro

    10 Sep 2014
    1. User avatar

      Przemyslaw Borkowski [Atlassian]

      Hi Nkau,

      we don't have a dedicated importer for the IBM issue trackers. You can workaround it by exporting your issues to one of the supported open format such as CSV and JSON.

      15 Sep 2014
  23. User avatar

    kishor

    Hi,

      Is there any utility to migrate data from DevTrack to JIRA directly or any work around?

     

    Thanks,

    Kishor Singh

    27 Jan 2015
    1. User avatar

      Bartek Gatz

      Please see this response. Hopefully it is going to be helpful.

      Cheers,
      Bartek 

      27 Jan 2015
  24. User avatar

    Yoni Samlan

    https://github.com/TheLevelUp/unfuddle-jira-migration

    We've written an updated Unfuddle -> JIRA migration script that does a few extras over the 2010 script linked to currently, including attachments, epics, comments, and issue linking.

    22 May 2015
  25. User avatar

    Lisa Weiss

    Is their a way to export defects from JIRA to VersionOne?

    Lisa

    04 Jun 2015
Powered by Confluence and Scroll Viewport