Export Next Gen to a different Jira instance

[Klaus Hammer]

Hello,

see if someone can help here... 

• We want to move about 500 open issues from one Jira instance to another.
• About 20-30% of these issues have images attached.
• Product: Next Gen

moving from instance as in

• From: https://instanceold.atlassian.net/
  
  To: https://instancenew.atlassian.net/

yes, we can export these 500 issues, and import via CSV. But, we will lose the images.

Ideas we had...

1. Is there a way to create  backup, and import. backup file i.e.?
2. I heard of this Add on, but seems quite costly... https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira?hosting=server&tab=overview 

Anything else you can think of?

Thanks in advance for any input! cheers, Klaus

[Klaus Hammer]

thank you for your input so far. but in the end we went with CSV export/import, and manually adding what was missing. 500 tickets, 6 hours total.

why didn1t I try one of the options here? Kaghitalas seems tricky and time-consuming, and I was unsure if this would work.

Nics option, well, simply for security reasons. I can not use a third party tool, where the third party then potentially has access to our tickets (sensitive info).

But, again, thank you for your time to answer, Nic and Kaghitala! :) 

here an answer from Atlassian

WiII <atlassian-support@am.atlassian.com>	Fri, Feb 26, 10:15 AM (5 days ago)
to me

WiII commented:

Hi Klaus,

Thank you for reaching out!

Migrating projects between Atlassian Cloud sites is not currently supported for Jira. However, we understand it is a common challenge. We are actively working to fix it and we recommend watching and voting on the 'Provide support for "Single Project" imports between Jira Cloud sites' feature request to stay updated.

My recommendation is to use the workaround outlined below or, if you have the time, wait for the feature to be released:
Using the Jira Cloud Migration Assistant on Server: This approach calls for the source site(s) to be brought down to a temporary Jira Server instance. You can then use JCMA to merge into the destination cloud site. Please note that there are some limitations as cloud users will have some downtime, there could be post-migration issues with add-ons since app data typically does not migrate, and you'll need some experience setting up and managing a self-hosted instance.

If you do choose to do this, keep in mind there would be an additional step because they are next gen projects, which do not exist on Jira Server. You would need to migrate between next-gen and classic projects first and then flip back to next gen projects after the migration. If you would like to wait a little bit longer, the Jira Software cloud to cloud migrations EAP begins in April and you can fill out the form on the linked page to get involved.

Please take a look and let me know if you have any questions!

Cheers,

Will
Cloud Migrations Manager

[Nic Brough -Adaptavist-]

I'm going to have to go with a blatant advert for Adaptavist stuff - https://pc.adaptavist.com/ should be worth a look for you.  Yes, we're going to charge for it (I think) in the long run, but it is free for now.

I would like you to try it out, if nothing else to give us feedback on what it can and cannot do - the more real-world use-cases we have, the better for developing it!

[KAGITHALA BABU ANVESH]

Hello @Klaus Hammer ,

In this link there is a workaround for attachments uploading with csv.

Me did not tried this. Please create a test project and try this.

https://confluence.atlassian.com/jirakb/importing-attachments-into-jira-cloud-applications-using-csv-files-779160784.html 

Thanks,

Anvesh