Why can't Story Points be mapped when migrating from a Company-managed project to a Team-managed pro

[Désiré Dadie]

Hello Atlassian Community,

I’m currently working on a migration and would appreciate some guidance from the community.

Context

We want to migrate two Company-managed projects into a single Team-managed project.
The objective is to allow our local teams to be more autonomous in configuring their fields within the Team-managed project.

Migration approach

Our plan is to migrate all issues from two Company-managed projects to the new Team-managed project.

Issue encountered

During our migration tests, we noticed that it is not possible to map the “Story Points” field (Company-managed) to the “Story points estimate” field (Team-managed).

As a result, Story Points are lost during the migration.

Question

• Is there a recommended way to map or preserve Story Points when migrating from Company-managed to Team-managed projects?

• Is there a best practice or workaround to ensure that all ticket information (especially Story Points) is preserved during this type of migration?

Any guidance or feedback would be greatly appreciated.

Thank you in advance for your help.

[Arkadiusz Wroblewski]

Hello and welcome @Désiré Dadie 

This happens because Story Points are not handled the same way in company-managed and team-managed projects.

During a company-managed → team-managed migration, Atlassian does not map global custom fields to the independent team-managed fields, and for story points estimation they explicitly state that this data will be lost.

In the target team-managed project, you need to enable Estimation again, which creates the team-managed estimation field there.

The practical workaround is to copy the Story Points into a separate Number field before migration, move the issues, enable Estimation in the target team-managed project, and then populate the new estimation field again from that helper field. 

Please take a look on following KB about migration between company and team-managed Projects:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/ 

[Tomislav Tobijas]

To chime in quickly here - I know a few of my colleagues have been struggling with this 2-3 weeks ago.

Anyway, there are a couple of relevant feature requests for improving this whole transfer experience:

• JRACLOUD-78620: Migration tool from company-managed (formerly classic) to team-managed (formerly next-gen) project and vice-versa 
• JRACLOUD-79147: Option to retain a value when moving an issue from a team-managed to company-managed project and vice versa 

What you could probably do (we did it the other way around) is export data to CSV and then re-import once you move items from CMS (company-managed space) to TMS. 👀

Again, just a thought - it would need to be tested if it's actually feasible.

Cheers,
Tobi

[Arkadiusz Wroblewski]

@Tomislav Tobijas 

That's also great idea 💡 😁