Compatibility

What version 1 supports

Unsupported fields are detected and blocked before any data is changed—the plugin never discovers a limitation mid-migration.

CapabilityStatusNotes

Top-level ACF fieldsSupportedText, textarea, number, select, WYSIWYG, date, relationship, and similar single-value fields.

Database-managed field groupsSupportedRenamed directly, with preview and rollback.

ACF Local JSON field groupsGuidedYou deploy the generated definition; the plugin verifies it before migrating data.

Posts, pages, custom post typesSupportedAnything storing ACF values in wp_postmeta.

WooCommerce productsSupportedIncludes variations that store values as post metadata.

Revisions and autosavesSupportedMigrated alongside primary records when exact field-key references exist.

Multisite subsitesSupportedOne subsite at a time. Network-wide batch renaming is not in v1.

Repeater fieldsNot in v1Detected and blocked before any data is changed.

Flexible Content fieldsNot in v1Detected and blocked before any data is changed.

Group and Clone fieldsNot in v1Nested naming makes safe key matching unreliable in v1.

Options pages and term/user metaNot in v1Storage lives outside wp_postmeta. Planned for a later release.

Renaming field groups or keysOut of scopeField Renamer changes field names only. Field keys stay stable.

6.2 or newer
PHP 7.4 or newer
Individual multisite subsites supported

ACF and ACF PRO 6.3 or newer
Top-level, postmeta-backed fields
Nested and PHP-registered fields are blocked