Illustrative example. The dates and amounts below are provided for practice.
A saved event was changed from August 14 to August 24, 2027, and the correct date still exists in a JSON backup. Restoring the whole backup can recover it, but also replaces every other local record.
Decide between one edit and full recovery
If only this date is wrong and you can verify the intended date, edit the card back to August 14. That is ten elapsed days earlier than August 24.
If several records were damaged, first export the current complete JSON collection from the calendar exporter. Keep that copy separately so newer plans are recoverable.
Restore deliberately
Choose the older JSON backup in the exporter, select Validate and Restore, review the replacement counts, and confirm. Return to the tracker and search for the event. The restored August 14 record should now appear.
A backup is a snapshot. Notes, plans, and new events created after it may have been replaced too. Invalid backups are rejected before replacement, and both local stores are replaced in one transaction.
For practice, use disposable records in another browser profile. Never test recovery by clearing your only copy. CSV and ICS are useful exports, but full restoration uses the versioned JSON format.