Hi
We run a Confluence installtion on a local virtual server and are planing to migrate to Confluence Cloud. In fact we already did a test migration but are missing some old information
The user information (e.g. posted or created from) on articles/pages from former employees does not exist anymore, are vanished and replaced with 'unknown' editor marks.
But this information is nesessary for the history.
How can this be solved that Confluence entries still posess this kind of references?
Thank you in advance
rgds,
@DevOps Welcome to the Atlassian community
Are the accounts that are coming over as unknown disabled or do they no longer exist in your instance? How are you managing users on your server instance?
Hi Brant
The accounts still exist but do not have a license assigned to them.
Users are imported from Windows Active Directory via LDAP (group).
rgds, Sandro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@DevOps It will only bring over the active users. Would you be able to activate them and then migrate and then deactivate them? Do you need them for historical purposes?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Brant Schroeder - We don't have enough licenses at the current Confluence to license former employees again. And yes we need them for historical purposes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Brant Schroeder - we did some test migrations. Content and user with email addresses were transferred/created on the Confluence Cloud instance. But all articles had the note that they where created from an unknown user.
For historical purposes (to know how imported the article still is) we need to know who created or edited it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@DevOps I would suggest submitting a support request to Atlassian to see if there is a workaround that they could provide to get the information migrated properly. If you are migrating the users and they are not displaying because they are disabled I think they should be able to help you out. Please post the solution here for others.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Brant Schroeder - thank you! As suggested I will contact Atlassian support and if we come to a solutin post it here.
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.