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
We planning to migrate Jira backlog from one cloud instance to another cloud instance but need to leave confluence to old cloud. There is reasoning behind this, but not going there in this question.
If we migrate issues to new cloud the links from Issues obviously works to old confluence if we have application link between them. but what happens to links from confluence pages to new Jira? What should be taken in consideration? Obviously they will break, but is there any easy way to keep them or bulk edit?
How about macros in Confluence. How should them be handled?
Hi @Jarmo Parviainen ,
Welcome to Alassian community!
As per my understanding, you want to migrate you data from old jira to new Jira and your old confluence will same. Now you are getting confuse, If you migrate the data then what happens to links from confluence pages and Macro.
As you know, we don't have the cloud db access, we can't do any operation work.
In the Migration, Atlassian team help us to repair the links and macro So After migration you just need to create a Migartion ticket to fix this and repair the old jira link to new jira link from the backend.
Please find the below document they have mentioned the solution
Accept the answer If it helps you😊.