Transferring stories from JIRA server to JIRA cloud

[Dennis Lindenberg]

I am merging two organizations. One is using JIRA server, and the larger one, JIRA cloud. I want to migrate a set of epics/stories/bugs. Not an entire project.

I have created a project on the receiving side, and am willing to do whatever mapping is needed. The basic stuff of names and descriptions. This is backlog, so there is no work associated yet. I just don't want to do manual data entry for about 100 issues.

The XML export/import looks too complex, and I got stumped with the .csv (thus far). Any help would be appreciated.

[francis]

Have a look at Exalate.

It is an issue synchronisation tool supporting the synchronisation between agile projects.

The following movie shows how this would work between jira server projects, but the same applies between server/cloud, cloud/server and cloud/cloud

https://www.youtube.com/watch?v=U7dzYzwyL30&feature=youtu.be

Interested in a demo - feel free to book one on 
https://exalate-demo.youcanbook.me

Francis

[Dave Theodore [Coyote Creek Consulting]]

Sounds like doing a CSV import would be easiest. There is no easy way to get the comments, history or attachments from the Jira user interface, though.  If that's ok, you can create a Filter that finds the issues you want to migrate, configure the columns to display the fields you want to migrate and then "save to Excel" the Filter. You'll need to convert it to CSV.  My recommendation is to use Openoffice for your CSV manipulation. MS Excel imposes rules on CSV that are not part of the standard and also doesn't do an amazing job of escaping cells that contain the delimiter in the text.

Make sure you have a header on each column in the CSV. The import wizard will ask you to map each column to an object in Jira.  For select lists, Priority, users, etc, you will need to map each field value to the corresponding value in Jira. It's pretty straightforward and the wizard should complain in a meaningful way to help you sort out the problems.  I would recommend doing this in a development environment before doing it in production. If the destination is Cloud, do it in a test project before doing it in your real project.

[Dennis Lindenberg]

Hi Dave,

I have run with your answer, and I need another piece of the puzzle: The backlog is composed of Epics, Stories, and sub-stories. I need to preserve the relationships through the migration, but it appears that the receiving JIRA cloud re-numbers everything and the hierarchy gets lost. I can export the links, but they don't import. Do you have a method to keep the links intact?

Thanks,

Dennis