Select your target
Choose a supported field, nested subfield, or Flexible Content layout. Unsupported structures are marked before you begin.
A premium plugin for Advanced Custom Fields
Rename ACF fields without losing your data.
Safely update populated Advanced Custom Fields field names without SQL, phpMyAdmin, or risky database edits.
Version 0.2.0 support: Eligible top-level fields, nested subfields, and Flexible Content layout names stored with posts, pages, and custom post types in ACF or ACF PRO 6.3+. Container names, Clone fields, and non-post storage are not supported.
✓ Keep the version you buy✓ Cancel anytime✓ Original data preserved✓ Preview before renaming✓ Verified rollback
property_tagline→listing_taglinefield_6a1c93f4b2e07- Field group
- Property Details
- Field type
- Text
- Storage
wp_postmeta- Affected records
8
✓ 8 records found✓ 0 blocking conflicts↩ Rollback available
Copy values and verifyNothing has been written yet.
The problem
Renaming a field doesn’t move the data behind it.
Change an ACF field name and values saved under the old name stay exactly where they were. Your content looks like it vanished—it’s still in the database, filed under a name nothing is looking for.
The manual approach
· Back up the database
· Find the correct metadata rows
· Write and run SQL
· Avoid touching unrelated fields
· Work out how to undo mistakes
With Field Renamer
✓ Select the field
✓ Review the affected records
✓ Rename safely
✓ Verify the migration
✓ Roll back when needed
How it works01 02 03 04 05
Five steps, and you approve every one of them.
Choose the new name
Enter a valid replacement name and check it against every active ACF field.
Review the impact
See affected records, content types, warnings, and conflicts before anything changes.
Copy and verify
Values are copied in batches and read back before the cutover happens.
Complete, with recovery
The definition switches while the original metadata stays preserved.
Safety by designMatching Preview Copy Preserve Reverse Resume
Six protections that make this different from search-and-replace.
Exact field matching
Values are identified by the stable ACF field key, not by a global replace on the metadata name.
Preview before execution
The exact field, record count, conflicts, and warnings are shown before a single row is written.
Copy before cutover
New metadata is created and verified first. The field definition switches only after verification.
Original data preserved
Old metadata is retained after the rename and is never deleted automatically.
Verified rollback
Reverse the rename while preserving newer content edits made after the migration.
Resumable processing
Interrupted migrations continue from the last verified batch instead of starting over.
Original values
property_taglineCopied values
listing_taglineVerification
8 / 8 matchedField cutover
definition updatedThe interface
Built for people who read the details.
The plugin shows what it found, what it will touch, and what it will preserve. No black-box progress spinner. No vague “success” notice.
See the compatibility reference →Field Renamer · Select a target to rename
FieldNameTypeStatus
Employee Phoneemployee_phoneTextEligible
Member Namemember_nameRepeater subfieldEligible
HeroheroFlex layoutEligible
Specificationsspec_rowsRepeater containerBlocked
Version 0.2.0 support boundary
Check the target before you plan the migration.
Field Renamer handles postmeta-backed ACF field names when it can prove the definition, complete storage path, and stable field-key ownership. Unsupported and uncertain targets are blocked before migration writes begin.
Supported now
Top-level fields
Value-bearing fields stored as ACF value and field-key reference pairs in post metadata.
Nested subfields
Value-bearing Group, Repeater, and Flexible Content subfields, including supported deep nesting.
Flexible Content layouts
Layout names stored in the parent layout sequence, with verified latest-sequence rollback.
Definition sources
Database-managed field groups and unambiguous ACF Local JSON through the guided cutover workflow.
Post-based content and multisite
Posts, pages, custom post types, WooCommerce products and variations, revisions, and autosaves. Multisite is supported one subsite at a time; network-wide migrations are not.
ACF editions
ACF or ACF PRO 6.3 and newer. You install and maintain ACF separately.
Not supported yet
Blocked before anything is writtenContainer field names
Group, Repeater, and Flexible Content container names remain blocked.
Clone ancestry
Fields reached through Clone are refused because one definition can use several storage paths.
Code-registered definitions
Fields registered in PHP cannot use the database or Local JSON definition workflow.
Other metadata stores
Options, users, terms, comments, widgets, menus, blocks, attachments, and WooCommerce HPOS orders.
Field groups and keys
Version 0.2.0 changes field and layout names. It does not rename field groups or stable ACF field keys.
Ambiguous ownership
Duplicate definitions, destination collisions, mixed ownership, or definition drift block the operation.
Simple license
$49 for the first year. Keep what you buy.
One licensed site with every supported version 0.2.0 workflow, updates, and priority support. Renew for $28.91 a year to keep receiving updates and support.
Field Renamer for ACF
$49USD · first year
✓ One licensed site
✓ Installed version keeps working
✓ $28.91 yearly renewal
✓ Cancel anytime
✓ Updates and priority support while active
✓ Migration history and rollback
Buy Field RenamerRenews automatically unless canceledQuestions people ask before buying
Deeper answers live in the documentation.
What happens when I rename an ACF field normally?+
The field definition changes, but values under the old name stay where they are. Your content looks missing because ACF is now looking under a different name.
Does Field Renamer modify my source code?+
No. It scans theme and plugin files read-only for references and flags what you may need to update.
Does it support Repeaters and Flexible Content?+
Yes. Version 0.2.0 supports value-bearing Repeater, Group, and Flexible Content subfields, plus Flexible Content layout names. Renaming the container field itself remains blocked.
Does it support ACF Local JSON?+
Yes. It generates a replacement definition, copies and verifies metadata, waits for you to deploy the file, and verifies the active definition before completion.
Can I roll back a rename?+
Yes. Completed migrations retain a recovery snapshot until you purge it, and retain original metadata until you run guarded cleanup.
Is this a subscription?+
The first year is $49 for one site and includes updates and priority support. It renews at $28.91 per year unless you cancel. If you cancel, the installed version keeps working; updates and priority support end when the license expires.
Rename the field—not your entire database.
Review the impact, preserve existing content, and rename populated ACF fields without touching SQL.
Get Field Renamer — $49