Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Copy ALL JIRA Cloud "Next Gen" Custom field values into labels field for ALL individual JIRA issues


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?

1 answer

1 accepted

0 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 07, 2020

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:

  1. Export your Next-gen issues by creating a query and using the option Export Excel CSV (All fields):
    Screen Shot 2020-10-07 at 20.59.32.png
  2. Edit the CSV file:
    1. Set the Custom field names as labels
    2. Change the project fields to the correct classic project
    3. Remove the Issuekey and Issue ID
    4. Check if workflow statuses or issuetypes must be changed (Mainly Subtasks, that must be changed to Sub-tasks)
  3. Import the CSV file to your site

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events