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.

Get Field Renamer — $49 See how it works

✓ One-time purchase✓ No subscription✓ Original data preserved✓ Preview before renaming✓ Verified rollback

Field Renamer · Review the impactwp-admin

employee_phone→contact_phonefield_6a1c93f4b2e07

Field group: Employee Details
Field type: Text
Storage: wp_postmeta
Affected records: 1,284

✓ 1,284 records found! 2 conflicts flagged↩ 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 works

Five steps, and you approve every one of them.

Select your field

Choose an eligible top-level ACF field. Unsupported fields are marked before you begin.

Choose the new name

Enter a replacement name and validate it against the field group.

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 design

Six protections that make this different from search-and-replace.

Matching

Exact field matching

Values are identified by the stable ACF field key, not by a global replace on the metadata name.

Preview

Preview before execution

The exact field, record count, conflicts, and warnings are shown before a single row is written.

Copy

Copy before cutover

New metadata is created and verified first. The field definition switches only after verification.

Preserve

Original data preserved

Old metadata is retained after the rename and is never deleted automatically.

Reverse

Verified rollback

Reverse the rename while preserving newer content edits made after the migration.

Resume

Resumable processing

Interrupted migrations continue from the last verified batch instead of starting over.

Original valuesemployee_phone

Copied valuescontact_phone

Verification1,282 / 1,282 matched

Field cutoverdefinition updated

The 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 field to rename

FieldNameTypeStatus

Employee Phoneemployee_phoneTextEligible

Job Titleemp_roleTextEligible

Care Instructionscare_infoWYSIWYGLocal JSON

Specificationsspec_rowsRepeaterNested

Simple license

$49 once. Use it forever.

One production site, its staging and development copies, all supported workflows, and one year of priority support.

Field Renamer for ACF

$49USD · one-time

✓ Permanent use

✓ No automatic renewal

✓ Updates for the supported lifetime

✓ One year of priority support

✓ Migration history and rollback

Buy Field Renamer14-day money-back guarantee

Questions 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?+

Not in version 1. Nested fields are detected and blocked before any data changes.

Does it support ACF Local JSON?+

Yes, through a guided workflow that generates a replacement definition, waits for deployment, verifies it, and then migrates the data.

Can I roll back a rename?+

Yes. Completed migrations keep a snapshot and the original metadata, with rollback available for 90 days by default.

Is this a subscription?+

$49 once for one site, with no renewal. Updates continue for the supported lifetime of the product.

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