Following Atlassian documentation for migration practices, I am trying to convert all the Nex-Gen Projects in Cloud to Classic Software Projects as I cannot import Next-Gen Projects to an on-prem instance.
Epic Name, Epic Link, and Next-Gen specific Fields appear to not be able to move from Next-Gen to Classic using the Bulk-Tool.
It seems since these Fields either do not apply to Next-Gen or apply only too Next-Gen, moving these issues with these data points into the global configuration will cause data loss no matter what I do.
Is it possible to export the Fields mentioned above accurately for Next-Gen Issues? If this could be possible along with Comment Bodies (all comments is very important), I could use our on-prem import tool to create these issues in the Target instance.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events