This page covers some of the most frequently asked questions we hear about switching from self-managed Bitbucket (server or Data Center) to Bitbucket Cloud.
If you’re ready to get started on your migration, check out our Bitbucket migration planning guide for additional guidance.
We’re working hard on creating a migration assistant for Bitbucket to migrate code, pull requests, and basic configuration settings from Bitbucket Server. If you’re interested in using this tool, sign up for the Bitbucket Cloud Migration Assistant early access program for updates as we roll it out.
There are several options for migrating your repositories over to Bitbucket Cloud, including:
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, then Bitbucket Cloud will not be able to access 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.
Currently, we only support moving repository data (your source code) from Bitbucket Server to Bitbucket Cloud. There's no supported method for migrating user accounts, permission structures, or repository metadata like pull request history and comments.
Note that due to the limited scope of data migrated, you can migrate from any version of Bitbucket Server.
No, there’s no cost to migrate from Atlassian's self-managed products to cloud.
With Bitbucket Cloud, hosting, maintenance, and upgrades are all handled for you. To see a grid that displays the differences between cloud, server, and Data Center check out the Bitbucket features page. For a more detailed look into the way Bitbucket Cloud functions differently than our Server product, refer to Functional differences in Bitbucket Cloud.
Security and compliance
In very rare instances the entire site may go down for maintenance. If this occurs, we'll announce it on status.bitbucket.org and will also show the status in a banner at the top when logged in to Bitbucket.
We don't currently have an official uptime SLA agreement. However, since downtime is bad for everyone's business, including ours, we strive for 100 percent uptime and have made uptime and reliability transparent and trackable.
We treat reliability and security very seriously. You can find out how we handle backups in our Bitbucket Cloud documentation.
Unlike Bitbucket Server, Bitbucket Cloud is offered as a monthly subscription on a per-user basis, with three different pricing plans: Free, Standard, and Premium. Check out Bitbucket Licensing to decide which plan is best for your team and estimate your monthly costs.
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 don't transfer to Bitbucket Cloud. These are two separate licenses and are paid for separately.
No, you can't switch an existing Bitbucket Server license to a Bitbucket Cloud license. To move to Bitbucket Cloud, you'll need to sign up for Bitbucket Cloud and then stop renewing your server license or maintenance.
Check out our Bitbucket migration planning guide for step-by-step instructions on how to plan and execute your migration.
When you migrate from Bitbucket Server to Cloud, the following data is imported:
Repository data (your source code).
The following is not imported:
Repository metadata, including pull requests and comments.
User accounts and permission structures.
Apps are not migrated when you move from Bitbucket Server to Bitbucket Cloud.
After migrating, you'll need to re-install any compatible apps or work with the app vendor(s) to migrate any relevant data.
You'll need to add your users to Bitbucket Cloud before or after migrating your repositories. Users aren't included when you import repositories.
For those that are interested in moving their CI/CD solution to the cloud, Bitbucket Pipelines is built-in to Bitbucket Cloud and offers a lot of the same benefits.
Whether you use Jenkins, Bamboo, TeamCity, or other third-party CI/CD tools, Bitbucket Cloud works with major CI/CD providers so your team can work how they want without having to start from scratch, with integrated webhooks functionality. Bitbucket Cloud enables timely and efficient builds to be triggered. Learn more about integrating other CI/CD tools with Bitbucket Cloud.
While we don't offer professional services for migrations, our Bitbucket Cloud Support team can help you plan 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.
Yes, our Bitbucket Cloud support team can help with technical questions or issues related to your migration.