Linked issues are lost when migrating from Team-managed to Company-managed project

[Ashok Shembde]

While migrating issues from a Team-managed project to a Company-managed project, the issues were moved successfully; however, the links between parent and child issues (such as Epic → Task or Task → Sub-task) were not retained. As a result, the issue hierarchy and traceability have been disrupted in the target project.

[arielei]

Hey @Ashok Shembde 

according to their doc it should preserve the data:

Things to keep in mind if you migrate from team-managed to company-managed

Team-managed projects and company-managed projects are technically quite different. Here's a few things to consider when you migrate from a team-managed software project to a company-managed software project:

• Board statuses: If you customized your team-managed board, you'll need to set up the same statuses in your company-managed project's workflow. Only Jira admins can create and modify statuses and workflows. Learn more.

• Custom fields: If you use custom fields in your team-managed project, a Jira admin needs to recreate the fields and add them to screen schemes and field configurations in your company-managed project. Custom field data will need to be recreated, otherwise it will be lost.

• Work types: If you added your own work types to your team-managed project, you'll need to have a Jira admin recreate these using a work type scheme that they associate to your new company-managed project. Learn more.

• Project access: Access to company-managed projects is controlled by a permissions scheme. Only your Jira admin can update your company-managed project's permission scheme. Learn more.

• Project and work item keys: Jira will automatically update the work item keys of migrated work items to reflect their new project. Any existing links to old keys will be automatically redirected.

• Reports: Reports data won't be saved. Even though your work items will be retained, data for your project's Velocity and Burnup reports won't transfer over, and will be lost.

• Story points estimation: This data will be lost. This is because the custom field that Jira uses to store estimates in company-managed projects (Story points) is different to the custom field used in team-managed projects (Story point estimate).

[Staffan Redelius]

Hi @Ashok Shembde 

It has been a while since I did this but from my experience there is a risk of loosing the relationship if you bulk move of all issues in one go.. 

If you move the Epics (and included Task/Stories) individually it should work, 

Move issues from Team managed project to company managed project with Epic and child issues | Jira and Jira Service Management | Atlassian Support

This might be a bit late for you but if you find the answer helpful please mark it as accepted to help other users find it,

Best regards,
/Staffan