You need to make sure the owner of the personal space has a user prior to importing the space. Otherwise you'll need to add permissions manually after the import.

Hello there,

"Importing personal spaces. It is a known issue that personal spaces will become global after being imported. The workaround is to create a new personal space and move the imported content to the new space."

This workaround is not working cause the error 'a space with key ~username already exists' keeps appearing when trying this workaround (see picture below)

At this moment we are in a transition phase of moving our confluence server version to a confluence cloud version. So exporting/importing personal spaces is a big issue for us.

Can you give me an update on this topic.

Greetings Peter

Atlassian Support,
Any word when this will get addressed? This is a real PITA, and it means that, for a period of time, personal information is exposed for everyone to see.

Importing from server ver 5.3 to Cloud, all personal spaces failed to import as personal spaces. This just became a manual task to complete. What happens if I try to create a personal space except that personal space key already exists?

Hi graeme.price

Thanks for getting in touch, unfortunately I don't have any update on this issue at present. There are a number of higher priority issues that we need to address before looking at problems such as this.

Out of interest would you be able to let me know which version of Confluence you are using, it will help us to track down the age, longevity and root cause of this issue.

Regards
Steve Haffenden
Confluence Bugmaster

Has there been any progress on this issue? For instances with a large number of users, the workaround is a non starter.
Thanks

we are having the same issue. my problem is thou when i click "Add Personal Space" the system just tries to create it in an infite loop. and nothing ever happens. the system basically just hangs as its "processing"

For those who still have this issue, since the personal space become global you can access it using this URL:
https://YourConfluenceUrl/wiki/display/~user.name (Replace YourConfluenceUrl by your URL and user.name by the personal space name)
Or by accessing the Global Space.

It won't fix the issue but at least you will be able to see the content.

Hope it helps,

Update
A better way to directly have the tree content is to use this URL:

https://YourConfluenceUrl/wiki/collector/pages.action?key=~user.name

Again, you will need to replace both "YourConfluenceUrl" and "user.name".

Unfortunately, it seems this is not so easy for Atlassian support to convert spaces any more: CONF-32918

FYI, Atlassian support was able to fix this for me very quickly.