Calling on all workspace Admins - Connect your Bitbucket workspace to an Atlassian organization

[Geert Vanden Boer]

I have a question regarding the billing. Currently we are reselling bitbucket to our customer (a government agency),  but the atlassian org is billed by another reseller (includes JIRA/confluence)

To me it seems to make sense to integrate and centralise it, but will you be able to split the billing of bitbucket to a separate reseller?

if not, what is your advice for us, the resellers, and for our customers?

[Ingo Syllwasschy]

We use Jira, Jira Service Management (each „Standard“) and Confluence Premium Cloud. These applications are licensed through a reseller. Bitbucket Premium licenses were purchased directly from Atlassian. Two different e-mail addresses and payment methods have been used.

Now we should add Bitbucket to our domain. According to our reseller, this is only possible if Bitbucket is also licensed by him. Since our Bitbucket contains the source code of all our applications, I am afraid to do something wrong if I simply asssigne Bitbucket to our domain according to instructions.

What do I have to consider?

[Indah Rosita BR Bangun]

Hi Atlassian Community,

As part of the Early Access Program (EAP), our Bitbucket Cloud workspace will be migrated into the Atlassian Admin Console (organization-level). Before we proceed, we would like to clarify a few detailed aspects to ensure a smooth transition.

1. User Access, Repository Permissions & Group Management

What will be the impact on user access, repository permissions (both personal and group), and group management after migration?

Specifically: Will our existing Bitbucket workspace groups be moved into the Atlassian Admin Console, or will they be deleted/archived?

How will existing permissions (especially those assigned via groups) to repositories/projects be handled? Will they carry over seamlessly or require re-assignment?

2. Changes in Access Control & Administration Model

Are there any changes in the access control model or administration model compared to our current standalone Bitbucket setup?

For example: changes to admin roles, token usage (SSH, API), or how access tokens are managed at organization level vs workspace level.

3. Preparations & Adjustments on Our Side

What preparations should we make (e.g., user/group audit, token review, SSH key cleanup) to ensure the migration is smooth and we avoid disruption?

Are there any best practices you recommend for handling access tokens, SSH keys, or API tokens when migrating from workspace to organization?

We appreciate your guidance and confirmation on these points so we can properly plan our internal workstream and avoid potential risks.

Thank you in advance for your support.

[Mario De Carli]

I'm trying to add Bitbucket App but my workspace doesn't show up, what can I do?

[Yana]

@Geert Vanden Boer  and @Ingo Syllwasschy 

Hi there, 

You can continue keeping Bitbucket billing separately even post migration to Atlassian Administration and new Billing engine. 

You can also continue maintaining different primary billing contacts for each product. 

Billing unification will be an option if you decide to do so, however it is completely up to you if you want to have a unified bill or continue having a separate bill for each Atlassian app. 

Cheers 

[Yana]

@Mario De Carli 

your workspace type is not yet eligible to complete the linking to an Atlassian Org. 

Our team will be reaching out to you early next year to advise on the next steps.  

cheers

[Yana]

Hi @Indah Rosita BR Bangun 

If you would like to participate in our EAP program to migrate your workspace to Atlassian Administration for centralized user and product access management.

Please fill out this participation form and post your questions on the form and we will respond to you via email. 

Thank you.

[Louis Spieckerhoff]

I cant link my personal workspace. How can i do that?

[Darcy Mulligan]

According to the AI support we have a "legacy Bitbucket Cloud workspace" and so cannot link it to our organization's Atlassian Organization.

Is there any ETA on when we'll be able to do that? Or can someone at support help us?

[Yana]

@Darcy Mulligan  @Louis Spieckerhoff 

Hi there, 

For legacy workspaces that are not yet eligible to link their workspace to an Atlassian Org, our team will be getting in touch with you via email and UI messaging in the first half of 2026 on the next steps. 

No action is needed from you at this time. Thank you for checking !

