Recovery

Rollback and snapshot recovery

Normal rollback and Restore original snapshot solve different problems. Both require a completed migration and an unchanged, supported destination definition.

Verified: 28 August 2026 · Field Renamer 0.2.0

Normal rollback preserves later edits

Normal rollback snapshots the current values under the new name and copies those latest values back to the old name. It refuses missing or duplicate current pairs instead of exposing stale data. This is the normal choice after content has changed since cutover.

Confirmation dialog for rolling an ACF field rename back with the latest values
The rollback confirmation identifies both names and explains that the latest values will move back.
Completed rollback with snapshots, copied values, and verification counts
The rollback completes only after the latest values pass read-back verification.

Restore original snapshot

This separate operation uses the immutable values captured before the original rename. It requires typing RESTORE because later edits may no longer be visible. It is unavailable after snapshot purge and refuses to run when new records are missing from the original snapshot.

Original snapshot restore confirmation warning about later edits
Snapshot restore is a separate recovery action because it can replace edits made after the rename.

Use original-snapshot restoration only when you explicitly want the pre-rename values, not merely the old field name.

Recovery prerequisites

Recovery is offered only when the completed destination definition is still active, supported, and not locked by another operation. The plugin also checks exact current pairs and Local JSON ownership before creating the reverse operation.

Need help with this workflow? Open a support request →