Best Practices for Migrating from Team-managed to Company-managed Projects in Jira Cloud

Question

Hi Community,

We are planning to migrate several Team-managed projects to Company-managed projects in Jira Cloud and would like to understand the recommended approach, key considerations, and any known limitations or pitfalls before proceeding.

Context:

We are consolidating projects for better governance and to align with SDLC standards. The current Team-managed projects have their own workflows, issue types, fields, and screens that need to be analyzed and possibly replicated in the target Company-managed setup.

Objectives:

Migrate existing issues from Team-managed to Company-managed projects.

Preserve key data such as comments, attachments, custom fields, and history (if possible).

Recreate or align workflows, fields, and screens used in Team-managed projects.

Looking for guidance on:

What are the recommended steps or tools for migrating issues between Team-managed → Company-managed projects?

Any limitations — e.g., fields or configurations that won’t transfer automatically?

How to best handle workflows and custom fields unique to Team-managed projects?

Tips for maintaining issue links, subtasks, and hierarchy (Epics, Stories, Tasks) after migration.

Any community scripts, marketplace apps, or manual strategies people have used successfully?

Any insights, step-by-step experiences, or caveats from others who have done this would be really appreciated

Dr_ Ankita Mehta-OpsHub_ Inc · Answer

Hi @Sudarsana G

Shifting from Team-managed to Company-managed projects can really help with consistency and governance, but there are a few details worth sorting out before you start. Here are a few things to consider:

* Fields and workflows: Team-managed projects use their own isolated configurations, so you’ll need to recreate or align them in your Company-managed schemes before migrating.
* Custom fields: List out all custom fields and see which ones can be standardized or merged, moving them as-is can create duplicates.
* Issue hierarchy: Epic–Story–Subtask structures usually move fine, but cross-project links or advanced hierarchies may need manual updates.
* Comments and attachments: These transfer with issues during a bulk move or via APIs but test a small batch first to confirm history is intact.
* Permissions and screens: Review these in advance as it’s easier to fix mismatches before migration than after.

In this case, you may explore OpsHub Migration Manager (OMM), an enterprise-grade migration platform. It supports phased or full migrations with no downtime, disruption, or data loss, and even provides reverse sync to capture any last-minute updates during cutover. It maintains high fidelity-including comments, attachments, relationships, and field mappings so your Team-managed data lands cleanly in Company-managed projects. As an Atlassian Silver Solution Partner, OMM has been used in large Jira Cloud consolidations like this to bring projects together without losing history or structure.

All the best!:)

Karan Sachdev · Answer

Hey @Sudarsana G

Welcome to Atlassian Community!

You may refer to this document for details on this:

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

Since there is a chance of some data loss, you may export all the work items before the migration (as a backup). In case some fields or data is missing, you can later reference the data to update the migrated work items.

Thanks!

Shalini Pradhan · Answer

Hello @Sudarsana G ,

Good day! Welcome to Atlassian Community :)

We have several pointers to keep in mind while moving issues from Team managed project to Company managed project. You can take a detailed look in this document: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

Thank you!