My company wants to migrate our projects from bitbucket cloud to gitlab.com. So to try this out I ran the importer and it seemed to work fine. Only I imported the repo into my personal gitlab namespace instead of the company one. Not realising I could simply transfer the project I deleted it in order to re-run the import, only to discover that in the bitbucket repo selection screen of the importer the repo is still marked as already imported, with a link to an empty project (that I tried to delete in vain several times already, but the link always shows me the empty project). So my first question is, is is not possibe to run an import of the same repo twice? Also, I was planning to do this as a dry-run, then prepare all git connected tooling (such as external CI) to work with gitlab instead of bitbucket, and once everything is set up and tested do another import, this time for real (to cause as little disruption as possible with out development processes). So is that not a valid strategy to migrate, and is there any way for me to get out of this situation?
For anyone else seeing this, I blieve that the importer will allow you to import again if the destination project has been deleted. It just takes a few minutes for it to change on the importer page.
1 Like
Deleting the project and waiting (days and weeks in my case) did not help. My solution was to create a new gitlab user to import with and that worked fine. Just took me ages to come up with the idea.
1 Like