Issue Summary

During a Jira Cloud-to-Cloud migration, the field renderers are not migrated as part of the field configuration settings.
Taking a multi-line text field as an example, it'd mean that post-migration, the field renderer will be set to its default value of Default Text Renderer.

Note: This discrepancy is not explicitly called out in the What migrates in a cloud-to-cloud migration for Jira article.

Steps to Reproduce

1. Create a new multi-line text custom field
2. Associate the custom field with a project
3. Modify the field configuration and change the custom field's renderer to Wiki Style Renderer
4. Migrate the project using the Jira C2C Beta Tool
5. Observe the field configuration in the destination site

Expected Results

The field configuration settings are migrated and the field renderer is the same as on the source site

Actual Results

The field configuration settings are not migrated and the field renderer is set to Default Text Renderer

Workaround

Manually modify the field configuration after migration and change the renderer to the correct renderer:

• Specify field behavior - Change a field's renderer