Plan your Cloud migration
Documents to help you prepare to migrate your Atlassian Server products.
Plan your Cloud migration
Documents to help you prepare to migrate your Atlassian Server products.
User management and migration
App assessment and migration
A collection of topics that help prepare you to migrate your apps to the Cloud.
Ensure you’re ready to migrate with these pre-migration checklists for Jira, Confluence, and Bitbucket Server or Data Center.
Jira Cloud Migration Assistant
Confluence Cloud Migration Assistant
Documents that walk you through using the Confluence Cloud Migration Assistant to migrate to Cloud.
Bitbucket Cloud Migration Assistant
Documents that walk you through using the Bitbucket Cloud Migration Assistant to migrate to Cloud.
Jira Site Import
Documents to help you use Jira Site Import to migrate to Cloud.
Get up and running in Cloud
Resources to help get started and testing after you migrate.
Everything you need to know about moving your data from one cloud site to another.
Migration best practices
A set of optional best practices that you can apply to your migration.
This guide provides an overview of recommended activities before and during the Cloud migration process. It covers enlisting your team, evaluating technology options, ensuring that the current Bitbucket Server site is ready for migration, and executing the migration.
Currently, we support migrating the following with the Bitbucket Cloud Migration Assistant:
Repository Git information: If your repository is part of a project in Server, the repository 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. Note: at this time, we do not support migrating forked repositories. Merge any open pull requests from forks to prevent any data corruption prior to migrating to the Cloud.
Pull request information: Title, description, pull request status (open, merged, declined), and the code diff, comments, tasks, and authors/reviewers.
Users: All active or licensed users and any inactive users who are attached to a pull request (are an owner/author or reviewer) in your Server instance will be migrated to Bitbucket Cloud.
Adhering to your organization's security requirements is critical to a successful migration. For more information about Atlassian's security, privacy, and compliance policies, check out the Atlassian Trust Center. At this point, you may want to work with your procurement or security teams to make sure Bitbucket Cloud meets your requirements. Learn more about Atlassian Trust Center
Before deciding to migrate, review any apps and custom integrations you have to determine what you'll need for your Bitbucket Cloud site. The Atlassian Marketplace offers a variety of apps and integrations that extend the functionality of Bitbucket Cloud. These include free integrations with leading SaaS productivity and collaboration products like Slack and Gmail, and subscription-based licensing of some of your most beloved Server apps. Keep in mind while you're evaluating that while Atlassian’s Cloud and Server products provide the same benefits, they can differ in features and functionality. As you evaluate, you may discover that Bitbucket Cloud includes functionality that is fulfilled through an app on Server. You may also have in-house or custom-built apps to consider. Learn more about the differences in administering Bitbucket Data Center and Cloud
App data is not typically included when migrating from Bitbucket Server to Bitbucket Cloud. Some apps do have the capability to export and import their data but you'll need to check with the app developers or their documentation to confirm if this is possible.
If you do need to map Bitbucket Server apps to Bitbucket Cloud, first check if there is a Cloud equivalent of your Server app in our Marketplace. If there is a Cloud equivalent, your next step would be to check with the app developer to see if it stores any data. If it does, you'll need to work with the app vendor to understand your data migration options. Atlassian doesn't directly handle migrating data generated from third-party server apps to Cloud apps. If there's no equivalent and the app stores data, you should still contact the vendor to see if there's a way to export the data.
There's no cost to migrate to Bitbucket Cloud besides the cost of your Bitbucket Cloud subscription. However, you'll still want to assess your payment options and overall costs.
Bitbucket Cloud is offered as a monthly subscription on a per-user basis, with three different pricing plans: Free, Standard, and Premium. Learn more about Bitbucket licensing
If you're planning on using apps from the Atlassian Marketplace in Bitbucket Cloud, remember to factor these into your cost considerations.
Note that your existing Bitbucket Server license and maintenance won't transfer to Bitbucket Cloud. These are two separate licenses and are paid for separately.
Sign up for a free Bitbucket Cloud trial to give Bitbucket Cloud a spin. Keep in mind as you try it out that the design and user interface and administration experience can vary across Bitbucket Server and Bitbucket Cloud, and you can't switch between the two. We recommend trying Cloud before migrating to get comfortable with the differences and identify any communications or training needed to help onboard your users. Learn how to sign up for a free trial
Now that you've decided to migrate, let's figure out how to get you there.
Migrating from Bitbucket Server to Cloud will have an impact on your users' experience and workflows, as well as various stakeholders throughout your organization. Depending on the size of your organization and number of users, a migration may require a fully fledged project with defined roles and responsibilities across teams. As early as possible, you should communicate with individuals and stakeholders who are interested and impacted by a move to Bitbucket Cloud. Where possible, recruit and enlist these people to be a part of the process.
Beyond informing your organization about the migration schedule, share your migration plan with team members. Determine how you'll alert users about any issues or errors that arise. At this stage, your migration communication plan should cover things like:
When will the migration occur?
What downtime can users expect?
Ask people to avoid changing anything during the transition.
What will happen to the old site after migrating? Will it still be accessible or readable?
Evaluate your current environment to determine if you need to make any changes before migrating your data. We recommend finishing and merging or closing all open pull requests before migrating. This way, all new pull requests will get created directly in Bitbucket Cloud after you migrate. Also, go through your Server user base and clean up any users who may be inactive or don’t need to be migrated to your new Cloud destination.
Note: In Server, you can have multiple repositories with the same name or slug, but in Bitbucket Cloud each repository name and slug needs to be unique. To avoid any issues, ensure that the name and slug of your repositories is unique throughout your Server instance before migrating to the Cloud.
Bitbucket Cloud supports SAML SSO with a subscription to Atlassian Access. You can configure SAML SSO for all users in your organization. When they access the Bitbucket Cloud web interface, they will be redirected to your SSO provider to log in. However, your users' SSO credentials are not valid for Git operations. Users will need to use an app password for https authentication, or switch to SSH authentication for Git operations.
If you are using the Bitbucket Cloud Migration Assistant, your Server users (both active and inactive) will be added to the Bitbucket Migration Users group in Bitbucket Cloud. The migrated users will not have access to anything within Bitbucket Cloud. Do not add permissions to the Bitbucket Migrations Users group. You will need to create groups or move the migrated users to existing groups and provide them the necessary access and permissions to any repositories or other content in Bitbucket Cloud. Learn how to organize groups for your repositories
Note: Inactive users remain inactive after being migrated to the Cloud, meaning those users do not count toward the people on your Bitbucket Cloud plan.
If you are using any of the other migration methods mentioned in Step 1 of the Migration section below, only repositories will be migrated to the Cloud.
If you need assistance with your migration, we have a wide network of partners globally that are very experienced in Atlassian migrations. Learn more about Atlassian Partners
After you have the necessary prerequisites in place and have completed the tasks associated with the pre-migration phase, you're ready to perform the migration. The steps outlined below provide guidance around migrating from your Server instance to your new Cloud destination.
We recommend using the Bitbucket Cloud Migration Assistant to migrate to Bitbucket Cloud.
There are a few ways to move your data to the Cloud:
Recommended: Use the Bitbucket Cloud Migration Assistant. You must be using version 7.0 or later of Bitbucket Server to install and use it. Learn more about the Bitbucket Cloud Migration Assistant
Use our repository importer to import individual repositories. To migrate using the importer, your Bitbucket Server domain needs to be publicly accessible. If it's not publicly accessible Bitbucket Cloud will not be able to access to your Bitbucket Server to perform the import.
You can also create a new repository on Bitbucket Cloud, and then simply push from your local repository to the new repository in Bitbucket Cloud.
If you have a lot of repositories, Bitbucket Cloud provides APIs for you to script the creation and pushing of repositories in bulk.
We recommend performing a trial run in a testing or staging site to ensure that everything is working as expected and the migration runs smoothly. You can do this using a free Bitbucket Cloud trial. The test migration will help you:
Identify possible bugs and the steps needed to resolve these before the actual migration. This will help you to:
establish a clearer timeline for your live migration, including any expected downtime.
validate the data before moving to Bitbucket Cloud.
Build a timeline: Identifying an ideal migration window can mean the difference between happy and frustrated users. Determine how much time your migration will take, factoring in time for troubleshooting. Consider scheduling the migration for overnight, on a weekend, or when your team is less likely to need access to Bitbucket. This will reduce the risk of data discrepancies between Server and Cloud.
Migrate to Cloud: Run your production migration using your chosen migration method. Don't forget to lock down your Server or remind your users not to make changes during the migration window. You will probably need to spend some time testing and troubleshooting before you can safely invite your users to Cloud.
Not all migrations are quite so straightforward. If you are using the repository importer and you need to merge multiple Server sites, just follow the same process for each site to import your repositories and add your users to your Cloud site. Learn more about the repository importer
If you've run into a problem during your migration, we're here to help. You can start by searching for known issues in Bitbucket Server or Bitbucket Cloud in our public issue trackers. There, you can find information about some of the common issues we see with Bitbucket migrations, including their status and suggested workarounds:
If you've run into a different question or need help to move forward with your migration, you can contact the Bitbucket Cloud Support team.
We have a number of channels available to help you with your migration.
Our Bitbucket Cloud support team can help with technical questions or issues related to your migration.
For help with a large-scale migration, we also have a wide network of partners globally that are experienced in Atlassian migrations. Get in touch to find one who can help with your migration.
Looking for peer advice? Ask the Atlassian Community.
Want expert guidance? Work with an Atlassian Partner.
Check out our After migrating to Bitbucket Cloud help documentation to get a clear understanding of what needs to be done once you’ve migrated to Bitbucket Cloud.
Support for Atlassian Server products ends in February, 2024. Learn more about the Server end of support timeline.
Was this helpful?