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

Question

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.

Dr_ Ankita Mehta-OpsHub_ Inc · Answer

Hi @Désiré Dadie

This issue is because story points are handled differently in Company-managed and Team-managed projects as already stated in one of the above responses

A few additional things you may want to keep in mind:

* Field independence: Team-managed projects create their own fields, so global fields like story points won’t map directly
* Pre-migration prep: Copying values into a helper numeric field is the safest way to avoid data loss
* Estimation setup: Make sure estimation is enabled in the target project before trying to repopulate values
* Validation step: Always test with a subset to confirm values carry over correctly before full migration
* Manual effort tradeoff: Native approaches usually mean post-migration cleanup or reconfiguration

If you’re trying to avoid these kinds of workarounds, tools like OpsHub Migration Manager can be considered. It supports phased or full migrations with no downtime or disruption, preserves complete history (comments, attachments, relationships), and manages field mappings more reliably across project types.

All the best!

Arkadiusz Wroblewski · Answer

@Tomislav Tobijas

That's also great idea 💡 😁

Tomislav Tobijas · Answer

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