Backup
A new machine, with your people intact.
Settings → Backup & Restore writes one dated folder to a drive you pick, and reads it back on another computer.
What travels: the database, meaning your rosters, jobs, MatchID results, catalog index and settings, plus the indexed headshots and their reference faces. That last part is what makes a restore useful. Without the faces you would come back with a list of names and no way to recognize anyone.
What does not: your photos. The originals stay on their own drives, and the catalog points at them again once they are connected. Your license, your FTP passwords and your Cloud sign-in also stay on the machine they were entered on. A license is per computer, so the new one activates on its own key.
Previews
Optional, and worth thinking about
You can mirror the catalog previews alongside the backup. They live in one shared folder that is updated in place rather than copied again each time, so repeat backups do not grow it. Leave it off and previews rebuild from your drives with Regenerate, which costs time rather than data.
GalleryID checks whether the drive can actually hold it first, and warns you when a drive’s formatting would make thousands of small preview files take far more room there than they do here.
Automatic backup
Bind one drive and forget it
Point it at a folder on an external drive and it backs up whenever that drive is connected: at most once per interval, and not at all when nothing has changed. The drive is remembered by its identity rather than its name, so renaming it does not break the binding. Choose every connect, daily or weekly, and how many dated backups to keep before the oldest rotates out.
Restoring
Staged, then applied on relaunch
Pick a backup folder and it is staged rather than applied on the spot. Relaunch and it takes effect. Your current database and headshots are kept beside it as .pre-restore copies, so the whole thing is reversible, and a staged restore can be cancelled before you relaunch.
It works across computers. Stored paths are rewritten for the machine you are restoring onto, which is what makes this a migration tool and not only a safety net.