Issue migration

[lad6bp]

Hi,

we recently moved from the old JIRA to JIRA cloud so I have to set up the projects on the new as well. I already added the people but I'd also like to copy all the issues with all the details. Is there a way for me to do so?

Thanks in advance.

[Vikrant Yadav]

Hi @lad6bp  Welcome to Atlassian Community!

Are you trying to move project issues from Old Jira( DC/Server) to Jira cloud ? 

If yes, with the help of Cloud migration assistant, you can easily migrate a single project to Jira cloud. 

https://support.atlassian.com/migration/docs/use-the-jira-cloud-migration-assistant-to-migrate/

OR you can import issues in Bulk in Jira cloud via CSV file using External System import feature

[lad6bp]

Hi Vikrant!

Thank you for your fast answer! I'm trying to move issues from old JIRA to Cloud.

Can I still import the issues like CSV files with the external assistant or the migration assistant is the only way?

[Vikrant Yadav]

@lad6bp  As suggested by @OpsHub - Enterprise class Integration and Migration Solutions for Jira  I suggest you to use Cloud Migration Assistant . For migrating old jira to cloud jira. 

Via CSV you can only issues in a project and rest other data won't migrate like boards, filter etc.. 

[OpsHub - Enterprise class Integration and Migration Solutions for Jira]

Hi @lad6bp,

Yes, you can definitely migrate your issues from the old Jira to your new Jira Cloud instance. Migrating in chunks in one of the migration best practices. But it’s important to plan carefully. To decide the right approach, here are a few things to consider:

• Are Jira DC and Cloud using the same field templates?
• Do you need to migrate everything, or just specific data?
• How much downtime can your team afford?

Here’s how you can navigate these factors:

Jira Cloud Migration Assistant (JCMA)

• If downtime is acceptable and your field templates match, you can explore Atlassian’s official tool for migrating users, projects, and issues to the cloud. It works well for simpler migrations but does require a pause in operations till the migration is completed.
• Supported versions: JCMA works with Jira Server/Data Center versions 7.6 and above.
  If your current Jira version is older than 7.6, you’d need to first upgrade to a supported version before using JCMA.
• CSV Export/Import: This method involves exporting your issues from the old Jira as a CSV file and then importing them into Jira Cloud. It's relatively simple, but does require downtime and has limitations, especially around preserving relationships, history, and attachments.
• Enterprise-Grade Migration: OpsHub Migration Manager (OMM)

If downtime isn’t an option or you’re dealing with different field templates between Jira DC and Cloud, working with an Atlassian Solution Partner like OpsHub could be a great fit.

It’s zero downtime, zero disruption (live++) migration approach allows you to keep working on both systems without any disruption, and they can handle complex scenarios like data transformations or compliance needs

Key benefits:

• No downtime and no data loss
• Supports Jira versions 5.x through 10.x
• Migrates custom/system issue types, sprints, work logs, attachments, and more along with history
• Only requirement: A dedicated Jira Server user to initiate the process.

Feel free to get in touch.

Hope this helps!