Issue Summary

When migrating spaces using the Confluence migration assistant, the data gets migrated for the spaces followed by the attachments.

If the attachment migration fails, we need to delete the space and re-migrate. This may not be a feasible option for the customer when time and human resources are limited.

An option to migrate attachments after the migration of spaces would be very welcome.

Why this is important

• In some scenarios, users notice the broken attachments days/weeks after the migration. New content have been created and it's not possible to delete the space to just re-migrate the attachments.
• Space deletion is taking very long for large spaces. This is causing delay on the planned migration timeline.

Workaround

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