Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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


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
Community showcase
Published in Team-managed projects

An update on team-managed projects customer feedback – November 2021

Hi! My name is Eoin and I'm a product manager working on Team-managed projects in Jira Software Cloud. We're continuously improving and updating Jira Software and feedback from our customers is ...

1,377 views 0 8
Read article

Community Events

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

Events near you