You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
What is the best way to go about this?
Do all the custom fields within instance A have to live in instance B before import? Or do those fields get auto created?
Hi @Ben Weisman
Adding to what @Joseph Chung Yin mentioned. I can’t recommend anything else other than using an add-on like Configuration manager for Jira for the migration.
The process by hand is too error prone and will cost you way more time than the cost of using the app I mentioned.
Also this is one of the few ways to ensure you have the exact data post migration. Even Atlassian recommends using one of these apps for project migration see: https://confluence.atlassian.com/adminjiraserver/migrating-projects-to-another-jira-instance-1167739597.html
As for custom fields, you need to create them if you are not using an add-on to do it for you.
Happy 2023. Are you using any add-on to conduct the single project migration from one instance to another instance? If not, then it is my experiences that all custom fields used by the specific project (instance A) will need to be created first in instance B prior to the migration.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team