Preflight

Impact review, conflicts, and warnings

The scan is read-only. Nothing is copied or updated until the review reports that the migration can start and an administrator approves it.

Verified: 28 August 2026 · Field Renamer 0.2.0

Field Renamer impact review showing affected posts, metadata instances, estimate, and conflicts
The impact review separates affected posts from metadata instances and estimates the run time.

What the review counts

The review reports the exact field and definition source, total owned records, primary records, revisions, counts by post type, and estimated raw snapshot bytes. Identification uses the same-post ACF pair: field_name for the value and _field_name = field_key for ownership.

Counts shown in website illustrations are examples, not product benchmarks or a promise about your database.

Blocking conflicts

A migration cannot start when ownership or the destination is ambiguous.

  • Another active ACF field already uses the proposed name.
  • A source pair is missing or duplicated.
  • Affected records already contain destination metadata.
  • Another field key references the destination name.
  • The same field key owns values outside post metadata.
  • Unsupported content types or ambiguous Local JSON are present.

Warnings and advisory code matches

The plugin always warns you to update external references. Its optional code advisory searches active theme directories and active plugin directories for literal occurrences in PHP, JavaScript, JSX, TypeScript, TSX, JSON, HTML, and Twig files.

  • The scan is bounded to 300 readable files, 50 matches, and files no larger than 1 MiB.
  • vendor and node_modules are skipped.
  • It reports the first matching line per file and never rewrites source.
  • It is advisory and does not claim completeness.

Need help with this workflow? Open a support request →