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

Mike Slivka
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 28, 2019

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.
January 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