~5 minute read

Branch Backup & Restore

Download a full branch backup and restore it later, including nodes, views, snapshots, wiki content, and images.

Use backup and restore to safely move or recover everything in a branch, including diagram data and images.

Back up a branch, review the replacement warning and target, then restore to replace the target branch's current contents.

What gets backed up

A branch backup includes:

  • nodes and edges,
  • views,
  • history snapshots,
  • wiki pages and links,
  • design review threads and comments,
  • planning dependencies,
  • node metadata,
  • branch-linked PR metadata,
  • images referenced by the branch.

Create a backup file

  1. Open the branch you want to export.
  2. Select the History tab to open its Timeline panel.
  3. Click Backup.
  4. Save the downloaded .json file.

Restore a backup file

Warning: Restoring replaces the target branch's full current state with the contents of the backup. It is not a merge; branch data not present in the backup will be replaced. Before continuing, create a snapshot or download a backup of the current state.

  1. Open the target branch.
  2. Select the History tab to open its Timeline panel.
  3. Click Restore.
  4. Choose a backup .json file. Restore starts immediately; no second confirmation dialog appears.
  5. Wait for the success message before continuing.

After restore, Nodeable refreshes the branch view so you can continue working with restored data.

Important behavior

  • Backup and restore are branch-scoped (you cannot merge multiple backups in one restore action).
  • Large branches with many embedded images may produce large backup files.

Recommended workflow

Before restoring:

  1. Create a new snapshot of the current branch.
  2. Optionally download a backup of current state.
  3. Run restore.

This gives you a quick fallback path if you need to return to the pre-restore version.

For creating, forking, and managing branches, see Branch Management.

We use cookies to understand how Nexus is used, via Google Analytics. Questions? Visit our contact page.