Import replaces rather than merges

Know the data boundary

Fastly's import is a replacement operation. It loads the backup dataset as the local state instead of adding those records alongside the ones currently on the device.

Use the supported file workflow

Export the current ledger first if you want to preserve it. Read Replace local records carefully before confirming an import, particularly when the selected file is older than your latest sessions.

The importer expects a version-1 Fastly JSON object and rejects files larger than 10 MB. Record validation checks dates, goal values, note length, optional weight, and the distinction between running and completed records.

Check the copy you actually have

A backup from last month does not contain this week's new entries. Importing it can replace those entries with the older dataset, even though the file itself is valid.

Manage each retained copy

There is no automatic merge or selective record picker in this workflow. Decide which complete copy you intend to use before importing.

There is no account or automatic custom-server backup in this release. The privacy text also states that the app's private local storage is excluded from automatic cloud device backups; exported files are your separately chosen copies.

A worked walkthrough

Imagine the device currently contains sessions through Friday, while the file you selected was exported on Monday. Confirming replacement restores the Monday dataset; it does not preserve Tuesday through Friday by automatically adding them afterward. If you need to keep the current Friday copy, export it before importing anything. Name the files clearly enough that the two complete datasets remain distinguishable. If you later restore the Friday file, that is another replacement, not a reconciliation of changes made in between. This matters especially when journals were edited on more than one device or a newer session was added after a restore. The importer has no selective merge interface to decide which conflicting fields you prefer. Treat the confirmation as choosing one complete ledger state, and preserve other states as separate files only when you actually want them.