Private data and in-app migration

New installations store private state in %LOCALAPPDATA%\Ballast\data on Windows. Program files may be updated separately. Saved credentials use Windows protection tied to the user; the database still contains private holdings, history and preferences. Protect your Windows account, device and backups.

An older installation may still use the program's data folder. Ballast keeps that ledger in place until you explicitly move it, avoiding a second empty account history. System shows the current and recommended locations and a notice if a cloud or shared folder may be involved.

Move private data from System

Open System → Private data and review the source and destination.
Choose Move private data and read the confirmation. Ballast will

close its background engine; automated exits are paused during the move.

Confirm only when no trading cycle is active. The app waits for the

server and background launcher to stop, copies and verifies the ledger, and restarts in the background. Keep the app window open while it reconnects.

Inspect the reported migration result, account history, open positions

and settings. STOP stays engaged until you review and release it in System. Compare open broker orders directly; stopping the app does not cancel already-submitted orders.

The move refuses an active cycle, an update in progress, a custom DATA_DIR override or a destination that already contains files. It never overwrites another private profile. The offline mover separately checks server ports, the launcher lock and SQLite write access before taking a consistent backup. It checks database integrity, protects copied credentials and restricts Windows destination permissions to the current user and SYSTEM.

No terminal command is required for the normal migration flow. A configured custom directory needs individual review rather than silently removing the user's explicit choice. If migration fails after shutdown, the helper attempts to restart the original profile and shows the result in System. Originals remain available; if automatic restart fails, reopen Start Ballast.pyw.

Quit without leaving a background engine

Closing the app window and stopping the background engine are separate actions. System → Quit Ballast asks the app and its background supervisor to exit cleanly after verifying that no cycle or update is active. It does not remove your startup preference or cancel orders already at the broker. Reopen Start Ballast.pyw when you want to use Ballast again.

Stop bot controls scheduled trading while keeping the interface open. The STOP file blocks subsequent cycles, including automated exits. Use the control that matches your intent and review outstanding broker orders.

Review old and cloud copies

Original files are retained for recovery. After verifying the new ledger, decide how to secure or remove the old files and backups. A local move cannot erase OneDrive version history, previously shared copies or another person's backup. Rotate credentials that were exposed while stored without protection.

Moving encrypted files to another Windows user is not a supported credential transfer method. Reconnect providers under that user instead of assuming their keys will decrypt.

Advanced offline recovery remains documented in Windows startup and recovery; it is not part of ordinary app use.