Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Are story points moved when migrating from nexgen to classic?

I understand that nexgen JIRA a uses Story Point Estimate field. If I move all my issues to a new classic project, will the story point values move?  I read another post on Two Story Points fields causing issues such that there is a Story Point (classic) and then a Story Point Estimate (nextgen) field. I'm not sure if I migrate all my issues via 'bulk move'  from nextgen to classic jira they will move over. Has anyone tried this?

When I look at a Classic Project, the field is also labeled Story Point Estimate so I was unsure. 

Thank you,


2 answers

1 accepted

0 votes
Answer accepted
Kevin Bui Atlassian Team Mar 05, 2019

Hi @Pam Heishman - As per, your story point estimates will be lost if you migrate your issues from next-gen to classic using bulk move.

You're right in that behind-the-scenes, the fields that handle story point estimates for classic and next-gen are different, and this means that the information doesn't transfer over when you bulk move the issues.

Hope that helps!

I appreciate such a quick reply. The link you referenced doesn't explicitly mention what will or won't be migrated. Are story points the only thing I won't have? (e.g. I'll have the sprint and issues relationships and other standard fields) 

I guess I need to do an export of the issues so I have a .csv to reference to manually add in the story points, unless there's a better way. 

I think exporting and importing wouldn't give me comments and maybe a few other things.



I also found that you lose the Epic names when migrating from NextGen to Classic.  I had to manually add those back in.

Has this issue been fixed?  If not when will it be?  I'd like to move tickets from a Classic Project to a Next-Gen Project, but losing all of the story points is painful.  

Like Umair Khalid likes this

For anyone that's getting here:


If you are migrating from NextGen to classic and want to keep the story points, please see the following steps:

1. Make sure your classic project has the "Story point estimate" field enabled, otherwise you will lose the data.

2. In your workflow, add a transition from "To Do" (or whatever status you end up having) to itself called "Migrate", and add a post function: copy the field value of "Story point estimate" to "Story points".

3. Bulk move the stories from NextGen to classic.

4. Bulk transition the stories with the transition you created in step 2.

5. Delete the transition (you don't want to keep it around).

Suggest an answer

Log in or Sign up to answer
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

75 views 0 4
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