Backup & Restore
Conduit supports both local and cloud backup to protect your vault data. Backups are encrypted independently from the vault itself using AES-256-GCM with a domain-separated key.
Flush before copying
If you plan to manually copy the .conduit vault file, use Manual Save (Cmd/Ctrl+S or File > Vault Management > Save Vault) first. This forces a WAL checkpoint so all recent changes are written into the main file.
Local Backup
Local backup writes encrypted copies of your vault to a folder on your machine:
- Encryption — AES-256-GCM with a domain-separated key (independent from vault encryption).
- Backup folder — user-selectable via a native OS folder picker.
- Automatic backup — triggered on vault changes with a 5-second debounce to avoid excessive writes.
- Manual backup — use the “Backup Now” button to create an immediate backup.
Local Retention
Configure a retention period (default 30 days) for local backups. Backups older than the retention period are automatically pruned. Pruning runs periodically every 6 hours. You can also delete individual backup files from the backup list.
Chat History
Optionally include chat history alongside your vault backup. When enabled, AI chat conversations are backed up together with your connection and credential data.
Cloud Backup
Paid tier required
Cloud backup requires a Conduit account and a paid subscription tier.
Cloud backup syncs your encrypted vault to Conduit's secure cloud:
- Automatic sync — periodic automatic sync keeps your cloud backup current.
- Manual sync — trigger a sync manually at any time.
- Incremental sync — mutation tracking ensures only changed data is uploaded.
Cloud Retention by Tier
Cloud backup retention varies by subscription tier. Backups older than the retention period are automatically pruned.
| Tier | Retention |
|---|---|
| Free | 1 day |
| Pro | 14 days |
| Team | 6 months |
Restore
Restore from a cloud backup by providing your master password for validation. The cloud sync status indicator shows the current state: idle, syncing, synced, or error.
Vault Export & Import
Conduit supports exporting and importing vault data via encrypted .conduit-export files. This is useful for migrating vaults between devices, sharing vault data with team members, or creating portable backups.
Exporting
- Export your full vault or individual folders from the vault switcher menu or folder context menu.
- You provide a passphrase to encrypt the export file. Encryption uses PBKDF2-SHA256 (600,000 iterations) with AES-256-GCM.
- The encryption key is domain-separated from vault and backup encryption, ensuring key reuse is not possible.
Importing
- Import from File > Import > From Conduit Export or the vault switcher menu.
- Enter the passphrase to decrypt, then preview before importing — see the source vault name, folder tree, and entry type counts.
- Choose to import into the vault root or a specific target folder.
- All imported entries receive fresh UUIDs, so re-importing the same file creates new entries without conflicts.
- Credential references are automatically remapped for included credentials, or cleared if the referenced credential was not part of the export.
- Works across personal and team vaults — team vault sync automatically picks up imported entries.