Migration
Move between SiroPing instances without reconfiguring anything — your workspaces, projects, monitors, alert channels and credentials come with you.
Trial → your own server (the common case)
- Export from the source instance:
bash python manage.py export_migration --user <you> --output siroping-export.json(Add--passphrase 'secret'to encrypt the file for transit.) - Install SiroPing on your server — see Installation.
- Import on the destination:
bash python manage.py import_migration --file siroping-export.json --owner <you>
What is migrated
| Migrated | Not migrated (by design) |
|---|---|
| Workspaces (owner) | Users / memberships |
| Projects | Incidents |
| Monitors (all types) | Check history |
| Notification channels | Audit / email logs |
| Settings (mail/webhook/telegram) |
Credentials (login passwords, channel tokens) are decrypted on export and re-encrypted under the destination's key on import.
NOTE
If the destination already has a workspace with the same slug, the imported one gets
a suffix (`-1`, `-2`, …) — nothing is overwritten.
Between two self-hosted servers
Same commands: export on the old server, install + import on the new one. Point DNS/HTTPS to the new server; keep the old one running until you've verified.
Security
- Use
--passphrasewhen the file travels off the server (Fernet-encrypted). - The export file contains your monitor config — treat it as secret.
- Credentials never appear as plaintext at rest on the destination.