In a C2C migrations of one or more project, all global customfields would be migrated, even if those customfields are not related to the migrated projects.

This causes a problem where there would be a lot of additional unnecessary customfields that were migrated.

We request to provide the ability to scope migrated CFs to be only those used within the migrated projects.

Workaround

1. Perform a C2C migration with one project that includes global custom fields. This will migrate the project along with all global custom fields.
2. Once the migration is complete, use the site optimiser tool to clean up the custom fields.
3. The streamlining tool will provide suggestions for cleanup, as these custom fields are considered stale.