Rename nested ACF subfields

Supported nested targets

You can rename value-bearing children inside Group, Repeater, and Flexible Content fields. Deep combinations such as Group → Repeater → Flexible Content are supported when Field Renamer can prove the complete metadata path and field-key ownership.

• A Group child uses the parent and child names in its stored metadata key.
• A Repeater child may appear once per stored row.
• A Flexible Content child is matched by row and field key; the layout name is not part of its metadata key.

Posts and metadata instances are different counts

A post may contain several Repeater rows or Flexible Content rows. The impact review reports affected posts and exact metadata instances as separate numbers. Snapshot, copy, verification, and cleanup use the instance count.

Container names remain blocked

Field Renamer does not rename Group, Repeater, or Flexible Content container field names. Changing a container rewrites every descendant metadata path and needs a separate migration model. Clone ancestry is also refused because one definition can be reused through several storage paths.

Choose a value-bearing child or a Flexible Content layout target. Do not edit the blocked container name by hand on a populated site.

Rollback uses the same complete path

Normal rollback identifies the current child definition and exact destination pairs before it creates a reverse operation. It copies the latest values back to the previous path, verifies them, and keeps the reverse snapshot for recovery.