Issue Summary

When doing a Server-to-Cloud migration, the spaces can fail in the import phase in case there are other spaces being deleted in the cloud simultaneously with the migration.

Steps to Reproduce

You need a large data set to reproduce this.

1. Delete a big space from Confluence Cloud
2. Start the space S2C migration with CCMA.

Expected Results

The migration assistant should identify there are processes running in the cloud that could jeopardy the migration and not start the migration at all, or wait longer for the table locks to be released so the space import would not fail.

Actual Results

The below exception is thrown in the migration logs and in the migration details screen

This connection has been closed.; 
To investigate this error please provide the trace id x to Atlassian support 

Workaround

Ensure there are no spaces being deleted in Confluence Cloud before starting the migration.