How do I rename a KEY Space name in Confluence so I can export and import into another cloud instanc

[Barry Freedman]

I am trying to import (merge) Spaces from one Cloud Confluence instance to another.  I have encountered an issue where there are Spaces in that use the same KEY identifiers.  I have tried editing the entries.xml and exportdescriptors file and even run the clean up tool for the entities file but, keep getting the: "com.atlassian.confluence.importexport.ImportExportException: Unable to complete import: Content is not allowed in prolog." error.  

Help would be most appreciated with this!

Thanks

[Alexey Matveev]

Hello,

Have a look at this ticket. It works for me:

https://jira.atlassian.com/browse/CONFSERVER-2085

[Barry Freedman]

I have and many other tickets.  I'm working with the cloud version and this doesn't work for me.  

Thanks for the effort though.  

Barry

[Jeremy Linkletter]

Hi Barry,

Did you ever happen to get a solution to this? I am having the same issue in cloud...export, edit entities and exportDescriptor file, then get the error, "com.atlassian.confluence.importexport.ImportExportException: Unable to complete import: Content is not allowed in prolog."

Anything you can share would be very helpful!

Jeremy

[Barry Freedman]

Short Answer is No.  

This is what I ended up doing (workaround):

1.  In Destination Space:

     a.  Created a new space with Same Name and Different Key

            EG: existing space named IT with Key of IT.  New space is IT with Key of ITSS

     b.  Did bulk move of pages to new space.  Very easy as it keeps all the internal links and metadata.  Just need to watch out for anything is in Draft/unpublished.

     c. Once all pages and attachments were moved, I exported the space (as a backup) and then deleted the space.  

Note:  I did need to have Atlassian re-index the back end as something did get hosed up and, with cloud, there is no database interface for use admins.  

2.  In Source space, I exported the spaces individually.

3.  Imported the spaces individually and verified content.

Note:  All "Links" in docs are hardcoded and not updated to reflect new space url.  EG.  Page with link to another space would not be updated with the migration as it doesn't see that as metadata....at least, that was my experience...

I did try all the other methods (editing the XML file but, there was always something that failed and it wasn't worth the time/effort compared to how many spaces I needed to migrate and the content in them...

Good luck...I"m now doing the Jira merge/migration and that's much more painful...