You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are planning a cloud-to-cloud migration of Jira projects.
There are two cloud instances, A and B. We intend to relocate the projects from B to A. How can we move Bitbucket repositories from cloud B to cloud A? Could you please share any documentation for this?
Hello @Deepika_Kanaparthi ,
Thank you for reaching out to Atlassian Community!
In case you want to migrate repositories from one bitbucket workspace to a different workspace, you can use the feature to Transfer repository ownership .
However, if you are just migrating the Jira projects and want your bitbucket workspace to still link to issues on that project, you will need to Connect Bitbucket Cloud with Jira Software Cloud in the new Jira instance.
Hope that helps! Let me know in case you have any follow-up questions.
Thank you, @Deepika_Kanaparthi .
Hello @Sanjen Bariki ,
Any repository-specific access will not be transferred to the new workspace. The admins of the destination workspace will need to manually configure the repository-level access, if any.
However, it's important to note that Bitbucket Clous uses project permissions inheritance, meaning that permissions defined at the project level will be propagated to all the repositories under that project.
When accepting a repository transfer, you will need to choose a project in the destination workspace where this repository will be moved to. All the groups/users that have access to this project will automatically be granted access to the transferred repository due to inheritance.
Thank you, @Deepika_Kanaparthi
Migrating from one cloud to another involves transferring data, applications, and configurations from one cloud environment to another. The specific steps will vary based on the type of data, applications, and configurations being moved, as well as the target cloud environment. Here are some general steps to consider:
Assess your current cloud environment and the target cloud environment, including any compatibility issues that may arise. Plan your migration by identifying what needs to be migrated and the order in which it should be done. Backup data and applications before starting the migration process. Test the migration process in a non-production environment before doing it in production. Perform the actual migration, following the plan. Validate that the data and applications have been successfully migrated and are working as expected. Perform any necessary post-migration tasks, such as updating configurations, testing and monitoring performance, and addressing any issues that arise.