Merge, update or deactivate users during your transition to Jira or Confluence Cloud

[#1]

Hi Atlassian Community!

I’m Akshay, a Product Manager with Atlassian. Our team owns all Atlassian data management tools, and helps customers plan and run their migrations and transformations. Today, we’re excited to share about a new capability that can simplify your move to cloud.

What’s new?

We’ve introduced a new capability in the Jira Cloud Migration Assistant (JCMA) and Confluence Cloud Migration Assistant (CCMA) that helps manage your user base during a cloud transition. When running a migration, and trying to fix your user base, you can perform all complex changes in one go, by downloading the list of all users as a CSV. You can:

• Merge users: Combine duplicate accounts.

• Update email addresses: Correct any invalid email addresses.

• Deactivate users: Disable user accounts that are no longer required after migrating.

Note: This new capability builds on the existing functionality of fixing invalid or duplicated emails in Simple mode (read more about this here).

How it works?

1. Navigate to the Assess and Prepare Users section in the Jira or Confluence Cloud Migration Assistant.

2. Choose between Simple and Advanced mode to fix users with invalid or duplicate emails

   • Simple mode: Allows you to choose a fix and apply it for all affected users.

   • Advanced mode: Allows you to download the user list as a CSV, make updates at an individual user level, and re-upload it to apply the changes.

This capability is available with JCMA version 1.11.7 and above and CCMA version 3.10.2 and above. To learn more, visit our support page.

We’re here to support in your migration journey. If you have any questions, please reply to this post, or contact us.

Regards,

Akshay Johri
Product Manager, Atlassian

[Darryl Lee]

Hi @Akshay Johri - would this address the issue where users who have been Deactivated in the IdP (in our case Azure AD) end up showing up on Confluence pages they created as "Former user (Deleted)"?

That issue really annoyed me and a lot of my users, and apparently the only way to prevent this is to "reactivate them (or the directory) before migrating."?

(https://support.atlassian.com/migration/docs/migrate-users-and-groups/#Deleted-or-inactive-users-and-directories)

[Akshay Johri]

Hi @Darryl Lee. This feature will not address the issue you're facing, as Deactivated users won't be present in the CSV file described in this solution. I would recommend to follow the existing guidance for now.

[Akshay Johri]

Hi. We would love to hear your feedback on this capability. We're also looking at suggesting accounts with same username (but different email addresses) as duplicate accounts. Do you think it would be useful?

[Islam Ziane]

Using this feature, can we migrate a jira site from org1 with users having emails in @domaine1.com to another org2 that have already same users in @domaine2.com. Note that we want to keep both accounts data for each user, should we go with Advanced mode and merge duplicate accounts ?