Exported custom fields
Project Configurator exports configuration objects which are used directly or indirectly by the exported project(s). As any field configuration in Jira contains all system and custom fields, and every project uses at least one field configuration, the previous rule means all custom fields will be exported.
...
It is used in any of the project’s permission, notification, or issue security scheme
OR
It is used in any workflow used by the project
OR
(It is visible in at least one field configuration used by the project
AND
It is included in at least one screen used by the project)
OR
It has a value set in any of the issues of the project
Filtering option
Since version 2.2.3 of Project Configurator, there is an intermediate filtering option: "Only those used in projects (no values considered).” This option will export only custom fields used by the exported projects, but it ignores whether there are values set for those fields in issues of the exported projects.
...
This intermediate option is intended only for users with large databases, and when the query evaluating the condition about custom field values might have an excessive impact on times required for exporting. In all other cases, its use is not recommended.
Custom Fields Used in Dashboard Gadgetsfields used in dashboard gadgets
If you are exporting dashboards, and a gadget is exported that uses a given custom field (for example, it is one of the fields included in the columns for the Assigned to Me Gadget), this custom field will be included in the export, regardless if it is used by an exported project or not.
...