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

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

1 vote
Answer accepted
Kevin Bui
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
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).

Joseph Rossi
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!
May 01, 2023

Wow! Thanks a ton Zheng Jin :)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events