Backups
Open Backups for workspace exports and restores, or choose a project’s backup action for a project-scoped bundle. Store the downloaded file yourself. Exports exclude admin API keys.
Export
- Choose the workspace or project scope.
- For a workspace export, choose Live, Sandbox or both. This selection is independent of the app’s current mode switch.
- Review Custom content selection, or choose All data.
- Review Include secrets, then export and keep the downloaded file.
The initial Custom selection includes configuration, credentials, customers, billing and allowance data, but excludes Usage & request logs and excludes secret values. Stored request data can include retained synthetic Sandbox content and is usually the largest group. See content retention for when text is present; exporting logs cannot recover omitted content or trimmed live-tail events.
All data enables secret values as well as every content group. Returning to Custom restores the prior custom selection. A secret-bearing file can contain provider keys, subscription authentication and integration tokens; restrict access to it.
Some content groups require others. The checklist keeps required parent groups selected so references can be restored. For example, billing needs products and customers. A project restore can reference shared workspace accounts and existing 1Password integrations without changing another workspace’s ownership.
Restore an existing scope
- Open the target workspace or project and choose a backup file for that scope.
- Review the plan and select the content groups to restore. A bundle from another scope is refused.
- Explicitly choose whether to restore credentials. This requires secret values to be present in the file.
- Export the safety copy offered by the wizard and verify that you retained the download.
- Review the final plan, then restore.
The browser initiates a safety-copy download; it cannot prove that the file was saved on disk. Keep your own copy before proceeding.
Restore validates and updates the selected records in one transaction. It is not a database rewind. Existing usage totals, accepted upstream sessions and immutable payment/request history are protected on conflict. Restored purchase history does not independently reactivate paid access. Records cannot cross their Live/Sandbox boundary.
Secret values do not guarantee a working subscription login. Expired, rejected or uncertain renewable credentials can restore disconnected and require signing in again. Separate subscription entries and relay membership remain distinct while shared credential sessions are reconciled. Conflicting identities and credentials are refused.
Import as a new project
Use Import project to copy configuration into a newly created project instead of changing the existing one. Import accepts a bundle containing exactly one project and its connected configuration graph.
The preview identifies supported configuration and credential counts. Import creates new IDs and ownership, remaps references and the default product, and excludes customer and purchase history. Credential transfer is a separate opt-in. A masked or credential-free import can require reconnecting providers; a copied provider can be disabled if its required credential source was not transferred.
Missing or detached references are rejected before writing. The import commits atomically, but a lost response can still leave you uncertain whether it committed. Check Projects before trying to create another copy.
Size and failures
| Symptom | Next step |
|---|---|
| Export too large | Exclude usage/request logs, export one project, or select one mode |
| Progress starts but export fails | Treat the export as failed even if its HTTP response began with 200 |
| Restore refuses the upload | Check scope, valid bundle format and decompressed size; the decoder limit is 64 MiB |
| Import or restore times out | Inspect the target state before retrying; timeout does not prove nothing changed |
| Credentials restore disconnected | Reconnect the account or subscription and verify its affected products/relays |
Vercel-hosted exports use a configured 4 MiB response ceiling. Local serving does not apply that same ceiling; a successful large local export does not establish that the hosted endpoint can return it.
For automation, use the admin SDK and backup API. Reissue Modem admin API keys separately rather than expecting a backup to recover them.