Back up and move devices
Before moving devices, reinstalling the app, or cleaning up, decide what you need to retain. Projects, experience, account access, and settings are separate objects. An experience archive or task package is not a complete backup.
Decide what to keep
| Content | Preparation | Recovery check |
|---|---|---|
| Projects and outputs | Save files; use project version control or file backups; include uncommitted work and databases | Required files and data are readable and output locations are correct |
| Experience assets | Use Import experience to identify supported archives and target runtimes | Types, IDs, counts, and import results |
| Model and plugin settings | Note connection names, model IDs, plugin sources, and non-secret configuration | The new device completes the same small task |
| Keys and service access | Use your controlled credential storage and check authorization on the new device | Valid credentials, intended account, and resource scope |
| Task material | Save outputs and relevant records; reconcile running work | No duplicate sending, publication, or completed actions |
A Git commit does not include untracked files, ignored material, or all external data. Check project requirements before deleting the old workspace. Store private or credential-bearing backups in restricted, encrypted storage.
Prepare the old device
- Save open files and check active and scheduled tasks.
- Note app version, data locations, backup time, and unconfirmed external requests.
- Pause related writes before copying data to avoid mixing different points in time.
- Open important backup files and check that uncommitted work and outputs are included.
- Keep a valid old-device copy until the new device passes verification.
Copying internal state while the app is writing does not establish consistency. Standalone Evolver locations are documented in State and asset paths; those directories are not the entire Desktop data store.
Restore and verify on the new device
Install the official app for the platform, restore project files, and configure model and plugin connections. Follow the Everyday setup checklist: read a sample, generate a small output, and verify account, location, and usage.
Desktop's experimental task-package import creates an independent copy with a new identity. It does not restore source approvals, running state, or an existing project. A .gepx archive migrates experience, not complete app settings and all tasks. Check coverage before treating a successful import as complete recovery.
Do not repeat external work merely because the new device lacks its record. Check sent messages, published content, and completed tasks in the destination before continuing or retrying.
If you run standalone Evolver
This section applies only to the independent CLI. Back up node identity, assets, events, memory graph, and workspace separately. A .gepx archive excludes the full root event stream, memory graph, mailbox, node credentials, and app settings.
Export experience to a new filename and retain the previous valid copy:
evolver sync --export backup.gepx
In an environment with an explicitly configured isolated data directory, preview import before writing:
evolver sync --import backup.gepx
evolver sync --import backup.gepx --write
Check IDs, counts, conflicts, and rejection reasons. Do not use --force instead of conflict analysis. Before migrating an original node identity, confirm the original instance has stopped. Two instances retaining the same identity must not process online tasks simultaneously. Reconcile remote work completed after the backup separately.
Clear the old device only after verification
Confirm required data is readable, usual tasks work, and external outcomes are reconciled before deciding what to remove. Use Change accounts and remove connections to revoke access, sign out, and handle local files separately. Installing an older app version does not restore data; recovery still needs a suitable valid backup.