• Prerequisites
• Import repositories
• Items that are imported
• Items that are not imported
• Items that are imported but changed
• User contribution mapping
  • Old method of user contribution mapping
• Troubleshooting
  • General
  • LFS objects not imported
  • Import fails due to invalid/unresolved host address, or the import URL is blocked

Import your project from Bitbucket Server

Import your projects from Bitbucket Server to GitLab.

Prerequisites

• Bitbucket Server import source must be enabled. If not enabled, ask your GitLab administrator to enable it. The Bitbucket Server import source is enabled by default on GitLab.com.
• At least the Maintainer role on the destination group to import to.
• Bitbucket Server authentication token with administrator access. Without administrator access, some data is not imported.

Import repositories

To import your Bitbucket repositories:

1. Sign in to GitLab.
2. On the left sidebar, at the top, select Create new () and New project/repository.
3. Select Import project.
4. Select Bitbucket Server.
5. Sign in to Bitbucket and grant GitLab access to your Bitbucket account.
6. Select the projects to import, or import all projects. You can filter projects by name and select the namespace for which to import each project.
7. To import a project:
   • For the first time: Select Import.
   • Again: Select Re-import. Specify a new name and select Re-import again. Re-importing creates a new copy of the source project.

Items that are imported

• Repository description
• Git repository data
• Pull requests, including comments, user mentions, reviewers, and merge events
• LFS objects

When importing:

• Repository public access is retained. If a repository is private in Bitbucket, it’s created as private in GitLab as well.
• Imported merge requests and comments have an Imported badge in GitLab.

When closed or merged pull requests are imported, commit SHAs that do not exist in the repository are fetched from the Bitbucket server to make sure pull requests have commits tied to them:

• Source commit SHAs are saved with references in the format refs/merge-requests/<iid>/head.
• Target commit SHAs are saved with references in the format refs/keep-around/<SHA>.

If the source commit does not exist in the repository, a commit containing the SHA in the commit message is used instead.

Items that are not imported

The following items aren’t imported:

• Attachments in Markdown
• Task lists
• Emoji reactions
• Pull request approvals
• Approval rules for pull requests

Items that are imported but changed

The following items are changed when they are imported:

• GitLab doesn’t allow comments on arbitrary lines of code. Any out-of-bounds Bitbucket comments are inserted as comments in the merge request.
• Multiple threading levels are collapsed into one thread and quotes are added as part of the original comment.
• Project filtering doesn’t support fuzzy search. Only starts with or full match strings are supported.

User contribution mapping

The Bitbucket Server importer uses an improved method of mapping user contributions for:

• GitLab.com
• GitLab self-managed 17.7 or later when the importer_user_mapping and bitbucket_server_user_mapping feature flags are enabled.

Old method of user contribution mapping

You can use the old user contribution mapping method for imports to GitLab self-managed and GitLab Dedicated instances. For imports to GitLab.com, you must use the improved method instead.

Using the old method, the importer tries to match a Bitbucket Server user’s email address with a confirmed email address in the GitLab user database. If no such user is found:

• The project creator is used instead. The importer appends a note in the comment to mark the original creator.
• For pull request reviewers, no reviewer is assigned.
• For pull request approvers, no approval is added.

@mentions on pull request descriptions and notes are matched to user profiles on a Bitbucket Server by using the user’s email address. If a user with the same email address is not found on GitLab, the @mention is made static. For a user to be matched, they must have a GitLab role that provides at least read access to the project.

If the project is public, GitLab only matches users who are invited to the project.

The importer creates any new namespaces (groups) if they don’t exist. If the namespace is taken, the repository imports under the namespace of the user who started the import process.

Troubleshooting

General

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. It provides verbose error output.

See the troubleshooting section for Bitbucket Cloud.

LFS objects not imported

If the project import completes but LFS objects can’t be downloaded or cloned, you may be using a password or personal access token containing special characters. For more information, see this issue.

Import fails due to invalid/unresolved host address, or the import URL is blocked

If a project import fails with an error message such as Importing the project failed: Import url is blocked, even though the initial connection to the Bitbucket server succeeded, the Bitbucket server or a reverse proxy might not be configured correctly.

To troubleshoot this problem, use the Projects API to check for the newly-created project and locate the import_url value of the project.

This value indicates the URL provided by the Bitbucket server to use for the import. If this URL isn’t publicly resolvable, you can get unresolvable address errors.

To fix this problem, ensure that the Bitbucket server is aware of any proxy servers because proxy servers can impact how Bitbucket constructs and uses URLs. For more information, see Proxy and secure Bitbucket.