Transfer Apps option is grayed out on the Organization
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Overview
The Transfer all apps to another organization you administer option can appear grayed out in Atlassian Administration. This happens when there are unresolved pre-transfer blockers on the source organization.
This article walks you through how to check whether you're eligible for a transfer, identify what's blocking it, and resolve the most common blockers.
Before you start
Confirm your User Management Experience
The transfer option is only available for organizations on the Original user management experience. If your organization uses Centralized user management, individual site transfers are not supported, and this option will not appear.
Here's how to check:
Go to admin.atlassian.com and select your organization.
Look at where the Users page appears:
Experience | Where to find Users |
|---|---|
Original user management | Users are under the App site. No Users page under the Directory tab. |
Centralized user management | Users are under the Directory tab in the admin hub. |
Learn more: Identify your organization’s user management UI experience
Step 1: Find the Transfer option
Go to admin.atlassian.com.
From the organization picker, select the source organization (the one you want to transfer products from).
Select Organization settings → Profile.
Look for Transfer all apps to another organization you administer.
If this option is grayed out, there could be blockers. Continue to Step 2.
Step 2: Identify the blockers
You can find the exact blockers using your browser's developer tools.
While on the Profile page from step 1, open your browser's developer tools using any of the following methods:
Press F12, or
Press Ctrl + Shift + I (Windows/Linux), or Cmd + Option + I (Mac), or
Right-click anywhere on the page and select Inspect
In developer tools, select the Network tab.
Confirm that network recording is active - look for a solid red record icon in the top-left of the Network tab. If the icon is gray, click it to start recording.
In the Network tab's Filter bar, enter: reparent-blockers
Reload the page by pressing F5 (Windows/Linux) or Cmd + R (Mac).
In the filtered results, click the reparent-blockers request.
Open the Preview or Response tab in the request details panel to view the list of blockers.
Tip: If nothing appears, turn on Preserve log and reload again.
Note: Refer to our public documentation, “Generating HAR files and analyzing web requests,” for detailed steps.
If you share the list of these blockers in your support ticket, Atlassian Support can provide the exact steps to clear them.
Step 3: Resolve Common Blockers
Below is a list of common blockers you may encounter in Step 2.
Rovo Credits and Indexed Objects
What it means: The source org has active Rovo Credits and Indexed Objects entitlements that must be deactivated before the transfer can proceed.
What to do: Provide written approval on your support ticket so we can deactivate these entitlements on the source organization. The blocker will clear once they're deactivated.
Rovo License
What it means: The source org has a Free Rovo license entitlement that must be deactivated.
What to do: Provide written approval on your support ticket. Then:
Removal can take up to one day.
After the transfer, reactivating Rovo in the destination org will require manual effort, a new ticket, and may require developer assistance.
There's an open feature request to automate it: https://jira.atlassian.com/browse/AX-1725.
App Access Settings (Or User Access Settings)
What it means: Custom App Access Settings on the source org need to be reset.
What to do:
Go to admin.atlassian.com and select the source organization.
Navigate to Products/Apps → App access settings.
Click Reset your user access settings.
See: How to Reset App Access Settings Before a Product Transfer
Will this affect my users? No.
Does not remove access from existing users or groups
Does not cause any downtime
Is an admin-side change only
Think of it as the rules for how new users get invited in the future. Resetting returns those rules to default; it doesn't take access away from anyone who already has it. You can reconfigure these settings in the destination org after the transfer.
Related Articles
Was this helpful?