Issue with Field Values Not Migrating from TMP to CMP During Bulk Move

[Suresh Sakhare]

Hi Team,

I'm in the process of converting a Team-managed project (TMP) to a Company-managed project (CMP), following the guidelines provided in the documentation. As part of the process, I've already created the CMP along with the required workflows, fields, issue types, and other configurations. I'm now moving the work items from TMP to CMP using the Bulk Move option.

Problem:


During the move, the custom field values are not getting copied to the issues in the CMP. Even system fields like Description are appearing empty after the migration. Is anyone else facing a similar issue, or aware of a workaround?

Thanks in advance for your help!

Best regards,


Suresh

[Ankita Mehta]

Hi @Suresh Sakhare

Are you seeing empty fields like Description or custom values after bulk moving from a Team-managed to Company-managed project? If you are, it's not uncommon, and here are a few things to consider pinpointing the root cause:

• Fields might be missing from the CMP screen configuration. Even if the field exists, it won’t appear unless it’s added to the right screen.
• TMP fields are often project-scoped. If the field wasn’t created globally, the CMP won’t recognize it during migration.
• Some fields are linked to specific issue types. If the CMP uses different issue types or contexts, those fields may not be applied.
• The Bulk Move wizard doesn’t always flag unmapped fields. It may silently skip them, which can lead to missing data post-migration.

 If preserving field values, traceability, and context during Jira migrations is on your priority list, you may consider an enterprise - grade migration platform from OpsHub (an Atlassian Solutions Partner). It handles these nuances behind the scenes with zero downtime, non-disruption and high fidelity—no guesswork, no rework.

Drop us a line if you have questions or want to see a demo!:)

[Luka Hummel - codefortynine]

Hi @Suresh Sakhare

If you're frequently migrating data between projects and need a more reliable solution to avoid data loss or misalignment, our app Deep Clone for Jira might be exactly what you're looking for.

Deep Clone can seamlessly clone and migrate issues, including many fields and data that aren't supported natively by Jira's bulk operations, such as:

• Issue status: Statuses are cloned accurately as long as the status and transitions exist in the target workflow.

• Attachments, comments, and sprints: Comprehensive cloning of attachments, comments (with original timestamps), and even active or future sprints.
• Bulk cloning: Easily handle large-scale migrations with up to 100,000 issues in a single operation, ensuring smooth project transitions.

Moreover, Deep Clone provides detailed error logs, easy error handling, and extensive configuration options to ensure the migration meets your project's exact requirements.

[John Funk]

Hi Suresh - I have never had a problem like that. 

I just move over 700 issues from TMP to CMP over the weekend and didn't lose a thing. 

Do you get any error messages or anything that looks strange along the way, even when doing a single issue?