Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Project Migration Jira

Hi all,


I am currently trying to migrate a project from an instance without Jira Software to an instance with Jira Software, and I encounter the following error :


The backup project 'xxxxx' requires custom field named 'Epic Color' with full key 'com.pyxis.greenhopper.jira:gh-epic-color'. In the current instance of Jira the plugin is at version '8.5.0-DAILY20190920183006', but this custom field was not installed in the backup data. You may want to create an XML backup with this version of the plugin installed.


I have this error with a lot of custom fields and I'm wondering, does this mean I need to have Jira Software on the instance that I export project from ?


Thank you in advance for your help !


1 answer

1 accepted

0 votes
Answer accepted
Brant Schroeder Community Leader Sep 21, 2021

@Eriau Welcome to the Atlassian Community.

It looks like you have an app on the instance you are trying to migrate from that is not on the new instance.  Thus when it tries to create a new custom field it cannot because that type does not exist.  Can you confirm that the apps on the two instances match?



It was indeed the problem so we went with .csv exports.


Thank you for your answer !

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events