How do I maintain custom fields in a migration from a project to another?

[evniki.constantinou]

I am trying to migrate issues from a team-managed scrum project to a company-managed scrum project.

I have set up the same workflows, same issue structure with custom fields, and I added the users to the destination project as well.

When I am trying to move the issues through, my custom fields get lost, even though I have the same ones in both projects. As an example, I have a custom field called 'Acceptance Criteria' in my stories, which gets lost after I move the story issue from the team-managed project to the company managed project. 

Any idea how to move the custom fields as well?

[Walter Buggenhout · Accepted solution]

Hi @evniki.constantinou and welcome to the Community!

As described in this support article, you will need to "re-create the data" in your custom fields.

Depending on how diverse that data is/was in your team managed project before the migration, you have a couple of options. No matter what option you choose, you might want to export your data to csv before you start, so at least you know what was in those custom fields.

Then, after moving the issues to your company managed project, you could:

• manually update all issues (which only makes sense if there's not too many to be addressed)
• use bulk update to edit the custom fields of all issues that had the same value before the move.
• or use csv import to update your custom fields from your exported file. For that to work, you'll need to match the old issue keys of your issues with the new ones after the move. For more instructions on csv import, see this support article.

Hope this helps!  

[evniki.constantinou]

Hi Walter, thank you very much for your prompt response. I thought so, I'll have a look at the article that explains how to match the old issue keys of my issues with the new ones, and follow the instructions.