Version History & Restore | Custory Changelog

We've added version history so teams can revisit earlier journey states, understand how the map changed over time, and recover work more safely when needed. This gives teams the confidence to explore, revise, and clean things up without worrying that a bad edit will erase useful thinking. Open it from the **Version History** option in the [journey editor](https://app.usecustory.com) menu.

## What's New

**Automatic snapshots.** Custory now saves journey snapshots at session start, session end, autosave points, milestone moments, and manual saves — giving teams a stronger safety net while the journey is evolving.

**Version browsing and preview.** You can review earlier versions before restoring them, which makes history more useful than a simple rollback button. Teams can compare where the journey was and decide whether going back is the right move.

**Version labels.** Important versions can be labeled so teams can identify them easily later — useful for workshop outcomes, major reframes, review checkpoints, or "before we changed the structure" milestones.

**Safer restore flow.** Before restoring an older version, Custory saves the current state first. You get a safer path backward without losing the present version in the process.

## Why it matters

Journey maps are living documents, and living documents change a lot. Version History & Restore gives teams more confidence to improve the map without fearing that structure, progress, or previous insight will disappear if they make the wrong edit.

We've added version history so teams can revisit earlier journey states, understand how the map changed over time, and recover work more safely when needed. This gives teams the confidence to explore, revise, and clean things up without worrying that a bad edit will erase useful thinking. Open it from the **Version History** option in the [journey editor](https://app.usecustory.com) menu.

## What's New

**Automatic snapshots.** Custory now saves journey snapshots at session start, session end, autosave points, milestone moments, and manual saves — giving teams a stronger safety net while the journey is evolving.

**Version browsing and preview.** You can review earlier versions before restoring them, which makes history more useful than a simple rollback button. Teams can compare where the journey was and decide whether going back is the right move.

**Version labels.** Important versions can be labeled so teams can identify them easily later — useful for workshop outcomes, major reframes, review checkpoints, or "before we changed the structure" milestones.

**Safer restore flow.** Before restoring an older version, Custory saves the current state first. You get a safer path backward without losing the present version in the process.

## Why it matters

Journey maps are living documents, and living documents change a lot. Version History & Restore gives teams more confidence to improve the map without fearing that structure, progress, or previous insight will disappear if they make the wrong edit.