It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best way to migrate from HP ALM to JIRA


We are planning on bulk migration of multiple projects from HP ALM to JIRA. Would like to know if there are any ways to migrate the below data from ALM to JIRA:


Testcases(along with test execution status)


Linkage between the entities


Have anyone worked on such migration before, if so can you share the best way/process steps to do the same.

3 answers

0 votes
Dave Theodore [Coyote Creek Consulting] Community Leader Apr 11, 2017

We have done a few for various clients from HP QC and ALM (along with countless other issue trackers.)  If you're going in to native JIRA, you can get most of what you are looking for by using the CSV import method.  There are some things, like creating issue links, that can not currently be done with a CSV, though.  We typically use the REST API for that stuff.  Many test case management systems, such as Zephyr can import legacy test data too, in case you're thinking about going that route.  These type of migrations are pretty tedious, but the CSV importer works well.  The biggest thing that you will lose is the individual issue history. You can set things like the date that the issue was originally opened in HP ALM, but there is no way to set the date of a comment, for example, via CSV import.

Thanks Dave. You are right, we tried the CSV Import for Requirements and defects and Zephyr Import Utility for Tests, but were not able to carry forward the history and attachments. Is there any way to get the attachments into JIRA if not the history. Atleast that should help for now.

Is there a way to do these migration using the REST API. Any pointers on that will also be of great help.

Dave Theodore [Coyote Creek Consulting] Community Leader Apr 12, 2017

You can check out this article to see what the formatting looks like for the CSV. Essentially, you need to harvest the attachments and put them in some kind of structure where you can identify which attachment(s) go with each issue. Then you create a CSV that has une URL per column, per the above doc, for the attachments. You will need a column for the JIRA issue key and also the Summary (note: the summary will be changed if you don't use the "real" summary.) You can either merge the attachment CSV data with your issue field data or do two CSV imports. Doing 2 is probably easier. I hope that helps!

Mohammed Amine Community Leader Feb 13, 2019

Adding my 2 cents, as we are in 2019. Importing linked issues works with the CSV importer without any problem. Here is the link in Atlassian documentation.

Like Stephen Jansen likes this
0 votes
Ash Apr 19, 2017

We are in same situation  we are moving from ALM to JIRA server we are using Xray plugin for Test management still we are in testing phase hope we will find a answer, These likns may be helpfull to you. Migration-from-HP-ALM-to-Jira/qaq-p/462162


mohan reddy Jun 05, 2017

Hi Ashish,


Have you migrated the data from HP ALM to Jira Xray Test Plan data? If yes,Can you let me know how you did.Even we are planning to do.Please replay me or send me to the following emain id :






Ash Jun 07, 2017

Sure Mohan.

Sudheer Naik Jun 27, 2018

Hey Ash/Mohan,

Do we have the solution for the same? Were you able to migrate the data from HP ALM to JIRA (Xray)? 

0 votes
Marcel Nick Jul 12, 2017

Hi Prathiba ,

We offer a JIRA Cloud Plugin which allows co-relation of data between different test tools for analysis and reporting.

So you could have all your testing happening in HP ALM while defects continued to be reported in JIRA. You can continue to use use your favourite test tools  and have JIRA as a Defect/Story tracking tool.






Ash Jul 13, 2017

Is this only for reporting or we can pull data into Jira?.




Marcel Nick Jul 13, 2017

Yes Ashish. Use case is for reporting across test tools.  It's currently not possible to sync between tools using the plugin

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

1,066 views 13 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you