Move OpenClaw to a fresh VPS or new machine.

Host moves fail when state, credentials, workspace files, and active configuration are copied inconsistently. ReClaw gives you one encrypted archive and a restore ledger before the source host is touched.

reclaw backup create --label "Before VPS migration"
reclaw backup list --json

Install ReClaw, authenticate with a scoped API key, then restore the archive to a safe path and verify it before using it in the OpenClaw recovery flow.

curl -fsSL https://reclaw.io/install.sh | sh
reclaw backup restore <backup-id> \
  --verify \
  --output /safe/path/openclaw-backup.tar.gz

VM snapshots are useful infrastructure rollback tools, but they are tied to a machine image and provider. ReClaw is narrower: it focuses on the OpenClaw backup artifact, restore metadata, and client-side encryption so the recovery path can move across hosts.

• Use VM snapshots for whole-server rollback.
• Use private git for source-like workspace files.
• Use ReClaw for encrypted OpenClaw restore points and backup cadence.

Before deleting the source host, prove that the destination can fetch, decrypt, and verify a backup archive. The drill should finish with a verified archive path and a known next OpenClaw import step.