What gets migrated with Bitbucket Cloud Migration Assistant

Repository Git information

• If your repository is part of a project in Server, then The Git repository (including all branches, tags, and commits) will be migrated to a new project with the server project name or added to a project of the same name that already exists in your cloud destination.

Pull request information

• Title

• Description

• Pull request status (open, merged, declined)

• Code diff, comments, tasks

• Authors

• Reviewers

Users

• Choose which users to migrate:

  • All users

  • Users with read access or who appear on selected repositories

  • Only users who appear on the selected repositories

Atlassian administrated workspaces only

Groups

Choose which groups to migrate:

• All groups

• Only groups with users and permissions selected for migration

• Do not migrate any groups

Permissions

Choose which permissions to migrate:

• Copy permissions of all users and groups

• Do not copy any permissions

Branch permissions & branch modeling

• Choose whether or not to migrate any branch permissions and branching models

Repository Git information

• Migrating the link or association of forked repositories

  • NOTE: The forked repo can be migrated but it will lose its link or association and be treated as a normal repo if migrated. We recommend merging any open pull requests from forks prior to migrating to the cloud to prevent any data loss.

• Content stored in Git LFS

  • NOTE: Git LFS can be migrated manually afterward. You will need to install and set up Git LFS on your repositories in Bitbucket Cloud. Learn more

• Git submodules

  • NOTE: Specifically, the extra configuration within the code base (in a .gitsubmodules file) is not automatically updated. This file contains the links to other repos that will need to be updated by a customer/partner either before or after migrating.

• Pull request attachments

• Pull request activity feed

• Repos with duplicate names

• Open changes on local machines

• Extra large repos (max is currently 10GB)

• Personal repos

  • NOTE: As a workaround, we recommend moving these to normal projects first so they can then be migrated.

• Repo settings:

  • Add default reviewers

  • Branch permissions

  • Managing webhooks

  • Merge checks

  • Build statuses

User metadata

• Groups - Bitbucket administrated workspaces only

• Permissions - Bitbucket administrated workspaces only

• Settings

• Avatars

• Passwords

• Timezones

• SSH keys

• App passwords

• Inactive users' permissions and/or any branch restrictions they’re associated to

Project data

• Settings

• Permissions - Bitbucket administrated workspaces only

Apps and app data

• App data is not included when migrating from Bitbucket Server to Bitbucket Cloud using BCMA. Some apps do have the capability to export and import their data (outside of BCMA scope) but you'll need to check with the app developers or their documentation to confirm if this is possible.

Atlassian administrated workspaces only

Issue tracker and wikis

• Wiki and Issue Tracker features are not supported in workspaces administered through admin.atlassian.com. These features will be disabled if you are migrating to a workspace administered through admin.atlassian.com. If you have already migrated the repository, you can still go back to that repository in your Server or Data Center instance to regain access to the wiki and issues. Wikis can be exported via cloning since they are stored as a separate repository. Issues can be exported as a zip file or migrated to Jira.