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
I have been going to the Atlassian Summit for a few years now but this year was a new experience - attending as a presenter. While I think that experience is likely worthy of it's own article, I wanted to share some of the information and help tips that I gathered together for any of those Jira admins that hope to consolidate Jira projects on a single instance.
Migrating Jira data can run the gambit of extremely easy to months and months of the exact opposite depending on what data is being migrated, the amount of data, and what you might be willing to let go of and recreate.
And as important as the technical approach is to migrating the data, it is equally important to do as much up front planning as you can.
As silly as it may seem, every one of our migrations is taken through the same process to help with consistency and documentation collateral for others to review.
The focus for the presentation was on merging data onto a single instance and the hoops that you might need to jump through. Half the presentation covers the importance of planning and the types of questions worth asking. And the second half hits on technical tips and tricks of modifying the metadata and Jira data to fit it in on an existing Jira instance without taking a wrecking ball to make room.
If you are interested to hear more please check out the summit recording.
One of my main goals was to avoid leaving people saying "That sound great, but I don't know where to get started". There is an open Bitbucket Repo of resources at this link.
This includes several resources: