Renaming a field in Advanced Custom Fields changes its definition, but values already saved on posts can remain under the previous metadata name.<\/p>\n\n
Esumo Field Renamer for ACF supports both before and after renaming, preserving the field key, raw values and metadata row IDs. It is a free developer tool with no account, license key, telemetry or external service.<\/p>\n\n
Workflow<\/strong><\/p>\n\n Before renaming supports native database definitions managed in the ACF editor. It changes only the field-name column and preserves the other field settings. PHP and Local JSON definitions must be renamed in their source first, then migrated with After renaming. Recent operations has its own tab; opening an operation there returns to its details.<\/p>\n\n When a field is renamed through the ACF field editor, the plugin records a suggestion for its previous name. Data migration always requires an explicit action.<\/p>\n\n Supported in 1.0<\/strong><\/p>\n\n Top-level Text, Textarea, Number, Email and URL fields in active field groups explicitly assigned to posts, pages or custom post types. Data belonging to a different ACF field key is skipped. Ambiguous references and occupied destination names block migration, including empty destination values.<\/p>\n\n Nested fields, Repeater, Group, Flexible Content, Clone, ACF Blocks, Options Pages, attachments, revisions, users, terms and multisite are outside this version. The plugin does not edit definitions in PHP\/JSON, dynamic names, JavaScript, Twig or meta queries. Test compatibility with any additional ACF extensions.<\/p>\n\n Optional theme references<\/strong><\/p>\n\n Review literal first arguments of get_field(), the_field(), get_field_object(), update_field() and delete_field() in PHP files of the active theme and its parent. Check each file before applying it. Calls use field names, so review their context if multiple field groups share a name. Dynamic, named and namespaced calls need manual review. Symbolic links, vendor and node_modules are excluded.<\/p>\n\n Limits: 2,000 PHP files scanned, 512 KB per file, 50 matching files, and 2 MB of combined before\/after content. Writes require edit_themes permission, allowed file modifications and direct filesystem access. Pause deployments and file edits during the operation. Files are restored separately from database changes. Hash checks refuse later edits, and saved file copies allow recovery after a lost response.<\/p>\n\n The preview checks write access to both the file and its directory. Unwritable files cannot be selected. Permissions are checked again before writing; existing theme permissions are never changed automatically. Replacement files preserve the original mode. Fix ownership\/permissions through your hosting tools or apply the reviewed differences in your code editor.<\/p>\n\n MySQL \/ MariaDB require InnoDB for posts, postmeta and journal tables. SQLite requires the WordPress SQLite Database Integration drop-in 1.8.0 or later.<\/p>\n\n Recovery and data retention<\/strong><\/p>\n\n Operations run in batches of up to 50 posts. Closing the tab stops subsequent requests; reopen the operation to resume. Completed requests remain recorded. Individual post changes and their journal updates use database transactions. On SQLite, each request also runs inside a write transaction.<\/p>\n\n Before-mode rollback restores the native field name and unchanged values. After-mode rollback requires restoring the old name in the source definition first, keeping the same key, type and group. Rollback refuses later edits. Restore selected theme files separately. Resolve any reported difference before resuming, or recover from a full backup.<\/p>\n\n The journal stores state and original metadata in This is an independent plugin by Esumo and is not affiliated with or endorsed by Advanced Custom Fields.<\/p>\n\n\n Yes in Before renaming mode, for native database definitions. For PHP\/JSON sources, rename the definition yourself and use After renaming.<\/p><\/dd>\n Optionally, after reviewing and checking the exact PHP file differences. Supported functions and limits are listed above. Other references require manual changes.<\/p><\/dd>\n The tool checks the hidden ACF field-key reference. Records belonging to another field are skipped; missing, invalid or duplicate references block migration.<\/p><\/dd>\n No. It provides guarded rollback for unchanged migrated records. Keep a full database backup before using the tool.<\/p><\/dd>\n No. Case-only renames are refused because common WordPress database collations do not distinguish those names.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
{prefix}fracf_jobs<\/code> and {prefix}fracf_items<\/code>, and file copies in {prefix}fracf_code<\/code>. Only administrators can use the tool. Metadata responses exclude raw field values; file previews show the relevant code lines to users allowed to edit themes. Journals are retained on deactivation and uninstall. Deleting a closed operation's journal also removes its file backups and rollback ability. Keep database backups and journal access appropriately protected.<\/p>\n\n\n
\n
Does this rename the field definition for me?<\/h3><\/dt>\n
Does it update get_field() calls or templates?<\/h3><\/dt>\n
What if two groups use the same field name?<\/h3><\/dt>\n
Is the journal a full backup?<\/h3><\/dt>\n
Can I rename a field using only different letter case?<\/h3><\/dt>\n
1.0<\/h4>\n\n
\n