I'm working with some historic data in a Civi database. For about ten years now we have created a custom field set each year to collect the same two pieces of information via an annual survey. We did it this way rather than using a field set which could store multiple values, because of perceived issues accessing data from multi-value fields (via Views etc.).

So I've now got ten custom field sets, and I'd like to move the custom fields into one larger field set. But the fields from one set have the same machine name as the fields in another set, and so Civi won't let me move them into the same custom field set.

Of course it's easy to change the field label via the UI, but there's no way to edit the machine name of the field. My assumption is that editing custom field names is problematic, otherwise there would probably be a way to do it. So before I get into the database and start editing field names there, I thought it best to ask: will editing field names in the DB break things? Is there a better way to do it, or am I stuck with what I've got?

1 Answer 1


For custom fields it's only problematic if there is custom code that references those field names, including mgd files or install hooks, or if there's some extension that stores that name in the database somewhere else in order to reference it. You'd need to update all those too.

But yes it's just a matter of changing it in the database (civicrm_custom_field.name).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.