A mechanical keyboard collection accumulates a surprising amount of documentation over time: switch specs, lube recipes worked out through trial and error, build configurations, and a running list of group buys in flight. Whether that history lives in a paper notebook, a spreadsheet, or a dedicated app, it exists in exactly one place until you deliberately copy it somewhere else. A lost phone, a corrupted file, or a factory reset can erase years of that detail in an instant, and the risk has nothing to do with which tool you used to record it in the first place.
What this article covers
This article opens with backup habits that apply to any keyboard collection, regardless of what you use to track it, before looking at the specific export and import mechanics available in ThockLog, including a Pro-only restriction on restoring storage-location data.
A backup principle that works regardless of tool
The “3-2-1” rule for data safety is a reasonable standard for a hobby ledger, not just a professional archive: keep three copies of your data, on two different types of media, with at least one copy stored somewhere other than the device you use day to day. For a keyboard collector, that might mean a working copy on your phone, a second copy on a laptop or external drive, and a third copy in cloud storage or emailed to yourself as an archive file.
Frequency matters as much as the method. A reasonable baseline is to export a full backup after any significant change — finishing a build, wrapping up a lubing session on a batch of switches, or a group buy shipment finally arriving — and to treat a monthly export as a fallback cadence even during quiet periods. This holds whether your records live in a spreadsheet you export as a CSV or an app with a built-in backup tool: the habit of exporting on a schedule is what actually protects the data, not the specific file format.
What a complete backup should include, whatever you use to track it
No matter the tool, a complete keyboard collection backup should capture a few distinct categories of information:
- Switch identity and specs: Brand, name, type, and quantity for everything in the collection, along with any measured actuation or bottom-out figures worth keeping.
- Modification history: What lube, film, or spring changes were made to which switches, and when — details that are easy to forget once a batch is lubed and put away.
- Build configurations: The specific combination of board, plate, case, switches, and keycaps used in each completed build.
- Pending orders: Group buy status, vendor links, and payment details for anything still in the pipeline.
- Secondary gear: Keycap sets, stabilizers, cables, and deskmats, along with their purchase details.
Export Formats and Use Cases
Once you’ve decided what to back up, the format you export to should match what you plan to do with it. ThockLog provides two distinct formats for extracting the data above:
- CSV Export: This format generates a ZIP file containing individual CSV files for each data category. This is the ideal format for users who wish to view or manipulate their records in external spreadsheet software for further analysis.
- Photo-Inclusive ZIP Backup: For those seeking a total archive, this format packages all text records along with every high-resolution photo attached to the collection. This ensures that the visual history of builds and switches is preserved alongside the technical data.
Understanding the Restoration Process
The restoration of data in ThockLog is handled through an import system designed to protect existing records. It is important to note that importing a previous CSV or ZIP file adds the records back into the app as new entries. The system does not merge or overwrite existing items, which prevents accidental data loss during the process.
While basic item data can be restored by any user, storage location data—the hierarchical mapping of boxes, shelves, and drawers—is a specialized data relationship. Within a backup, this location mapping is only restored if the user has a Pro entitlement.
Securing Your Records with ThockLog
Because ThockLog stores data locally on the device rather than syncing to a server, the general backup habits above apply directly to it. ThockLog’s CSV/ZIP Export and Import features implement the same “get it off the device regularly” principle described above, and they’re available to all users for free, so every collector can secure their data regardless of subscription status.
To ensure your years of keyboard data are protected and portable, you can download the application here: ThockLog on the App Store
Summary
Whether you track your collection on paper, in a spreadsheet, or in a dedicated app, the same backup principle applies: three copies, two media types, one copy off-device, updated on a regular schedule. By exporting your switch specs, lube logs, and build histories on that schedule, you protect years of accumulated detail from a single point of hardware failure. For a broader look at why keeping this data in one place beats juggling spreadsheets, see One App or Five Spreadsheets? Why Mechanical Keyboard Collectors Need a Single System.
This article organizes information from a recording and organizing perspective. If you notice an error or outdated information, please contact us. Last verified: July 2026
