Error "user is not org admin" migrating Bitbucket data to the cloud

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Check what to do when you are an organization admin of your cloud instance, but the Bitbucket Cloud Migration Assistant (BCMA) still errors out with "user is not org admin".

Overview

When a user who is an organization admin in the destination cloud Instance creates a migration plan using BCMA, they can experience a migration failure during user creation.

The migration logs show that the migration failed during user creation with the below error:

1 "message": "[<key> throwIdentityException] Error body: {\"key\":\"forbidden\",\"context\":{\"message\":\"user is not org admin\"}}"

This often happens because the user account that created the migration plan is not the same as the user account authenticated in the cloud platform.

Whoever connects the workspace through the "Connect to Bitbucket Cloud" step links their personal account to the cloud.

The user account that connects to the cloud is the one that needs to be an organization admin.

Solution

Refresh the connection by clicking I already have a workspace and selecting the workspace again, with the below steps:

  1. Ensure you logged in with a user who is an organization admin.

  2. Return to the Connect step in BCMA.

  3. Select I already have a workspace to add your cloud destination workspace to your migration plan again.

  4. Select your workspace again from the dropdown.

  5. Click Next.

Connect step screen in BCMA

Connect step screen in BCMA
Updated on April 17, 2025

Still need help?

The Atlassian Community is here for you.