How to Back Up and Restore Your workcmd Data
workcmd lets you export settings and supported local data to a JSON file, then import it after reinstalling or moving to a new machine.
Building a library of snippets, colour rules, folders, notes, reminders, and vault metadata takes time. Losing it because you reinstalled Chrome or moved to a new machine shouldn't be the cost. workcmd's backup feature exports supported settings and local data to a JSON file, then imports it with safe settings merges and Pro-gated data restore.
How to export your backup
Open workcmd settings and navigate to the Backup tab. Click Export Settings. The file is saved as workcmd-backup.json and can include settings plus supported local data such as notes, folders, reminders, vault metadata, custom assets, and custom sites. Keep it somewhere private, because exported backups may contain workspace context.
How to import settings on a new machine or after reinstall
After installing workcmd fresh, go to the Backup tab and choose the JSON file you exported previously. workcmd reads it and merges settings safely: new templates and colour rules are added, duplicates are skipped, and other preferences are updated from the file. Supported local data is restored for active Pro accounts.
What is and isn't included in the backup
Exports can include templates, colour rules, folders, preferences, notes, reminders, vault metadata, custom assets, and custom site entries. Billing status, credits, and subscriptions are never imported from a backup file.
When to use this
Export before a Chrome reinstall, a machine upgrade, or a factory reset. For teams, use backups carefully as a starter configuration for settings and snippets, and remember that any exported file should be treated as private workspace data.
Make inbox cleanup repeatable
workcmd helps teams reduce recurring noise, keep local context, and move faster across the tabs where work already happens.