What stays compatible
BurrowTime targets Watson 2.1.0 command behavior and preserves theconfig, frames, state, andlast_sync formats. Its agent and concurrent-timer metadata lives in separate companion files.
Move from Watson
On first interactive use, BurrowTime offers to copy a detected Watson installation. Watson's files are not moved or edited. You can run the same migration later:
burrowtime migrate from-watsonIf BurrowTime already has data, it confirms replacement and creates a timestamped backup.
Move back to Watson
burrowtime migrate to-watsonWatson can represent one active timer. BurrowTime refuses the export while extra concurrent timers are running, and it does not copy the companion agent or concurrency files.
Migration is a snapshot, not a sync. Activity recorded after a copy does not automatically appear in the other program.
Use custom directories
burrowtime --data-dir /path/to/burrowtime \
migrate from-watson --watson-data-dir /path/to/watson
burrowtime --data-dir /path/to/burrowtime \
migrate to-watson --watson-data-dir /path/to/watson --forceThe compatibility executable
Release archives also contain watson. It keeps Watson's original data-directory behavior and non-interactive bare command for users who want a direct Go-based replacement.