Custom fields migration from project managed by team to project managed by company

[Mohamed RASSO]

Hello,
I am a JIRA adminstartor and we have a migration project , what we are doing now is migrate "Project 1" which is managed by teams to a "Project 2 " managed by company.
I recreated the issuetypes, workflows, rules and custom fields .
When we created the same custome fields in project 2 we had a lot of problemes with rules execution in project 1 . We have contacted the support and they told us that having the same custom fields in 2 different project has created a confusion for JIRA and as a solution we decided to add ( _ ) at the and of the custom fields in project 2.
The probleme that we're having now is that when we try to migrate issues from project 1 to project 2 we get the message that all the custom fields values will be lost , so we want to know if there is a solution to do the custom fields migration without losing their values . We thought that we can delet (_) from project 2 so Jira recognize the same custom fields but we are affraid that we will have rules execution problemes which will be crucial for our company activities.

Best regards

[Walter Buggenhout _ACA IT_ · Accepted solution]

Hi @Mohamed RASSO and welcome to the Community,

That is unfortunate, indeed. Migrating from team managed to company managed projects:

• seems like the step you indeed should make for your use case;
• does mean loss of data in the process, as you can read in this support article 

You will need to re-create the data from your custom fields in your new project. So, as described in the referenced article:

• make sure you have all the necessary custom fields already available in your target project;
• export the data from your current project to csv (you may be able to use them to import your custom field data later on of at least use them for later reference)
• move your issues from the team-managed to the company managed project

Then, depending on the number of fields and the variety of data, either update your moved issues manually or through bulk change.

Or, if you could add the issue keys from the migrated issues to your csv file, you should be able to use it to import your custom field data into the new project based on those issue keys.

Hope this helps!

[Mohamed RASSO]

Hi @Walter Buggenhout _ACA IT_  thank you for your response 

I will take these steps and do it in my project and let you know if does work

Best regards