Backup and restore

Tap **More → About → Export JSON backup**.

Use the iOS share sheet to save the file to Files, iCloud Drive, or another destination.

No sign-in is required. The export captures data currently on this device only.

**Drives** (trips), including GPS route samples when recorded.

**Expenses** (amounts, categories, merchants, notes, links, and other fields — including receipt *file names*).

**Vehicles**, **Saved Places**, **Smart Routes** (Frequent Drives), **Work Hours**, **mileage rates**, and **trip purposes**.

**Receipt and attachment image files** — only filenames are stored on expense records; the photos/PDFs themselves are not embedded in the JSON.

**App settings** — for example automatic tracking, notifications, units, appearance, and accessibility preferences.

**Budgets**, **recurring expense rules**, **custom expense categories**, and **merchants**.

Tap **More → About → Restore from backup**.

Select the JSON backup file from Files or another location.

MileLedger merges the imported data with your existing local records. Review your drives and expenses after restoring to confirm everything looks correct.

Restoring does not bring back receipt images, app settings, budgets, recurring rules, custom categories, or merchants that were never in the file.

If you are signed in with a Google account, MileLedger automatically syncs structured data to Firebase (Firestore) and can sync receipt images to Firebase Storage. That sync is separate from the manual JSON export.

Cloud sync covers more than the JSON file for signed-in users (including receipts and many settings/entities that sync). Use both if you want a portable offline copy plus cloud recovery.

If you are not signed in, the JSON backup is your main portable copy — remember its gaps above.

MileLedger may periodically remind you to export a manual backup if you have not signed in and your expense count has grown since the last reminder. You can dismiss the reminder or export immediately.