Hello,
Use Case:
Questions:
Regards,
Verinder
Hi @Verinder Singh,
For cloud to cloud migration - as of today - you would still have to depend on import / export of your spaces from source to destination or a migration from cloud to server and then again from server to cloud to use the migration assistant in the process.
A good thing is that Confluence has a Jira macro repair feature built in. You can find it under Confluence Admin / Jira Macro repair. That tool will do some of the heavy lifting for you.
However, Jira macros are bi-directional. If you link Jira issues on a Confluence page, a link is also added to your Jira issues pointing back to the Confluence page. From my own experience, that link could not be fixed automatically, resulting in missing information in Jira and the linked issues not being displayed at the top of your Confluence pages.
It is very well possible that the migration process has evolved again in the meantime and that these issues are covered better. But I would recommend you anyway to reach out to Atlassian Migration Support before you plan your actual migration.
Apart from Jira links, you may also be facing issues with links to other pages. Some of these links must be fixed behind the scenes. Support can help you prepare for those changes and do some of the post-migration fixes for you as well.
Thanks that was helpful Walter! I am checking with Atlassian Migration support team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.