Plan your Cloud migration
Documents to help you prepare to migrate your Atlassian Server or Data Center products.
Move customers with mismatched account types
The capability to move Jira Service Management data from one instance of your Jira Cloud to another is only available to customers who’ve signed up for our Early Access Program (EAP).
When you move customers from one instance of your Jira to another, it’s possible that some of your customers' email addresses are associated with different account types in those instances. Learn more about different customer account types
If you have customers whose account types differ between the instances, the migration could result in affected customers losing permission or being unable to access existing requests on the destination instance of Jira. This article explains the migration behavior and the actions you’ll need to take to avoid the issues that are related to mismatched account types for customers.
Possible behavior for customer account movement
Customer email | Account type on source | User with the same email address exists on the destination | Account type on destination | Account type (post-migration) | Recommended post-migration action |
|---|---|---|---|---|---|
jsmith@abc.com | Portal-only | Yes | Atlassian account | Atlassian account | Review group to assign Customer role |
dmurphy@xyz.com | Atlassian account | Yes | Portal-only | Portal-only and Atlassian account | Upgrade portal-only account to Atlassian account |
Review group to assign customer role
When portal-only customers from one instance of Jira to another where the same email addresses already exist as Atlassian accounts, we’ll aggregate the affected accounts into a new user group on the destination instance of Jira. Without the Customer role being assigned to the group, members of the group won’t have access to the Jira Service Management projects on the destination instance that they had access to on the source.
To review and assign the Customer role to the group of customers moved from the source instance of Jira:
Go to your post-migration report folder and open the RequiresAttention.CSV.
Take note of the group name under the Next step column.
From your destination instance of Jira, navigate to admin.atlassian.com.
Under User management, select review now from the banner for imported groups.
Select Review for the group you’ve noted.
Select Approve to assign the Customer role for Jira Service Management.
Learn more about migrating groups and permissions
Upgrade portal-only customers to Atlassian accounts
When customers with Atlassian accounts from the source are moved to the destination where the same email addresses already exist as portal-only accounts, duplicate accounts will exist on the destination: the same email addresses are applied to both portal-only and Atlassian accounts. The affected customers won’t have access to the requests that they previously raised in the Jira Service Management projects on the destination instance of Jira. To avoid identity conflict, we recommend that you only maintain one account type for your customers by upgrading portal-only customers to Atlassian accounts.
To resolve the conflict of account types for the affected customers on the source:
Go to your post-migration report folder and open the RequiresAttention.CSV.
Take note of the customers' email addresses under the Problem column: Found duplicate accounts on destination.
From your destination instance of Jira, navigate to admin.atlassian.com.
For each of your affected customers, migrate their portal-only accounts to Atlassian accounts.
Learn more about migrating portal-only customers to Atlassian accounts
Was this helpful?