[Jayden Thorup]

I need support to contact me. I am unable to open a ticket, and I am unable to link my organization's workspace. 

[Siddardha Sarabu]

Hi @Yana,

Our bitbucket workspace is already linked to our Org.

What's the ETA for migration to happen? I am primarily interested in user migration to Atlassian Administration.

EAP link that you provided doesn't seem to work now. I get this error - "Not Found. Either you don't have access to this request type, or it doesn't exist. Log in"

- Sid

[Yana]

Hi @Siddardha Sarabu 

The EAP is now closed. We are completing migrations for all customers that enrolled in EAP before December 1st. 

I'll send you an email with further details. 

Cheers

[Yana]

@Jayden Thorup 

I have reviewed your workspace, my response here https://community.atlassian.com/forums/Bitbucket-articles/Calling-on-all-workspace-Admins-Connect-your-Bitbucket-workspace/bc-p/3150011#M2619 

is applicable to your workspace. 

Thank you

[birden]

@Yana 

If we create a new organization following this approach, does that mean we can use Bitbucket within an independent framework?

The entire group already has an Atlassian account and has been using Bitbucket under a separate management structure.
Due to cost payment reasons, we do not want to incorporate this Bitbucket into the group-wide organization.
(We understand integration would be more convenient, but company circumstances prevent us from consolidating.)

[Yana]

@birden 

Thank you for your question. This is correct, if you create a new Org and link your Bitbucket workspace to it, we will migrate billing and user management to this new Org for Bitbucket workspace and it will be independent from other Atlassian apps.  

This means that Bitbucket billing will continue to be separate from other Atlassian apps. Also you will be missing out on full context of Atlassian TeamWorkGraph since this new Org will be completely separate from the rest of your company. 

Hope this helps.

[Asanka Indunil]

after we link bitbucket workspace, do we need to reassign bitbucket permission again ??.  cos we already have Atlassian organization using same domain users. 

[Yana]

@Asanka Indunil 

Linking your workspace to an Atlassian org, will not impact permissions or users immediately. 

When Atlassian migrates your user management, product access and billing to Atlassian Administration, all permissions will be preserved as they are on the day of the migration. 

The change that you will observe post migration will be that user's product access and user management will be handled in Atlassian Administration, however resource permissions, like repository and project access will continue to be handled directly in Bitbucket App. 

[ARF ENG]

We only use bitbucket and find the rest of the jira ecosystem to be unwanted overhead that someone in our group must figure out how to deal with. I'm sure other companies have some use case for the rest of jira beyond bitbucket but we don't. Is there a way to only use bitbucket and get away from the rest of jira? 

Edit: Sorry replace jira with Atlassian, the Atlassian ecosystem is the unwanted overhead. When I log into bitbucket it seem that I'm also logged into ever other product that Atlassian makes. I would rather have a simple host for a git repo and not all the extra Atlassian overhead. 

[Yana]

@ARF ENG 

Current Bitbucket workspace Admins, will continue to have the same permissions level at the Org level. You will be able to manage App Access as well as being a User Access Admin for Bitbucket App in Atlassian Administration. 

You will not need to interact with Jira app, since user management and apps access management is handled in the Atlassian Administration through groups membership. 

If however you would like to keep Bitbucket completely separate from the rest of your Atlassian Org and Apps,  you can create a brand new Org and link your Bitbucket workspace to it. This way you will have full control over user management and billing in that Org just for Bitbucket.  

Here are a few helpful resources 

• How to control users product/apps access in Atlassian Administration:  Control how users get access to apps | Atlassian Support

• How to configure project permissions for user groups in Bitbucket: Configure project permissions for users and groups | Bitbucket Cloud | Atlassian Support  

• For Atlassian Guard integration, how user licensing works: Atlassian Guard | Atlassian  

• How cloud users are counted towards billing: Atlassian Cloud Licensing | Atlassian