Some customers have dedicated and seperate instances for production, test and development. Here the current setting for matching custom fields upon import, based on identical type and name makes perfect sense.
Some customers duplicate the production environment and use this as a test or development system. This helps ensure with easy efforts that the systems are identical (which is a basic requirement of PC. In this case, existing custom fields already have the identical custom field ID’s. Here it makes much more sense to match the fields based on this.
My suggestion is, implement a selector, on “how custom fields should be matched”
- either by custom field ID
- or by type and name
which then results in a merge on the changes (CF Contexts, Translations, Screens etc.) could make many customers happy, and many lifes easier.