Migrating project from Jira Service Management to Jira Software

[Maristella Botsi]

We have a project in Jira Service Management under which there are about 12000 issues.

These issues contain attachments, links, internal notes, attachments + links in internal notes, as well as around 10 custom fields we have created. 

We would like to migrate the whole project (all issues) to Jira Software instance without losing any information we have. 

Please advice the best way to do so if possible and the problems we may confront.
Which solution could work? Export/Import .xml? or with backup and restore backup?

[Alexis Robert]

Hi @Maristella Botsi , 

if this is on a the same Jira Cloud instance, then you have a few options : 

• export the issues in CSV then re-import them in the new Jira Software project
• use the move issue feature to change the destination project
• use an app like Deep Clone to copy the issues to your new project

I would suggest trying each of these on a small set of issues to test which one is best suited to your needs.

Let me know if this helps, 

--Alexis

[Maristella Botsi]

Yes, the case described is on a the same Jira Cloud instance.

We've tried the export/import possibility but we've noticed unstable behaviors, e.g. with internal notes (sometimes they are migrated, sometimes not), issues with usernames and links, etc. So we've started investigating other way to do the migration.

That is why we would like to clearly know if using a backup / restore backup is not an option in this case, so as not to spend more time investigating this. 

Also we've checked the "Move" possibility. Move would work ideally if only we could find a way to store somehow (and be able to use as reference) the old issue key, since move the issue and keep the same issue key in new project is not possible even if the issue key has not been used in the new project. Is there any way we could do this in the new project? To be able to store somewhere the old issue key?

[Lisa Grau]

Hi Maristella,

you can copy the old issue key into a custom field and then move the issues to the new project. You cannot keep the old key in the new project as the "main" issue key.

[Maristella Botsi]

Thanks for the prompt replies.

Could you please provide with instructions on how to copy the old issue key into a custom field for all issues in the project? 

[Lisa Grau]

You can create an automation rule for that purpose.

Use the scheduling trigger and the "Edit Issue"-action. Set the smart value {{issue.key}} as the new value and wait for it to execute. That should do the job!

[StephanieC]

Do the same instructions apply if both apps are on Server or Data Center? 

[Jacek Wizmur _getint_io_]

Hi @Maristella Botsi ,

It's been a while since you posted this question - but we know that plenty of other people have similar issue. 

As Getint, Atlassian Gold Vendor we have a solution in a form of an app:

https://marketplace.atlassian.com/apps/1223930/jira-jira-issue-sync-2-way-integration-migration-new-app?hosting=cloud&tab=overview

It can be used to migrate the data with statuses, comments, attachments, regular and custom fields. What's important, it's not a CSV import/export which is outdated from the moment you do the export. You can migrate the data and keep the instances in a live sync.

best,

Jacek

[Marlene Kegel - codefortynine]

Hi @Maristella Botsi,

I am the product manager of Deep Clone for Jira.

Here some benefits if you plan to use our app for project migration:

• The original issues with original keys remain in the instance. So there's no risk to loose any data.
• You have flexibility to decide which field you want to clone and which not.
• It is possible to create a link between the clone and the original issue.

You can read more about migrating projects with Deep Clone for Jira in our documentation.

If you have further questions or feedback, don't hesitate to contact  us.