We finally used the methods described in this article to move/migrate users from one directory to another:

https://confluence.atlassian.com/doc/reverting-from-crowd-or-jira-applications-to-internal-user-management-188086.html

I also urgently need this feature. My confluence has been installed for a long time. I used LDAP to synchronize users and groups. But recently we integrated Confluence and Jira. If you want to use Jira's users and groups, or users who directly synchronize AD, Confluence manages its own groups. Abandon LDAP completely, if we disable LDAP directly, many users and groups will be lost. Now I urgently need to transfer the LDAP group and user information to the Jira directory or AD directory or internal directory.

I also think that such a handy migration function for moving users between directories is more than necessary. The best reference example is JIRA where it has been implemented recently so the demand is there.

Many sites use JIRA & Confluence together and at a certain point of growth it makes sense to implement single-sign-on. I think most admins setup JIRA with "Internal Directory" and consider to move to a different authentication model sooner or later but then they already have several accounts created and need to move them in a seamless way.

Yes would be really great if you could just switch between the LDAP based directory types as it seems they are pretty much the same anyway in the database

e are using a DELEGATING (LDAP) directory at the moment, since the installation is a little older. Now we need to change the directory type to a LDAP directory, because we want to use the features for synchronizing users automatically and so on.

It would be really great to do this in a quite simple way instead of using "unsupported" workarounds.

We are unable to change our LDAP authentication directory as users loose their group memberships.
Please implement the feature JIRA has whereby a new LDAP directory can be added and then using the built in feature, the old LDAP directory can be mapped to the new.
This makes the process so much simpler.

Please Atlassian, make this possible for Confluence as you made this possible for Jira!!

We would need this feature as well urgently. Came across the scenario that one of my clients decided for Confluence as Wiki and against Jira (because of lack of extensive mail-handling support) as Helpdesk Solution. Now I have to recreate all Users/Groups again in Confluence.

Our Knowledge Base article, Migrating Users and Groups from JIRA or Crowd Directories to a Locally Managed Directroy may help some people who are encountering this problem.

Some thougths on this issue. Using some scripting techniques and the soap api, users can be extracted from confluence and stored in an ldap server or vice versa, however it seems that the password hash is not transferrable. Crowd has the ability to import users from Confluence ut only to an internal directory, using the Atlassian-SHA password encryption https://confluence.atlassian.com/display/CROWD/Importing+Users+from+Atlassian+Confluence.