Problem

When a Confluence group is renamed on the source site, any space permissions previously granted to that group are not carried over to the destination site during space export/import or Cloud-to-Cloud data copy. This happens even if the renamed group appears correctly in the space permission UI before export. The backend continues to hold the old group name in the spacepermissions table, resulting in missing or incorrect group permissions after import.

Environment.

• Confluence Cloud (Enterprise plan)
• Source site: https://kc-at.atlassian.net
• Destination site: Confluence sandbox
• Group renamed: confluence-users → at-confluence-users
• Affected space: 公開情報_旅行事業本部（OPENTRAVEL）

Steps to Reproduce

1. Create a group confluence-users and assign it permissions in a Confluence space.
2. Rename the group to at-confluence-users in Admin UI.
3. Confirm in the space permission UI that the renamed group (at-confluence-users) appears to hold the expected permissions.
4. Export the space (XML export) and import it into another Confluence Cloud site (sandbox or production).
5. Inspect the imported space's permissions.

Expected Results

The imported space should preserve permissions for at-confluence-users, since this group was visible in the UI and expected to be used during the export.

Actual Results

• The imported space unexpectedly assigns permissions to the old group name (confluence-users) — even though this group no longer exists on the source site and was not shown in the UI at export time.
• In the exported file (e.g., spacepermissions.csv.gz), the group name is still recorded as confluence-users.
• The spacepermissions table in the database also reflects the old group name (permgroupname = confluence-users), confirming that the backend did not update the name after the group rename.

Workaround

• Before exporting the space, open the space permission screen, explicitly remove the old group, and re-add the renamed group (at-confluence-users), then save.
• Alternatively, after importing, manually reconfigure space permissions in the destination site.
• Editing the exported XML or CSV files manually is not recommended due to corruption risks.

Notes

• This behavior is not visible in the UI because Confluence now reads from cwd_group, allowing renamed groups to appear correctly on screen, while legacy tables like spacepermissions still store outdated names.
• See related bug: CONFCLOUD-79402 :Group name was not updated for space permission
• A feature request to update group names in page restrictions is tracked in CONFCLOUD-80746
• This bug impacts both space export/import and Cloud site copy processes.