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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
On the project, we have Portfolio, Jira Cloud and Confluence Cloud. Soon, we will need to migrate all the data on a new Jira Cloud owning by our client. Is there anything in particuliar to look for when migrating the Portfolio app?
Migrating cloud to cloud, the portfolio data should come through without issue, you will want to follow the "Migrating from one Cloud instance to another Cloud instance" guide using a Site backup method, and importing to the new cloud site with the portfolio application in place, and you should be good to go once migrated over.
However there is a issue with migrating next-gen project types currently, and as Portfolio is not compatible with Next-Gen project types you should not have any next-gen projects tied to the Portfolio plans unless you are ok with the limitations covered in "Portfolio for Jira next-gen support" so the only limitation to look out for currently is if there is any next-gen project data coming over in the migration, covered in the XML migration document "Exporting issues" :
Currently, exports that include next-gen software projects won't include any epic link or other relationship data between epics and their children issues. This is a known error and we're working to fix it. Thanks for your patience.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.