STATECONSOLE

Back up and restore your StateConsole workspace

Save your local StateConsole workspace as a .phbackup file, then check what a restore would replace before confirming. Keep a separate backup of your repositories and practice recovery with disposable data first.

1. Know what your backup includes

A .phbackup is a snapshot of the StateConsole workspace, including saved project paths. Those paths are references to your folders; the folders themselves are not in the backup.

DataBackup coverage
Workspace recordsIncluded: tasks, checklists, copies of task attachments, Inbox items, prompts, settings and saved project paths.
Project filesExcluded: project folders, source code, PROJECT_STATUS.md, other repository files and Git history.

The backup is not encrypted. It can contain text you entered, attachment copies and local paths. Keep it in a trusted location with access limited to people who should see those records. Back up your project files separately.

2. Create and check a backup

  1. In the Windows desktop app, open Settings → Data & recovery.
  2. Choose Create backup and save the .phbackup file to a trusted location.
  3. Wait for Backup created. Check the filename, date and displayed record counts. Keep the file somewhere you can find it again.

A successful save confirms the app created a verified backup file. It does not replace a practice restore. Backup and restore are only available in the desktop app.

3. Inspect before you restore

Restore replaces your current StateConsole data. It does not merge the two workspaces. Tasks and Inbox items added after the selected backup are not in the restored state. If you need your current workspace, make a separate manual backup first.

  1. Under Restore backup, choose Select backup and open the file you intend to restore.
  2. In the preview, check the filename, creation date, compatibility and record counts. Cancel if it is the wrong file or the app rejects it.
  3. Choose Review restore. Confirm with Restore StateConsole data only when you are ready to replace the current workspace.
  4. After the app reports success, choose Reload StateConsole and check the restored records.

Before replacing the database, StateConsole creates a verified recovery snapshot of the workspace you are leaving. It reports the snapshot filename after a successful restore. Project folders and repository files are not changed.

4. Practice a restore with disposable data

Fictional exercise: use a separate Windows test profile with no real workspace data. The results below describe what to check, not a restore that has already been run.

  1. Register a disposable project with a PROJECT_STATUS.md. Save a separate copy of the status file as a reference.
  2. Create a task called Fix CSV export with a checklist item for names containing a comma. Create a workspace backup.
  3. Add Verify large export after the backup, then follow the restore steps and reload the app.
  4. Confirm that Fix CSV export and its checklist are present, and that Verify large export is absent from the restored workspace. Compare PROJECT_STATUS.md with the reference copy to check that it did not change.

5. Restore on another computer

A compatible backup can restore workspace records on another computer. Copy your repositories separately. Any saved path that does not exist on the new computer stays registered but unavailable. StateConsole does not recreate project folders or automatically relink moved ones.

For the difference between the workspace database and project files, see where StateConsole stores your data and the Privacy page.