Summary

Currently, when using the Copy product data feature to copy a project between sites, many unused custom fields are copied. This happens even if the custom fields aren’t used by the project, or don’t have a context relevant to the project or its request types. This populates the new site with irrelevant fields, introducing administrative overhead and a potential performance impact.

Suggested solution

The issue could be avoided by adding an option to select which custom fields are copied when creating the copy plan.

Current workarounds

The only workaround presently is to manually delete the unneeded custom fields in the destination process. This is cumbersome, since custom fields must be deleted one at a time.