Move Task types from a "Team managed" to "Company managed" Project?
Asked by Daniel Pfeffer:

Hello out there

When I move **Issues** from a Jira project of the type "Team managed software project" to a project of the type "Company managed software project", information from the issues **is lost** because the issue types in the "Team managed" project are not available in the new project.

Is it also possible to **transfer the task types** used to the "Software project managed by the company".

If so, how?

I look forward to advice from the community.

Best regards

Daniel


Answers:
author: Dave Mathijs
body: Hello [@Daniel Pfeffer](/t5/user/viewprofilepage/user-id/4812153)

That is behavior "by design" unfortunately and one of the many reason I don't recommend using team-managed projects as specific configuration is not "shared" across the platform.

Things to keep in mind if you migrate from team-managed to company-managed {#toc-hId--351490741}
------------------------------------------------------------------------------------------------

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](https://support.atlassian.com/jira-cloud-administration/docs/work-with-issue-workflows/).

* **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.

* **Issue types:** If you added your own issue types to your team-managed project, you'll need to have a Jira admin recreate these using an issue type scheme that they associate to your new company-managed project. [Learn more](https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type-scheme/).

* **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](https://support.atlassian.com/jira-cloud-administration/docs/manage-users-groups-permissions-and-roles-in-jira-cloud/).

* **Project and issue keys:** Jira will automatically update the issue keys of migrated issues to reflect their new project. Any existing links to old issue keys will be automatically redirected.

* **Reports:**Reports data won't be saved. Even though your issues 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**).

comments: author: Daniel Pfeffer
body: Hello [@Dave Mathijs](/t5/user/viewprofilepage/user-id/2662590)

Thank you very much for this comprehensive answer.

I suspected it would be like this, but I was hoping there might be a trick after all.

We also only work with "company managed" projects, but we still have a few "sins" from before.


Tags: cloud

jira-cloud