DriftSync
Get Pro

Snapshots & rollback

Every apply is preceded by an automatic snapshot — a restore point covering exactly what the release is about to change. If a change turns out wrong, open the History panel and roll it back in one click. There is no separate backup step to remember.

A restore point before every apply

The moment you confirm an apply, DriftSync records the current value of every field the release touches, before writing anything. The snapshot is scoped to the release: it captures precisely the values that are about to change, so a rollback restores them and nothing else. That keeps restore points small, fast, and predictable.

Note

Snapshots cover the configuration and content DriftSync manages. They are not a full-site or database backup — keep your usual backups for that. A snapshot's job is to make a single release reversible.

The History panel

DriftSync → History is the audit trail of every release applied to the site. Each entry records:

  • What changed — the values written, with their before and after.
  • When it was applied, and by which user.
  • The source of the bundle — a file, a direct connection, or a scheduled sync.
  • The attached snapshot, ready to restore.

Rolling back

  1. Open DriftSync → History.
  2. Find the release you want to undo.
  3. Click Roll back. DriftSync restores the snapshot, returning every value the release changed to its previous state.

The rollback is itself recorded in History, so the audit trail stays complete — you can always see that a release was applied and then reverted, and by whom.

Important

Roll back the release, not the clock. A rollback restores the values that release changed; edits you made to other settings afterwards are left as they are. If several releases overlapped the same values, review the diff before rolling an older one back.

Fits the whole loop

Snapshots are the safety net at the heart of the core loop. They protect automated applies too: a scheduled sync and a multi-site fan-out each take their own snapshot before writing, so every site remains one click from its previous state.