Renaming custom field creates new field

It appears you emailed us in our paid support queue, so I replied there before I saw this message.

For others who may see this, it is a known issue, and the only workaround at the moment is to directly manipulate the data in the database, which of course is outside the scope of support. We do have it logged internally, but it hasn’t been the highest priority, so we don’t have an ETA for it.