Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Best practice for old directories after migrating to Crowd

I recently implemented Crowd for JIRA, Confluence, and Fisheye/Crucible.  This involved moving three directories (2x LDAP and the internal directory) from each JIRA and Confluence into the same three directories in Crowd.  At this point I plan on deleting the old delegated LDAP authentication directories from JIRA and Confluence as the users coming from Crowd just naturally override the old users.

However, the internal directory is a more complicated issue as it cannot be deleted.  In JIRA, I can move the Internal directory higher than the Crowd directory and then delete the Internal directory users one by one (I plan on leaving an administrative account in case of emergencies).  This is not ideal by any means, but it works to clean up old data.

I cannot do the same in Confluence.  I moved the Internal directory higher than the Crowd directory, but I get errors deleting users "because he or she has authored content in one or more spaces".  This seems like an artificial error in this case because I was able to remove two whole directories full of users who have authored content and that content was simply mapped to the new user record from Crowd.

What have others done to clean up old data after migrating to Crowd?  I really don't want to leave old data sitting around as it only serves to complicate the solution.

1 answer

You really need to leave an admin user in JIRA and Confluence internal directory in case the link between Application and Crowd is not working.

You could move the Crowd directory in first position.
Run a query in database to indenty all users that are in internal and in Crowd directory and do nothing with these users.
And identity all users in internal and not in Crowd, should only stay the admin user account.


Yes, I planned on leaving at least one admin user in the JIRA and Confluence internal directories for recovery purposes.

However, doing nothing with the overlapping users doesn't resolve my original complaint that there is now a lot of duplicated data that only serves to complicate the current situation. This will only get worse over time as some accounts get disabled in Crowd but don't get changed in the no-longer-used internal directory.

It would be really nice if Atlassian had a whitepaper to cover the migration to Crowd that included some more complicated scenarios (e.g. moving multiple directories to crowd) and included what to do with the data that is no longer needed in JIRA and Confluence.

As far as resolving my issue with the extra internal users that are no longer needed, it seems like there are no options outside of fixing the data directly in the database.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

203 views 0 6
Join discussion

Community Events

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

Events near you