All your Wrixton data lives in the cloud, so keeping a local copy is good practice. The track export and track import commands let you snapshot everything to a single JSON file and restore it later — whether you are migrating to a new account, safeguarding against accidental deletion, or just want an offline record.
Exporting your data
Run track export to download everything: all active items, all done and canceled items, and the full project → feature → requirement tree.
# Write the backup to a named file
track export --out backup.json
# Or redirect stdout to a file of your choice
track export > backup.json
jq if you want to inspect or transform your data outside of Wrixton.
The export always includes completed and canceled items — there is no flag to exclude them. If you only want a partial snapshot, edit the JSON manually after exporting.
In the web UI
Go to Settings → Export / Import and click Export. The browser downloads a backup.json file in the same format the CLI produces.
Restoring from a backup
Pass the backup file to track import to recreate everything in the current account:
The import assigns fresh IDs to every row so there are no conflicts with the destination account’s existing sequences. Feature IDs are remapped internally so tasks re-attach to the correct features even after the ID change.
After a successful import, the CLI prints a summary:
imported 142 item(s), 6 project(s), 18 feature(s), 34 requirement(s)
track import is designed for restoring into a fresh, empty account. Running it against an account that already has data will create duplicate rows — Wrixton does not deduplicate on import. If you need to restore, create a new user with track user add, configure the CLI to use that user’s API key, and then import.
In the web UI
Go to Settings → Export / Import, click Import, and select your backup.json file. The same warning applies: import into an empty account only.
What the backup file contains
The JSON export is a single object with two top-level keys:
items — every item of every kind (todo, chore, task, gift, shopping, grocery), including done and canceled rows. Each item carries its full set of fields: title, kind, status, due date, priority, tags, estimate, recurrence, and more.projects — the full project tree, with each project’s features and their requirements nested inside.
The file does not contain your API key, credentials, or sharing configuration. Share relationships are not exported or imported.