Issue Summary

Say you migrate 1000 spaces and 10 apps in the same migration plan. Now from these 1000 spaces, 1 fail. Because of this, the app's migration cannot be triggered again and all the 999 spaces that were successfully migrated will not have part of the app data migrated over, and then we will have to wipe the instance and migrate again, because of a single space fail.

Steps to Reproduce

1. Create a plan to migrate via CCMA with app migration.
2. Start the process (Pre-checks / Users&Groups / Attachment upload / Space Export&Import).
3. App migration failed because of one or more spaces that failed.
4. Solve the dependencies found on the support zip, wipe the cloud site and start over.

Expected Results

An easy way to re-trigger only the app migration framework after adjusting the spaces that failed to migrate after using as a base the support zip error logs.

Actual Results

The way CCMA works is that it migrates in phases: first the pre-checks, then users and groups, the attachments and spaces (export/import), and lastly the apps. As we don't have control to trigger the app migration again, a new plan to migrate needs to be created and the cloud site wiped to start over.

Workaround

Use the Re-run an app migration API. However the same seems to be more useful when all the spaces were migrated successfully and only the app has failed for any reason.
Also, this method offers the following advantages:

• You only need to create one plan and re-run it as many times as required.
• You can re-run the app migration using testing tools like Postman or Command-line, without having to re-run a fresh migration from the Cloud Migration Assistant user interface each time you want to test the app migration.