- How it works
- Importing your Bitbucket repositories
Introduced in GitLab 11.2.
Import your projects from Bitbucket Server to GitLab with minimal effort.
- In its current state, the Bitbucket importer can import:
- the repository description (GitLab 11.2+)
- the Git repository data (GitLab 11.2+)
- the pull requests (GitLab 11.2+)
- the pull request comments (GitLab 11.2+)
- Repository public access is retained. If a repository is private in Bitbucket it will be created as private in GitLab as well.
- Currently GitLab doesn’t allow comments on arbitrary lines of code, so any Bitbucket comments out of bounds will be inserted as comments in the merge request.
- Bitbucket Server allows multiple levels of threading. GitLab import will collapse this into one thread and quote part of the original comment.
- Declined pull requests have unreachable commits, which prevents the GitLab importer from generating a proper diff. These pull requests will show up as empty changes.
- Attachments in Markdown are currently not imported.
- Task lists are not imported.
- Emoji reactions are not imported
- Project filtering does not support fuzzy search (only
full match stringsare currently supported)
The Bitbucket Server importer works as follows:
- The user will be prompted to enter the URL, username, and password (or personal access token) to log in to Bitbucket. These credentials are preserved only as long as the importer is running.
- The importer will attempt to list all the current repositories on the Bitbucket Server.
- Upon selection, the importer will clone the repository and import pull requests and comments.
When issues/pull requests are being imported, the Bitbucket importer tries to find the author’s e-mail address with a confirmed e-mail address in the GitLab user database. If no such user is available, the project creator is set as the author. The importer will append a note in the comment to mark the original creator.
The importer will create any new namespaces (groups) if they don’t exist or in the case the namespace is taken, the repository will be imported under the user’s namespace that started the import process.
If you’ve enabled this feature, the importer tries to find a user in the GitLab user database with the author’s:
If the user is not found by any of these properties, the search falls back to the author’s
Alternatively, if there is also no email address, the project creator is set as the author.
User assignment by username is under development and not ready for production use. It is deployed behind a feature flag that is disabled by default. GitLab administrators with access to the GitLab Rails console can enable it.
To enable it:
To disable it:
- Sign in to GitLab and go to your dashboard.
- Click on New project.
Click on the “Bitbucket Server” button. If the button is not present, enable the importer in Admin > Application Settings > Visibility and access controls > Import sources.
Enter your Bitbucket Server credentials.
Click on the projects that you’d like to import or Import all projects. You can also filter projects by name and select the namespace under which each project will be imported.
If the GUI-based import tool does not work, you can try to:
- Use the GitLab Import API Bitbucket server endpoint.
- Set up Repository Mirroring, which provides verbose error output.