Deleting duplicate projects from trash does not unblock migration

[hillrunner2008]

After facing the "Projects already exist on your destination site" error, I have tried to follow the suggestion to fully delete the conflicting projects (see https://support.atlassian.com/jira-cloud-administration/docs/trash-for-jira-cloud-projects/).

After 24 hours it seems this has not been effective as the same error remains. This seems like a bug and I'm hesitant to follow this advice

• reset your entire destination site

Do I have any other options? Are others facing the same error? I ran into this with both the cloud -> cloud migration and local instance to cloud.

[Jehan Bhathena]

Hi @hillrunner2008 ,

There are 2 approaches you can take in this scenario:

• Permanently delete the project from the DESTINATION site
• Rename the project in the SOURCE site

This article here gives more information https://confluence.atlassian.com/cloudkb/project-name-and-project-key-conflict-when-migrating-using-jira-cloud-migration-assistant-jcma-1101932314.html.

You may want to check the TRASH to see if the project is actually deleted or if it is processing the deletion, in that scenario you need to wait until the delete is processed.

NOTE: would recommend making a new migration run after the deletion or renaming has been successful, this will avoid any old data from being re-used and you'll have a more precise view of the migration

[hillrunner2008]

Hi @Jehan Bhathena ,
I thought I had made it clear I have already deleted the projects from the trash. That is the bug i'm reporting. I was trying to avoid renaming the project on the source, but was aware of that option. What isn't clear is why clearing a project from the trash is not enough as this should be enough according to the documentation. 

Its been a full day since fully clearing the trash of the projects but the issue has remained a blocker. 

[Jehan Bhathena]

Thanks for the feedback @hillrunner2008 , approaching the support in this use case would be the right step ahead then.

Do let us know what comes out from your conversation with the support team, so that it can be shared with the other community members.

Cheers!!