Merge user accounts

Account merge is a data management tool in Atlassian Administration that allows you to combine two separate user accounts into a single target account by consolidating user data, such as work item history in Jira or page edits in Confluence, from a source account into a target account in Atlassian Cloud.

For instance, if an employee has two accounts due to a company acquisition, data migration, or a change in email domain or two different accounts in Jira and Jira Service Management, a site admin can merge the "source" account into the "target" account. All of the user’s assigned tasks and contributions will then be associated with the single target account.

Account merge can help reduce operational risk and manual cleanup after migrating data between sites, and ensures that your users maintain a consistent history across Atlassian apps without having to manage duplicate identities.

Entities covered

When accounts are merged, the following entities are updated:

制限事項

Entities we do not support

Account merge does not move or update the following entities. Their existing values are preserved on the source account and are not transferred to the target account:

• Issue History

• 課題セキュリティスキーム

• 監査ログ

• Group Membership

• All Jira Service Management (JSM) fields

Merging users with the same email is not supported

The email addresses in the source and target accounts must be unique.

User references in Jira text fields are not supported

Text fields, such as description and custom text fields, in Jira cannot be updated.

Each source account should only map to one target account

You can only add a source account once in a CSV file. Each source account must map to only one target user. However, you can map multiple source accounts to a single target account.

For instance, let’s say ABC@atlassian.com and 123@atlassian.com are source accounts and XYZ@atlassian.com and 100@atlassian.com are target accounts.

• You can map ABC@atlassian.com and 123@atlassian.com to XYZ@atlassian.com.

• You can’t map ABC@atlassian.com to both XYZ@atlassian.com and 100@atlassian.com.

Account level info, SAML, and SCIM provisioning

Merging accounts only moves product data and contributions. It does not merge, transfer, or update identity provider (IdP) configurations, SCIM provisioning links, or SAML SSO settings, or any account-level details such as email addresses or other profile info. If either account is SCIM-provisioned, identity provider sync will continue to target the account associated with the email address in your directory — regardless of which account data was merged into. To manage how account sync actions behave, see How to Manage Account Sync Actions in Atlassian Admin Hub.

はじめる前に

To be able to merge user accounts, you’ll need to have:

• Organization admin permissions so you can access Atlassian Administration.

• Jira and Confluence admin permissions to access the sites where users' information currently resides.

Steps to merge user accounts

To merge user accounts:

1. Go to Atlassian Administration, and select Data management from the navigation pane.

2. Locate the cloud site where you want to merge user data.

3. Select Actions (⋯), then select Start an account merge.

4. Select Download template to get a CSV file. Read about the information required in the CSV

5. Fill the CSV with your source and target user details, then select Upload CSV. Note: The CSV file you upload must not exceed 7 MB. If the file exceeds this size limit, it will not be accepted. To work around this, split your mappings across multiple CSV files and run separate merge operations.

6. Select Run operation.

7. Monitor the progress on the homepage. You can select Actions (⋯), then Download latest results to track progress.

Once the data is merged, the status will change to Complete. Select Actions (⋯), then Download results to view the success or failure report.

If you’d like to rollback changes, contact support.

Information required to merge users

To merge users, you’ll need to provide the following information in the CSV file. The CSV file must be encoded in UTF-8 format. Files in other encoding formats (e.g., UTF-16, ANSI) will not be accepted and will result in an error. If the file format is incorrect or is missing required columns, you’ll be prompted to fix the errors and upload the file again

If the status of the account merge comes up as SKIPPED, it may be because duplicate email addresses were found. AAID-based merge is currently supported only for Jira and must be performed through our Support team. The self-serve UI does not support AAID-based merge yet. If you encounter SKIPPED rows, contact Atlassian Support for assistance with AAID-based merging. Read how to find your Atlassian Account ID

User ID from the source email

The user ID from the email address of the account you want to merge from. This account's data will be moved to the target account. If the status of the account merge comes up a SKIPPED, use your Atlassian Account ID (AAID) instead of your user ID and try merging accounts once again. Read how to find your Atlassian Account ID

User ID in the target account

The user ID from the email address of the account you want to merge data into. This account will remain active and inherit the data from the source account. If the status of the account merge comes up a SKIPPED, use your Atlassian Account ID (AAID) instead of your user ID and try merging accounts once again. Read how to find your Atlassian Account ID

Product selection

Select the apps the merge applies to (Jira, Confluence, or both). The tool routes requests only to the apps supported in your specific tenant.