Bitbucket EAP Migration – Clarification on Group Migration, Permissions & Tokens

[Indah Rosita BR Bangun]

Hi @yana 

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.