Renaming ACF fields, written out properly.
Six guides on what ACF actually stores, what breaks when you rename a populated field, and the safe ways to fix it — including the cases our plugin deliberately refuses to automate. No signup, no gate.
Start here
If you are about to rename a field, or something already went wrong.How to Rename an ACF Field Without Losing Data
The full safe sequence — what ACF actually stores, the queries that move it, and how to prove nothing was lost.
11 min readQuick answerACF Field Data Disappeared After Renaming — How to Get It Back
Your content is almost certainly still in the database. The fastest fix, and the two things not to do while it looks missing.
6 min readCompare approaches
Four ways to do it, and what each one costs you.Reference
How the storage works, and the cases version 0.1.0 will not automate.Renaming ACF Repeater and Flexible Content Fields
The case we block in v1, why automating it is not safe, and the manual path if you have to do it anyway.
6 min readQuick answerACF Field Name vs Field Key: What Actually Stores Your Data
Two identifiers, two rows, one common misunderstanding — and why the difference is what makes a safe rename possible.
5 min readWalkthroughRenaming ACF Fields When You Use Local JSON
A rename becomes a code change and a data change. The order they must happen in, per environment.
9 min readOr skip the queries entirely.
Everything above is free and works. Field Renamer is for when the field is populated, the site belongs to a client, and you would rather see the affected record count than find out afterwards.