Unable to Migrate a Confluence/Jira Space using Data Transfer Tool

Question

Hello, 
I am trying to migrate a space/project from one instance to another (ex. name1.atlassian.net to name2.atlassian.net) by using the Data Transfer tool. When validating the data I get an error that there is already a space that exists in the destination with the same key (ex. SP).

I checked the destination instance and there are no projects with SP that are active, archived, or in the trash.

Secondly, when I try to change the key of the space I'm migrating (from SP to SPU) to work around the error, the changed key is not getting properly reflected in the Data Transfer page (it still shows the old key SP, not SPU).

Aaron Pavez _ServiceRocket_ · Accepted Answer

HI @Marika Sword

This sounds like a browser issue.

Can you check if the space really exists? Use this API:

youratlassianurl.atlassian.net/rest/api/3/project/PROJECTKEYHERE

If  you want to make sure it's deleted, use the API to delete the project:

https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-projects/#api-rest-api-2-project-projectidorkey-delete

If you still can't move it with the data transfer, open a ticket with Atlassian. Maybe something in the back is being obnoxious.

Regards

Trudy P Claspill · Accepted Answer

Hello @Marika Sword

I believe another way this might occur is if one of the projects in your destination system previously used the key "SP". Jira keeps track of key changes so that when a user has a link to an issue with the old key it can automatically redirect them to the issue with its new key. Refer to

https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Announcing-the-ability-to-unlink-previously-used-project-keys/ba-p/2814789

If you look at Space Settings > Details where it shows the Project Name and Project Key it will also show you any previous key associated with the project.

Try checking each space to see if "SP" is recorded as a previously used key.