why is migration from Team managed projects to Company managed projects impossible?

[Efe Obaseki]

why is it difficult to migrate from a Team managed project into a Company managed projects? is it because of the complex configurations in Company managed projects and Jira admin permissions?

[John Funk · Accepted solution]

Hi Efe - It's not impossible, but not a fun task. That's why I never suggest anyone create a Team-managed project. 

[Efe Obaseki]

Thanks for the prompt response Mr. Funk. However, I shall be chuffed if an in-depth explanation is given on how this migration is possible and the attendant  issues or difficulty one would encounter in migrating from the Team managed projects to Company managed projects and vice versa?

---

[John Funk]

The main thing is to set up your Company-managed (CM) project in advance. Create and add Custom fields with the exact same names (including case) as in your Team-managed (TM) project (if they don't already exist). Same with the workflow(s) and issue types, versions, etc. 

Then do a move function from move an issue or two to test it out. 

Here is a handy guide to help. 

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

[Trudy Claspill]

Hello @Efe Obaseki 

In my opinion the difficulty is due to the difference in the underlying architecture of the projects and the variation in the functionality between the projects.

Company Managed project architecture is designed to let the projects share configurations elements. Multiple CM projects can use the same fields, screens, issue types, workflows, etc.

Those items are managed in central locations by Jira Administrators who can assess the impact to all the projects that use those items.

Team Managed projects are designed so that project administrators can customize their project without affecting other projects. These items can't be shared with other projects. As such these items are not all located in central management locations, but rather within each project. They also may not be stored/organized in the same manner in the database, because they don't need all the same attributes of the shareable items.

To migrate a TM project to a CM project each of those items has to have a corresponding shareable item. Since such shareable items are managed by Jira Admins, their involvement is required to ensure those items exist.

[Efe Obaseki]

its is due to the complex project configurations  and that Company managed projects need Jira admin permissions  and that it is not confirned to a small or contained space because Company managed projects can be used for multiple projects in a company wide projects.