Back up settings, workspaces and research
Preserve the right objects and recover deliberately without resetting account or execution state.
Reviewed 2026-10-24 · Windows & macOS
On this page
Know what each backup contains#
| Object | How to preserve it | What it does not establish |
|---|---|---|
| App settings | Settings → Data → Export settings | Complete broker credentials, one-click arming or research databases |
| Named workspace | Explicit Save, then workspace Export | Broker/account state or every app-wide preference |
| Chart/screener template | Its supported save/export workflow | A complete workspace or execution session |
| Research results | Supported run/export actions plus operator backup of authoritative storage | Reproducibility without source, data and assumptions |
| Plugins | Source, manifests, build instructions and compatible payloads | Automatic replacement of running plugin instances |
| Server execution/audit state | Operator backup of the configured server's storage | Independent proof that the broker is flat or reconciled |
A settings file and a workspace file are deliberately different formats. Export both when moving an analysis setup to another machine. Keep secrets in the receiving machine's supported credential authority.
Export app settings#
Open Settings → Data and choose Export settings. Store the resulting amm-settings JSON in a location you control. It includes supported app preferences such as appearance, shortcuts, chart defaults, notification choices and workspace prompts. One-click arming and broker credentials are not portable settings to silently restore.
Use Import settings for a compatible file and review the app's result. Importing preferences can alter appearance and navigation choices. It is not an instruction to start trading or an account migration. Keep the previous exported file for rollback.
Settings reset and layout reset have different scopes. Read their confirmation text. Use the available backup restore workflow only for the intended settings object, not as a substitute for restoring a research or execution database.
Save and export a workspace#
- Arrange your charts, screeners and research panels.
- Explicitly Save the named workspace. Working preferences and the saved named snapshot are separate.
- Use workspace Export and retain the supported package unchanged.
- On the receiving installation, use Import and review the named workspace, tabs and supported templates.
- Reconnect accounts and data feeds under that machine's authority. Verify every retained instrument/account route before an order or strategy start.
Native geometry depends on available displays and OS support. Reopening a workspace does not move windows between macOS Spaces or virtual desktops. Browser and desktop preferences are separate; opening a browser page does not automatically restore the native window arrangement.
Drawings have local, layout and global same-symbol scopes. Workspace templates intentionally exclude drawings. Do not delete a chart before understanding the lifetime of its local drawings. Preserve actual supported workspace exports when moving user state.
Preserve research reproducibility#
Retain run identity, algorithm/plugin build, exact parameters, all instrument routes, date range, initial capital, costs, fills and source provenance. A CSV of the best optimization row alone cannot recreate its engine input or all child results.
Ask your operator to back up the configured authoritative SQLite/results storage using a consistency-safe procedure. Do not copy an actively changing database as if it were a closed standalone file, and do not merge result folders from different running profiles blindly. Preserve required market archives according to provider licensing and access rules.
Recover an interrupted session#
After an unexpected exit, AMM can restore desktop working layout and recover eligible server sessions according to their configured policies. These are two separate processes. Verify actual recovery state before manually recreating a session; duplicate sessions can create duplicate subscriptions or exposure.
Read exact account/environment identity, broker positions, working orders, ownership and synchronization health. A restored chart is not proof that the strategy is running, and a running server session can exist while the UI is closed.
If an action timed out, reconcile before retrying. If external/manual trades changed a netted account, use the provider's supported baseline/sync workflow. Preserve the previous state and audit evidence when requesting support.
Plan recovery before a failure#
Test importing a non-production workspace and settings export on another installation. Confirm plugin compatibility and required history. Record where your operator stores backups and how to restore a specific version. A backup that has never been restored has a different evidence level from a tested recovery.
Avoid general-purpose “start over” resets while diagnosing trading exposure. Keep any irreversible data deletion outside routine recovery and retain the last known-good snapshot.