Last updated Feb 4, 2022

Rate this page:

Re-run an app migration

This page talks about how you can re-run your app migration. You may want to re-run an app migration in the following scenarios:

  • to migrate a very complex project or space which involves possible failed app migrations
  • to run integration tests

The above scenarios are only a few examples, and is not limited to, why you may need to re-run app migration.

How to re-run the app migration

After you have run a migration plan in your assistant (like selecting a cloud instance and entities to migrate), re-run the app migration using the following URL: rest/migration/latest/app-migration/rerun/<planId>. This operation can be repeated multiple times as required.

Replace planId with your own unique planID. You can find your planId in the URL when you view the plan details.

See an example for Confluence

The following is an example of a URL where the planId is e508b1f0-364d-4a0f-8c66-198ac67b2a2b.

curl -u admin:admin -X GET "http://localhost:1990/confluence/rest/migration/latest/app-migration/rerun/e508b1f0-364d-4a0f-8c66-198ac67b2a2b"

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.


  • The re-run method explained on this page will not re-migrate product-related data (projects, spaces, users, etc) that were originally migrated.
  • The lifespan of the original mapping (when the plan was first run) won't be affected by an app migration re-run.
  • The rest/migration/latest/app-migration/rerun/<planId> endpoint simply creates new transfers and invokes all the local listeners each time a migration is re-run.

Rate this page: