User mgmt switch after Confluence+Jira migration to self-hosted

[Rupert Edwards]

We're using one instance of Confluence OnDemand w/o Jira. Is it possible to, after first spinning up a self-hosted Jira instance & then migrating Confluence to self-hosted, to then force Confluence to use Jira for user mgmt?

If not, is there any workaround to a Confluence OnDemand instance with a lot of data getting migrated to a self-hosted instance w/ external user mgmt? Thanks!

[HosseinA · Accepted solution]

Hi Todd,

Yes, it is possible. The step to do this is easy as explain here

[Rupert Edwards]

The link you provided helps, but it doesn't articulate if it's possible to adopt Jira for user mgmt after Confluence has been using its own user mgmt. When backing up Confluence, it backs up users as well as content - imports are destructive and you can't selectively import, so can you select Jira for user mgmt after Confluence has been setup & the backup imported?

Also, what happens to the users that are imported after mgmt is switched to Jira? Since the same users will essentially be duplicated in Jira and logins handled from there, can content ownership be changed to each new Jira user? I'm hoping the issue is more simple than I'm making it...