We cannot use the Confluence Cloud Migration Assistant. However, we were able to successfully import a Data Center export to our Cloud instance. Unfortunately, users were not assigned correctly.
Does anyone have experience in patching the XML export? As far as I can tell, there are data sets binding usernames to UUIDs, but only the UUID is used in the content data itself.
Hi @Frank Adler
I have experience from a few years ago with modifying the XML export. Unfortunately, it's a negative experience. It should be possible, but the export I was trying to update was too large to fit in memory for any XML parser I tried. Also, the XML wasn't always valid, and didn't encode certain entities correctly. If memory serves, it was some Unicode characters, but this was some time ago.
It's a shame you can't use the cloud migration assistant, which solves many of the problems that we struggled with during an XML migration.
Thanks for sharing your experience. Memory should not be an issue in my case as the space is only a few GB of size. My approach would be to just search/replace some parts using regex.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Frank Adler
Check the below suggesstion from Atlassian KB article
See Importing a Confluence Space for notes on restrictions when importing a space to Confluence Cloud.
Taking this export to Confluence Data Center? For best results, we recommend:
asking a Site Admin to perform the export, so that email addresses are always included, regardless of the user's profile visibility settings.
importing the space into Confluence 6.15.4 and later, or selected Enterprise Release versions, so that email address matching is available.
This will avoid content being attributed to ‘unknown user’ after the import. Learn more
Your organization may choose to prevent people from exporting data in particular product instances or with certain classification levels.
If you're migrating from Confluence Server to Confluence Cloud, you can use the Use Confluence Cloud Migration Assistant to migrate (legacy) to migrate your content and spaces.
More Reference Docs for your support
https://confluence.atlassian.com/confkb/xml-backups-and-space-export-import-troubleshooting-180294700.html
https://support.atlassian.com/confluence-cloud/docs/import-a-confluence-cloud-space/
Thanks
Jayesh R
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, but neither of the suggestions fits my case to migrate from Data Center to Cloud *without* CCMA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems I could solve this issue by replacing the User's UUID with the Cloud UUIDs. XML parsing was not necessary, so memory was not an issue.
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.