Problem statement

After a migration (successful or failed) there is no way to check within the CMA if the source and destination site data is equal for the migration plan. In order to get this a set of manual queries need to be run by an Atlassian MSE after the migration. Being able to see this data automatically directly after the migration has run will enable early detection of issues and subsequent resolution.

Suggested solution

1. Add post migration checks as a diagnostic report to the migration dashboard.

1. Examples of datapoints on this report (from source and destination site for the migration plan that ran) for Jira

1. 1. Total number of users
   2. Total number of workflows
   3. Total number of issues
   4. Total number of projects
   5. Total number of attachments
   6. Total size of attachments per projects
   7. Total number of statuses
   8. Total number of issuetypes
   9. Total number of resolutions
   10. Total number of issue type schemes
   11. Total number of field configuration
   12. Total number of configurations schemes
   13. Total number of custom fields
   14. Total number of screens
   15. Total number of screen schemes
   16. Total number of workflow schemes
   17. Total number of permission schemes
   18. Total number of issue security schemes
   19. Total number of issue security level
   20. Total number of notification schemes
   21. Total number of dashboards

1. 1. Filters shared with ‘Group (Anyone)’
   2. Dashboards shared with ‘Group (Anyone)’
   3. Agile boards shared with ‘Group (Anyone)’

1. 1. Check for assignees of issues that are not present in the CWD Table
   2. Check for reporters of issues that are not present in the CWD User Table
   3. Check for any missing project leads that may have an entry in the app_user table but not present in the IDP directory
   4. Check for any missing comment author that may have an entry in the app_user table but not present in the IDP directory
   5. Check for Post-functions not native to the Cloud in the migrated workflows. (Add-ons and apps etc)
   6. Check for Validators not native to the Cloud in the migrated workflows. (Add-ons and apps etc)
   7. Check for Conditions not native to the Cloud in the migrated workflows. (Add-ons and apps etc)