Issue Summary

When a customer selects 1 space (a personal space) and the scoping resolves to 1 user, the CCMA completion UI displays:

• ✅ Migrated 1 user and 0 groups
• ✅ Migrated 1 space

However, because the scoped user belongs to the confluence-users group (containing ~1,156 members), the entire group and all its members are migrated. The UI does not reflect this — neither at the review stage nor on the completion screen.

Steps to Reproduce

1. In a Confluence Data Center instance, select a personal space where the owner belongs to a large group (e.g., confluence-users with ~1,156 members).
2. In CCMA, create a migration plan → Select "Only users and groups with permissions on selected spaces".
3. Select only the personal space (1 space, scopes to 1 user).
4. Review screen shows: 1 space, 1 user.
5. Run the migration.

• 6. On completion, UI shows "Migrated 1 user and 0 groups" — but all ~1,156 group members are actually migrated.

Expected Results

1. Accurate completion summary — The migration completion screen should display the actual total number of users and groups migrated (e.g., "Migrated 1,156 users and 1 group").
2. Pre-migration warning — Before migration execution, if scoped users belong to groups with additional members, a warning should be displayed: "The selected user(s) belong to groups containing X additional members. These members will also be migrated to preserve group integrity."

• 3. Parity with JCMA — JCMA provides the option "Migrate users and groups separately" which allows customers to control this behaviour. CCMA currently lacks this option.

Actual Results

• Migration completion screen shows: "Migrated 1 user and 0 groups"{}
• Actual users migrated: 1,156 (all members of confluence-users group)
• No pre-migration warning that group membership cascading will increase the user count
• Customer is misled into believing only 1 user was migrated

Workaround

1. Create a new group and provide license access to it.
2. Remove the user intended to be migrated from current groups (e.g., confluence-users).
3. Add the user to the new group where no other users are added.
4. Perform the migration — only the single user will be taken to cloud.

 

• CCMA version: 3.13.8
• Confluence version: 10.2.2
• Migration type: Server-to-Cloud (S2C)

 

Impact

• Customer trust — Misleading UI erodes confidence in the migration tool's accuracy.
• Licensing/billing concerns — Customers unknowingly migrate hundreds/thousands of users which may affect cloud subscription user counts.
• No rollback awareness — Customer has no indication that additional users were migrated until they check the destination site.

Suggested Improvements

 

 
1|Display accurate user/group count on migration completion screen|High|
2|Add a pre-migration warning when group membership cascading will increase user count beyond what's visually scoped|High|
3|Add "Migrate users and groups separately" option to CCMA (parity with JCMA)|Medium|
4|Show a breakdown in the Review step: "1 user scoped → belongs to X groups → Y total users will be migrated"|Medium|

Design Behaviour Reference

This is by-design per How Confluence users and groups are migrated:

When you select this option, we also migrate the groups to which these users are added and have space permissions.

The MIG is not about changing the migration logic — it's about the UI accurately representing what actually happens and providing appropriate warnings.

Workaround Provided to Customer

1. Create a new group and provide license access to it.
2. Remove the user intended to be migrated from current groups (e.g., confluence-users).
3. Add the user to the new group where no other users are added.
4. Perform the migration — only the single user will be taken to cloud.

Related Ticket

MOVE-1825007

Web link

Title: MOVE-1825007 - Customer Ticket

URL: https://atlassiansupport.atlassian.net/browse/MOVE-1825007