Can we move a project from team managed to company managed

[Mohammed Yousuff]

Can we move a project from team managed to company managed without loosing anything for an example every sprint should have the tickets and tickets should be linked with epics and should retain the original tickets nos, backlog should have the tickets. 

[Trudy Claspill]

Hello @Mohammed Yousuff 

Welcome to the community.

No you cannot move a project from Team Managed to Company Managed without losing some information.

To "move" between project types you have to create a new, empty project of the desired type and then use the Move Issue function to move all the issues.

Because you are changing projects types and they handle tracking of the Epic/Child relationship differently, you will lose the links between Epics and their child issues. You will have to manually re-link the child issues to their paren Epics.

When you move the issues to the Company Managed project they will no longer exist in the Team Managed project. Since the Scrum board for the Team Managed project is scoped to only the issues in the Team Managed project, you will not retain sprint information for moved issues.

You will have to create a new Scrum board for the new Company Managed project.

The ticket keys will change for issues that are moved to the new project because those are comprised of the Project Key and a sequential number within the project. Jira will keep track of the change of the ticket key, though, so if somebody has the original ticket key they can enter that in a search and Jira will automatically redirect to the new ticket key.

[Thomas Parish]

"You will have to manually re-link the child issues to their parent Epics."

This part can be done more easily with Bulk Change, and careful use of Labels.

1. Filter to all work items in one Epic
2. run Bulk Change to apply a Label, using the current Epic issue number (e.g. AB-123)
3. also add the same Label to the Epic
4. Move the work items to the new project, then move the Epic (creates them in numbered batches with the Epic 1 higher -- new work items will have higher numbers so you can see migrated vs new in each Epic)

5. Repeat that process for each Epic in the project until all work items migrated.

6. export a CSV that includes the Label column (e.g. AB-123 now ZY-987) -- this is now your work list
7. Filter work items with each Label (Epic)
8. Bulk change to update the Parent Link to the new Epic issue number.

It's still quite manual, but you only have to do that once for each Epic, not the number of work items. May be much faster.

I've done this successfully with <10 Epics and 50+ work items in each Epic.

You could probably justify scripting these steps, if you have a particularly large project.

[Pavel Junek]

Hi Mohammed,

You can see this Atlassian manual for move project types.

Pavel