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

Moving tickets from classic to next gen project doesn't fill custom fields

We have occasion to move tickets from a classic project to a next gen project, but there is a custom field we added to the source and target issue types which doesn't fill. The field name is the same in both the projects. 

Is there a way to get custom fields to migrate between project types? 

1 answer

0 votes
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 28, 2019


The only way I found to migrate custom fields is to export all data from a next-gen project to a csv file, then create new custom fields and modify your csv file so that values in the custom fields in the next-gen project would be named as newly created custom field. Then you can upload the csv file to Jira. 

I would strongly advise you to try it first in a test environment.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events