NextGen to Classic Migrations

[andy.pawl]

Hello...  Jira Cloud here.

I am working with a few folks on moving their issues over from NextGen to Classic Projects.

What I am wondering is if there are any work arounds to resolve the issues named in this link under 

Things to keep in mind if you migrate from next-gen to classic

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-next-gen-and-classic-projects/

Specifically - the links between Epics and Stories that are broken when moved to Classic.

Right now I am trying to determine resource and effort for these and just want to get a good idea if what Atlassian states cannot be done in the above link, actually cannot be done.

[John Funk]

Hi Andy,

I don't see anything in the document that list Epics and Stories as being a problem with migrated. Have you tried a single Epic and it's Stories to see what happens?

[Jack Brickey]

i haven't done this but since Epics in NG don't have Epic Link (or has this changed :-)), I would assume the following to be the right (?) approach....

1. Move the NG Epic and ensure it is clean and has the desired Epic Name. Actually, I might even consider creating a new Epic in Classic.
2. Move over your issues and use Bulk update to add Epic Link

[Walter Buggenhout]

And as an additional safety net: create a csv export of your issues with all custom fields before you start moving anything at all. That way you have a snapshot of your data before you move them as a reference for fixing anything that may go wrong or that you need to fix manually (such as the story point estimation).

[andy.pawl]

@JohnI put the wrong link in - in this link it mentions the issue of Epics and Links

https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-an-agility-project-to-a-classic-project-957974933.html

[Jack Brickey]

yep. that is precisely to the point i made...

Things to keep in mind if you migrate from next-gen to classic

<<<<<<<< SNIP >>>>>>>>

• Epics: Jira moves your epics across if you map them to an epic issue type in your new project. But, you'll lose the relationship between your epics and their child issues. The child issues themselves will sill exist, but the links between them won't.

[andy.pawl]

Yes so that's what I am asking in this case - is this 100% true or are there ways around this with potential 3rd party tools or maybe assistance from the vendor?

[John Funk]

Yes - you can do what Jack suggested above. 

[andy.pawl]

@John I put the wrong link in - in this link it mentions the issue of Epics and Links

https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-an-agility-project-to-a-classic-project-957974933.html