Before switching servers, Hermes Agent prioritizes generating backup packages with official hermes backup and then restoring them on the new machine with hermes import. Don't just copy the repository directory, as the configurations, sessions, skills, and keys that really matter are usually ~/.hermes/.
What to confirm before migrating
- Old machines can operate
hermes doctornormally, avoiding the direct relocation of bad environments. - Clarify whether you want to migrate keys, sessions, skills, crons, and profiles.
- The new machine system is officially supported: Linux, macOS, WSL2 or Termux.
- If it involves a Docker/SSH/Modal backend, make sure that external resources are also accessible on the new machine.
Basic migration process
- Older machines perform
hermes backup, saving the resulting zip or archive file. - Transfer the backup package to a safe location on the new machine.
- The new machine installed Hermes before performing the
hermes import 备份文件. - Run
hermes doctorandhermes statusto check the recovery results.
Be extra careful with your keys
Backups may contain sensitive information such as API keys, bot tokens, email authorization codes, and webhook secrets. Do not use public links when transferring, and rotate key tokens after the migration is completed, especially if the old machine is no longer controlled or has been exposed to multiple people.
If you only want to migrate an independent identity, you can also consider profile export/import. Use backup/import for whole machine migration, and profile export for individual role migration, which is clearer.
