Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,557,844
Community Members
 
Community Events
184
Community Groups

Change a jira project from team managed to company managed

Aman Singh
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 22, 2023

I have a problem raised by a user, who wanted to change his Jira Project from team-managed to company-managed. I went through the document and learned that I have to create a new company-managed project and move all the issues from the team-managed project to the company-managed one by one which seems a very time-consuming task.
Can someone please help me if any other solution is available to change the project type?

 

Thanks in advance.

AMAN SINGH

1 answer

2 votes
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 22, 2023

Hi @Aman Singh and welcome to the community!

Unfortunately, this is true.  Team-Managed and Company-Managed are designed to be vastly different under the hood because the former is designed to be sort of sandboxed while the latter is designed to be centrally managed.

Further complicating matters is that when you migrate, it's rare that you can simply "move" the issues from team to company because any custom fields created do not map to their company managed counterpart.  So, depending upon how much customization went into the original project, you could have a few steps to perform:

  1. Export all of the Team Managed issues to csv
  2. Move all of the Team Managed issues to the new company managed project (This will preserve system fields like summary, Description, status, comments, etc.)
  3. Set up the company managed project to include any custom fields that were lost in the move
  4. Export the migrated content to csv and merge with the csv that was created in step 1 so that the data matches the new key
  5. Perform a System Import on the updated csv from step 3 mapping the custom fields accordingly to the new company managed custom fields
Paul Wiggers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

Luckily, this is not completely true. Please see this article: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

However, since team-managed projects are highly customizable, you need to consider the differences and how to handle those. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events