Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to move Bitbucket workspace from one organization to another (duplicate)

Jon Geerars
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 27, 2026

Hi Atlassian Support,

We have two Atlassian organizations that both belong to the same company. This appears to be a historical artefact: our Bitbucket workspace was created under an older account, and Jira/Confluence were set up later under a different admin account, so each ended up with its own auto-created organization.

- Organization A — ID `2e911c83-...`
Products: Jira and Confluence
4 managed users

- Organization B — ID `4542e1c0-...`
Products: Bitbucket only
1 managed user

Request: please move the Bitbucket workspace from Organization B to Organization A, so that all our products (Jira, Confluence, Bitbucket) are managed under a single organization. Once the workspace has been moved, Organization B will be empty and can be deleted (we can do that ourselves, or you may delete it as part of the same request).

What we have tried: in Organization A, "Link Bitbucket" fails with "This app has already been linked to an organization". In Organization B there is no transfer/unlink option for the workspace, and the workspace settings in Bitbucket offer no way to unlink it from the organization either. As far as we can tell this can only be done by Atlassian.

Notes that may help:
- Both organization admins are the same person;
- The workspace has an existing Jira integration. We would like that integration to remain intact after the move.
- No billing changes are involved; the workspace is on the Free plan.

Thank you!

Jon

2 answers

2 accepted

1 vote
Answer accepted
Gabriela - LeanZero
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 27, 2026

Your read is half right, and the half that's off matters. The KB is flat about the move itself: "It is not possible to unlink the workspace from an existing Atlassian Org or move it to a different Org. This is a current limitation." It doesn't say anything either way about what support can do behind the scenes, but I've not seen a case where they moved one, and a ticket quoting that sentence back at you is the likely outcome.

The useful part is that it's tracked and moving. BCLOUD-23320, Support transfer of Bitbucket Workspaces Between Organizations, sits at In Progress with 100 votes and 104 watchers. Yana from Atlassian commented on 6 August, "We are actively working on this request. Once this functionality is available, we will be updating this ticket." Open since July 2024. In Progress with that comment on it is about as good a signal as that tracker hands you.

Your exact shape is on the thread already, someone describing the same auto-created org holding nothing but the Bitbucket app. So watch and vote there, because that is where the announcement lands.

If it's the narrower ask you want, an org admin unlinking it without Atlassian, that one is AX-424, still Gathering Interest at 7 votes.

Jon Geerars
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 31, 2026

Thanks Gabriela, that's the nuance I needed. Vote and watch added on 23320, and one on AX-424 for good measure. Marking this as the accepted answer.

0 votes
Answer accepted
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 31, 2026

Hi @Jon Geerars 

It is not possible to unlink an organisation from a workspace once linked, or transfer the workspace from one org to another - this is highlighted in our documentation:

You may follow the feature request BCLOUD-23320: Support transfer of Bitbucket Workspaces Between Organizations for updates on when this will be available. It is currently in progress and being actively worked on by our engineering teams.

Alternatively, you may create a new workspace within the correct org and migrate the data across to the new workspace:

Cheers!

- Ben (Bitbucket Cloud Support)

Jon Geerars
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 31, 2026

Hi Ben,

Thanks for the clear answer. That matches what I could (not) find in the admin UI. Since one of our accounts is already a workspace admin, there's no functional gap for us; it's purely an organisational tidy-up, so I'd rather wait for BCLOUD-23320 than migrate to a new workspace and change every repository URL. I've voted and am watching the ticket. Feel free to close this one.

Thanks,
Jon

Like Ben likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events