Failed Space import Cloud -> Cloud

[Karstein Kvistad]

Hello.

My backup from one cloud that I tried to import to another cloud keeps failing with the error: A space with key SEW already exists.

Reading on other similar failures on this page. This is not working:

Trying to make a new Blank page with same Key:

I had no Spaces left, since I delete them, and also from trash. Set the ID to the page above - to SEW2. And this is the only one showing.

And under Archived and Trash - nothing.

How can I fix/delete this SEW-key.

Or can I change the SEW-key in the import-zip to something else?

Weird that I find this error in 6 year old posts.

[Karstein Kvistad]

Well this is crazy, I found a new solution.

Extracted the Zip backup.

Opened one by one file in Notepad, Replaced all SEW with NEW, all sew with new.

Zipped the edited files. Imported without error.

But the Space were nowhere to be found. Tried the Blank page creation with id NEW, same fault as with SEW.

Looked around on all settings, found Space Permissions, had to start a 14-day trial.

Pressed Recover Permissions under Operations, 

Now I suddenly have both SEW and NEW, all data and pages are there. #mindblown

[Marc - Devoteam]

Hi @Karstein Kvistad 

You need to unzip your export.

Then do the following explained in the steps on this page:

https://confluence.atlassian.com/confkb/how-to-copy-or-rename-a-space-in-confluence-169578.html#:~:text=Manual,-Open%20the%20space 

Raise an issue with Atlassian Support to let them check why the key information still seems to be in the database of your instance even when the space is deleted and removed from trash