You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are in process of migrating from "Next Gen" Projects to classic project in JIRA cloud. This is being done because want to migrate to Data Centre and cannot have any "Next Gen" Projects in existance for this to be under taken. Currently if we were to just move the "next Gen" project to "Classic" project all of the custom fields that have been set up are lost. We would like to retain this information and rather than a heavy manual data entry task it has been deemed acceptable if we could convert those custom fields into the single native labels field.
Is this possible or is there a better way to retain this information?
Hello @Darren Fairweather
Welcome to the Atlassian Community!
I believe the best way to transition your issues from a Next-gen to a Classic board keeping the custom fields would be by exporting and importing the next-gen issues to a Classic project using CSV format. These would be the steps:
Let us know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.