Summary

The What gets migrated with the Jira Cloud Migration Assistant documentation has a section called What isn't migrated pointing out that Select List (multiple choice) Custom Fields doesn't get migrated. These type of fields are widely leveraged in Server environments.

Suggestion

To enhance Jira Cloud Migration Assistant (JCMA) so it does migrate such custom fields or to avoid failing the entire migration in case the tool run across any of these.

Current Scenario

JCMA will throw the following error on logs and fail the entire migration when attempting to migrate a Board that has a Select List (multiple choice) Custom Field:

2020-04-10 21:40:26.474 ERROR TESTPROJECT project-import We couldn't import Board 'XXX'. Reason: query: The option 'YYY' for field 'ZZZ' does not exist..

Expected Scenario(s)

• Administrators are presented with a message in the migration plan (or in the logs) stating which boards/projects to remove the Custom Field from before migrating.
• Administrators can migrate all boards/projects without their Custom Fields.
• Administrators can migrate all boards/projects with their Custom Fields.

Workaround

So the entire migration doesn't fail, identify these Custom Fields before hand and manually re-create them on Cloud before the migration runs. The migration won't fail, but data related to this Custom Field won't be migrated either. At the end, one would still need to use CSV Import to import the data behind these specific fields to Cloud.