User Problem

As an org admin performing a C2C Confluence migration between two linked Confluence Cloud instances, there is not a functionality built into the product to merge two duplicate non-empty personal spaces each with unique sets of data during a migration.

Hypothetical Scenario

• Example user John Smith exists in both source and destination Confluence instance.
• Example user John Smith has a non-empty personal space ~smt in both the source and destination instance.
• John Smith personal space ~smt (source instance) has pages "Page 1", "Page 2", and "Page 3"
• John Smith personal space ~smt (destination instance) has pages "Page 4", "Page 5", and "Page 6"
• 1000+ users exist with this scenario during a migration.

Desired Outcome

• The destination instance would have John Smith’s personal space ~smt include pages “Page 1", "Page 2", and "Page 3", "Page 4", "Page 5", and "Page 6".

Suggested Solutions

Functionality built into the Confluence Cloud Migration + Copy Product Data tooling

Current Workarounds

There are a couple of supported solutions for handling of duplicate space key conflicts as mentioned in Check For Space Key Conflicts,

Check for space key conflicts

Make sure that spaces from your Cloud site don’t have the same space key as the ones you’re migrating. When you migrate a space with a duplicated key, the migration will fail.

If you find conflicts, you can:

• Delete duplicate spaces from your Cloud or Server instance
• Reset your Cloud site
• Exclude spaces from migration

At a high-level the solution which meets the requirements:

If you find conflicts, you can:

• Delete duplicate spaces from your Cloud or Server instance
  • Unless the destination personal space is empty and has not content to be overwritten then deletion of the destination space doesn't seem feasible.

• Reset your Cloud site
  • This doesn't seem feasible given some or all of the destination spaces have content which cannot be overwritten.

• Exclude spaces from migration
  • This is the only feasible option given the scenario to not overwrite the destination data. Excluding the conflicting space keys would be the first step.

Assuming excluding the conflicting space keys from the migration is the first step.

The second step would be performing a manual merge of the content between the source and destination spaces for each user. The second step is not an option built into the Copy Product Data functionality and therefore the second step would need to be done manually. The following article describes the process for each user you would want to follow:

• Import A Confluence Cloud Space

At this time admins would have to import each duplicate personal with a different key and then have to manually move the pages from the newly imported space into the destination spaces.