Issue Summary

Changes to the Group Names made after the Migration plan is created and Saved doesn't reflect on the Destination Cloud Site Confluence Permissions after Migration.
The renamed groups are migrated as New Groups to the Destination, but they are not associated with the Space permissions in Confluence.

Cloud to Cloud Migration - Copy Product Data

Steps to Reproduce

To reproduce the issue make sure to follow all 3 parts below:

First Part:

1. Create a Migration Plan for couple of Spaces from Source Cloud Site to the Target.
2. Select Source and Destination Cloud site and provide a Migration Plan Name.
3. Select Spaces to Migration. Make sure the Group Names that you are going to change are part of these Space Permissions / Access.
4. Select options Users and groups associated with selected spaces under Users, groups, and teams
5. Users with their groups or Users and groups separately Under Group memberships
6. Validate the Plan. Merge Duplicate Groups to make sure Groups with same name merge together on Destination.
7. Click Next, but Do Not Click "Copy Data".
8. Click on Close and go back to the List of Migration plans. Now the Plan is created, Validated and Saved.

Second Part:

1. Change the group names. For Eg: Change "administrators" to "administrators-atlas-change" and "confluence-users" to "confluence-users-atlas-change". Save these group Name changes.
2. Go to "All Spaces" > select the space that you have added in the Migration Plan > Go to "Space Settings" > Expand "Space Access" and select "Groups".
3. Confirm the Group Name Changes are reflected in the Permissions of the Confluence Space.

Third Part:

1. Go back to the Migration Plan.
2. Validate the Plan again (A couple of times to make sure no changes are left out or undetected on these spaces".
3. Run the Migration Plan.
4. Observe the results Post Migration on the Destination site. Go to "All Spaces" > select the space that you have migrated > Go to "Space Settings" > Expand "Space Access" and select "Groups".

Expected Results

• Groups with New Group Names are added to the Permission of the Space under Space Settings.

Actual Results

• Groups with New group names are Migrated to the Destination Cloud Site. You can confirm this from admin.atlassian.com > "Directory" > "Groups".
• When Checking the Space Settings > Space Access > Groups, The Renamed Groups are not associated with the Space Permissions.
• The Old Space Group Names are added to the Space Permission as if the changes to the groups are not considered. This can elevate User Permissions for the users present in the Old Groups and they can access the space.
• This is causing security concerns due to unwanted groups being given access to the SPACE.

Workaround

1. Remove the Incorrect Groups from SPACE Permissions and Add the New Renamed Groups in the Space Permissions. (This is not feasible when there are many spaces involved in the Migration).
2. Group Names need to changed before the Migration Plan is created and saved. If the Groups name is changed prior to creating the Plan, then during Validation step the Plan picks the New groups names and Migrates them successfully.

However, this is a BUG because it does not warn the user about how the Group Name changes would affect their Migration. Neither, the tool picks up the changes on the Group Names and their association with the Confluence Spaces during re-validation of the same Migration Plan.