Our organization is slowly phasing out JIRA (we're still locally hosted on v6.4) and moving to another product, but we are keeping Confluence (also aged; v5.7.4). As part of this shift, we would like to move to the latest Confluence version (still running locally for now but with a possible shift to cloud in the future).
Currently, our JIRA is the "source of truth" for our user database. Confluence is using OAUTH against JIRA for its users. Users in JIRA are "local" users, not tied to LDAP or other user directories.
In some POC scenarios, I was able to successfully get our Confluence articles/data over to the new instance without any issue but this was when we were planning to keep and upgrade JIRA as well.
My goal is to set up a brand new, up-to-date Confluence server (no JIRA on it this time) and port over our content from the old Confluence server to the new one. Along with that, we want to break ties with JIRA from Confluence from a user perspective - but I would rather not lose the user data connected with Confluence (article authors, comments, etc).
Is it possible for me to "export" user data from old JIRA, bring it into NEW Confluence and have it seamlessly reconnect those now "local to Confluence" users to the articles and content previously authored by "local JIRA users" after we import the OLD Confluence data?
Kind of an esoteric request, I know. :) Appreciate anyone's thoughts and/or experiences in this endeavor.
@Shane Monroe, there are a couple of options you can handle this. Regarding export users from Jira and import them into the "new" Confluence, you can utilize apps to help you do the work (e.g., Confluence CLI, among others). Alternatively, you could do a backup site export/import and get Confluence upgraded to the target version if you need to retire the existing one. If you can keep your current installation, you can also migrate users from the Jira directory to the Confluence internal directory - you would need some database manipulation since it's a feature that it's still gathering interest with Atlassian (CONFSERVER-25630). Some options require additional work but less risky. It's essential to understand the pitfalls you may come across in each approach. I would advise going through the Atlassian documentation to understand what entails moving your spaces/sites between instances and, mainly, the type of problems you can get, such as duplicate users and how to fix/merge them. Perhaps, getting a better sense of the hurdles you might find helps you decide the approach to choose in light of your current migration expertise and experience.
You might have known that by now, but it's worth mentioning that Atlassian ended sales for new server licenses and will end support for server products on February 2, 2024. If you haven't done it yet, as you're now studying your move options, you can also consider beginning your Cloud journey if you feel ready.
Some related links that may help you to explore and learn more.
Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events