error from "importing a space" content from a confluence srv: A space with key NET already exists.
Asked by Woody Marvel:

Working to import zip XML "Confluence-space-export-123040-46.xml.zip" file exported from a local confluence server to be imported to the cloud site. Searched the community but nothing explicit for this type of error. Do I need to create an existing space on the cloud confluence instance before importing? That does not seem to be reasonable, IMO. There is no matching "space" existing on the importing system on the community errLogs..

Any help appreciated.

w.marvel


Answers:
author: Woody Marvel
body: 31jan24@1039h  
There was a setting for showing the  
spaces, iirc, that was able to see all the spaces imported and then there was an activation of the 14day trial which allowed management of those work spaces and deleting of the ones not needed.


author: Kristian Klima
body: Hey [@Woody Marvel](/t5/user/viewprofilepage/user-id/3788287)

**Hypothesis 1**

It looks like you already have a space with the space key 'NET' in your Confluence.

Space key is a unique identifier of a space on a Confluence site, it cannot be changed, and there can't be two spaces with an identical key.

Ensure there's no such space in your cloud - including in archived and trashed spaces. (Spaces \> All spaces \> Archived \> ... \> Space settings \> Delete space \> Delete.

**Hypothesis 2**

Since this is a Server to Cloud import, ensure that you followed the migration procedure. Haven't done a migration for almost two years but I think there's an app/setting on the server side that kind of preps your space for seamless cloud import.

comments: author: Woody Marvel
body: Have attempted to delete the NET key name and let the import create the workspace. There is nothing from the dashboard showing on 2 spaces for 2 admins. I was able to create a new space, not a matching name to the old one, and will retry all the steps you mention, status after that. If GTG then will accept your answer.

Migration procedured, walk-throught with someone who has more experience with migration, done and we did those steps you mentioned.

I was think there is a cache entry in the system and that could be cleared but I do not know how to clear that.

reporting back:

WM


author: Woody Marvel
body: deleted anything in spaces from the dashboard


author: Kristian Klima
body: Make sure to check the tabs in the Spaces dashboard. Spaces in Archived and Trashed do not appear under All spaces view.

And after you delete Archived, they still linger in Trashed.

BTW, there's no need to create a space in Cloud prior to importing a space.

![Spaces.png](https://community.atlassian.com/t5/image/serverpage/image-id/303352i48D14D1C04A93FFF/image-size/large?v=v2&px=999 "Spaces.png").


author: Woody Marvel
body: Even though the import seemed to work, (changing the key name in the entities) the workspace does not show on the dashboard, even logging out and back in, starting confluence again. It must be cache on that remote server contains some setting we do not have access to. Posting replies to the original posting on the community discussions with hope someone can help.

31jan24@1039h  
There was a setting for showing the  
spaces, iirc, that was able to see all the spaces imported and then there was an activation of the 14day trial which allowed management of those work spaces and deleting of the ones not needed.

The prior posting(s) are appreciated but at this time there is not an issue with workspaces. Thank you.


author: Kristian Klima
body: Sure, no problem, I just like tinkering and solving Confluence mysteries :)


Tags: cloud

confluence-cloud