Migrate a team-managed project to existing company-managed project??

Emily Brol October 29, 2024

We are rolling an existing team-managed project into an existing company-managed project for visibility and I am having issues I cannot find answers to on other articles/questions. I have created a test CM project that mirrors the project i would like to migrate my tasks to. I also clone the TM tasks before moving them. I've tried several different methods to move/migrate tasks outlined below.

Bulk Move:

Status -> successful

Custom Fields -> all but 1 do not even give me an option to map to the custom field with the same naming/casing in the test CM project. I am planning to move hundreds of issues so manually updating 20 custom fields for hundreds of issues after moving them is not practical.

Export/Import:

Status -> moves everything to backlog. Even if i manually change the status name to match status options in the new project before importing.

Custom Fields -> some give me mapping options some don't. For the ones with no mapping option they are 1. a date field. 2. a short text field. 3. a dropdown menu picker field. Other instances of these field types migrate fine.

 

Is there a better way to do this? Not having/minimizing manual update steps post change is my top priority.

2 answers

0 votes
Luka Hummel - codefortynine
Atlassian Partner
October 31, 2024

Hi @Emily Brol and welcome to the community!

Migrating from a team-managed to a company-managed project in Jira can indeed be tricky, especially with custom fields. Since you've noted issues with bulk moving and importing, you might consider our app Deep Clone for Jira, which streamlines migrations with advanced cloning options. Deep Clone allows you to clone issues across projects, keeping custom fields, statuses, and other settings intact. This minimizes manual updates and supports bulk actions (up to 100,000 issues at once), making it easier to handle large-scale migrations effectively.

Emily Brol October 31, 2024

I use Deep clone alot however I am not able to bulk deep clone which would mean deep cloning each card/epic individually which is just as much work. is there a way to deep clone from a JQL query search? That way i could encompass all my tasks in one deep clone.

Luka Hummel - codefortynine
Atlassian Partner
November 3, 2024

Hi @Emily Brol

Your account might be missing the necessary permissions to perform a Bulk Clone. If you have the permissions, you can use the Bulk Clone feature to clone any JQL query, filter, or Jira project.

0 votes
Eric Sibomana
Contributor
October 29, 2024

Hi Emily, 

Here are some potential solutions

1. Prepare the Company-Managed Project

Before migration, ensure that your company-managed project is set up correctly:

  • Create all necessary custom fields in the company-managed project
  • Set up the correct issue type scheme
  • Configure the appropriate workflow scheme
  • Ensure the screen schemes are properly set up

2. Use Bulk Change with Advanced Options

Try using the Bulk Change feature with more advanced options:

  • Use JQL to select all issues from the team-managed project
  • In the Bulk Change wizard, select "Edit Issues"
  • Map as many fields as possible, including custom fields
  • For fields that can't be mapped, consider using the "Change Value" option to set a default value

3. Two-Step Migration Process

Consider a two-step migration process:

  1. First, use Bulk Move to transfer the issues, which should preserve the status
  2. Then, use Bulk Edit to update the custom fields that weren't transferred

4. Utilize Jira's REST API

For more complex migrations, you might need to use Jira's REST API:

  • Export issues from the team-managed project using the API
  • Transform the data as needed
  • Import the transformed data into the company-managed project

5. Third-Party Migration Tools

Consider using third-party Jira apps specifically designed for project migrations. These tools often provide more flexibility in mapping fields and statuses.

Additional Considerations

  • Backup: Always create a full backup of your Jira instance before attempting any large-scale migration
  • Test Run: Perform a test migration with a subset of issues to identify and resolve problems before the full migration
  • Custom Field Compatibility: Ensure that custom fields in the team-managed project have compatible counterparts in the company-managed project
  • Workflow Differences: Be aware that workflows in team-managed projects are simpler and may not directly map to company-managed workflows

Remember, there's no perfect one-size-fits-all solution for this type of migration. You may need to combine multiple approaches and potentially accept some manual work for certain aspects of the migration. I would like to hear which final approach will work for you.

Emily Brol October 31, 2024

I'm not sure you've understood my dilemma. I can't bulk edit all the custom fields because they have different values. Things like an additional assignable field are what I need to be able to copy over with hundreds of issues and a bulk edit wouldn't reassign the issues to the same QC reviewer. Doing this manually isn't an ideal option. So #1-3 i have tried and do not work for my project migration. 

I'm not familiar with how REST API would create less work than updating manually. I have been testing this migration for weeks and have not found a solution. I think this is just a stock answer and not an answer to my dilemma specifically.

Eric Sibomana
Contributor
October 31, 2024

Dear @Emily Brol ,

I apologize for the confusion in my previous response. Here are some potential solutions that might work for your situation:.

  1. Jira Cloud Migration Assistant:
    If you haven't tried this yet, Atlassian's official migration tool might be worth exploring:
    • Install the Jira Cloud Migration Assistant app
    • Use it to select your Team-Managed project as the source
    • Choose your Company-Managed project as the destination
    • Run a test migration to ensure all fields, including custom fields, are correctly transferred
    • If successful, perform the full migration
  2. REST API Script:
    For a more technical but potentially more controlled approach:
    • Use Jira's REST API to fetch all issues from the Team-Managed project
    • Create a script that takes this data and creates new issues in the Company-Managed project, preserving all field values
    • This method requires programming skills but offers the most flexibility
  3. Atlassian Marketplace Apps:
    There are several Jira apps designed for project migrations that might suit your needs. Some options to explore include:
    • Project Configurator for Jira
    • Jira Issues Sync
    • Structure for Jira


Best regards,

Eric

Suggest an answer

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

Atlassian Community Events