Problem Definition

At the moment, using the bulk change feature to move issues to team-managed (formerly next-gen) project. When a similar custom field with the same name exist on the Issue type custom field there's a prompt for data update. Likewise, if the field doesn't exist, there will be no prompt for data update.
In the above scenarios the data on those fields are removed and needs to be added manually. If the fields exist (In the team-managed (formerly next-gen) project), the data is still removed and still needs to be entered manually. However these fields data are actually hidden, by using the search button view all issues and select the columns to add the field name, the data is still there but if altered prior to the move, then the data changes.

Suggested Solution

Add a feature that will automatically detect that those fields do not exist and prompt the user for a decision. If the fields that match exist, automatically match the fields to the team-managed (formerly next-gen) project retaining the data.

Why this is important

As the team-managed (formerly next-gen) project provides a Roadmap functionality, which tells a much larger part in Agile Project. it would be better if projects can be migrated successfully than going through the daunting task to re-creating projects from scratch and custom fields which is inefficient.

Workaround

To manually create a similar custom fields following the available custom fields in team-managed projects that mimics the same fields / have the same name on company-managed (formerly classic) project and manually update the data all over again on the team-managed (formerly next-gen) project or during the move. [last resort]