Issue Summary

CCMA space migration can result in an error if userKeys are detected that contain non-alphanumeric characters.  One way this issue can arise is if a Confluence cloud backup is imported into a Confluence DataCenter instance. Users in the Confluence cloud backup may have userKeys that match their Atlassian Account ID values. These values can contain non-alphanumeric characters such as colons and dashes.

This is reproducible on Data Center:

Steps to Reproduce

1. Create a Confluence cloud site.
2. Create a space with a page. For this test, ensure that the user used for this activity has a user_mapping.user_key value that contains a colon or dash.
3. Go to Confluence Settings > Backup Manager.
4. Generate a Backup for Server.
5. Delete the space that you created via Step 2 above so that you can re-migrate it later.
6. Create a Confluence DataCenter environment and import your backup from the cloud site.
7. Use CCMA to migrate the space from Step 2 to a cloud site (either the original cloud site or any other cloud site).

I replicated this issue using CCMA 3.4.1.

Expected Results

The users, groups, and space will migrate successfully.

Actual Results

Users and groups migrate successfully.

The space migration generates this error message:

Failed to export [cloudId=<CLOUDID_VALUE>,fileId=<FILEID_VALUE>,spaceKey=TEST]. Error: Invalid characters in userKeys . Only alphanumeric characters are allowed.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available