Migration of Bitbucket from 1 org to another

Vijay Kalkundri

Hello Everyone,

We had a old Atlassian account in which we had setup a bitbucket and use it as code repository. Later we purchased another account with Atlassian where we started using confluence and Jira . We have now have 2 organisation one which has just bitbucket and other has jira + confluence. Now we want to migrate all into 1 organisation and archive it. Following are some of the things we are looking post migration ::

1. One Atlassian account with Confluence , Jira and Bitbucket
2. No link between Jira and bitbucket be lost .
3. All the history of the contents needs to be maintained in the Bitbucket ( branches, pull requests etc )

Can this be achieved ? If yes how it can be done.

What are the risks ?

Viswanathan Ramachandran

Hi,

Welcome to the Community! 👋

TL;DR: Yes, 100% achievable. You won't lose PR/commit history, and Jira issue links will restore once re-indexed under the consolidated organization.

Here are the details:

1. Does History & Jira Linking Stay Intact?

• Bitbucket History: Preserved. Commits, branches, PRs, comments, and approvals remain untouched.
• Jira - Bitbucket Links: Preserved. Jira links work via smart keys in branch names, commit messages, and PR titles. Once Bitbucket is reconnected to Jira, a full sync will re-index and repopulate the issue Development panel.

2. Recommended Migration Path: Direct Workspace Linking

Avoid manual repo migrations if you can. Simply link the existing Bitbucket workspace into your Jira/Confluence Organisation:

1. Verify Roles: Ensure you are an Org Admin in the target org (Jira/Confluence) and Workspace Admin in Bitbucket.
2. Link Workspace:
   • Go to admin.atlassian.com > select your Jira/Confluence Org.
   • Navigate to Settings / Atlassian apps > Bitbucket > Link Bitbucket workspace.
3. Connect Jira:
   • In Bitbucket, head to Workspace Settings > Jira (under Atlassian Integrations) > click Connect to your Jira Cloud site.
   • In Jira, verify under Settings > Products > DVCS accounts / Bitbucket and trigger a Full Sync.
4. Decommission Old Org:
   • Verify all repos, user access, and billing are active in the target org, then cancel subscriptions on the old organisation.

💡 Note: If the Bitbucket workspace is an old personal workspace or locked, create a new workspace under the target org and use Repository Settings > Transfer repository instead.

3. Risk & Pre-Flight Checklist

Area	Risk	Mitigation
Pipelines Secrets	Deployment/environment variables do not transfer if moving repos between workspaces.	Backup all Pipelines environment variables and secured keys prior to any transfer.
Git Remotes	If the workspace slug changes (transfer scenario), developer push/pulls fail.	Linking the workspace keeps URLs intact. If transferring, have devs run: git remote set-url origin <new-url>.
User Identity	Mismatched email addresses cause unlinked commit authors.	Ensure users' Atlassian account primary emails match their Bitbucket commit author emails.
Webhooks & CI/CD	Third-party webhooks (Jenkins, SonarCloud, OAuth tokens) may break.	Audit workspace-level and repo-level webhooks before disconnecting the old setup.

FYI: At any point of time, please feel free to contact Atlassian support under Technical issues and bugs.

Note: If you don't have a sandbox setup, please do one and try the migration there to understand the process and technical details, have UAT tested and sign-off before the migration.