Local backups
Some records deserve a place beyond the screen where you check them every day. HoursKit lets you export a local JSON backup, giving you a deliberate copy of the shifts, jobs, and setup you have built.
It is a practical option for people who like to keep their own archives organised.
Local backups
Export a local JSON copy of your HoursKit records and bring it back into the app when you need it.
Export a backup at a natural moment: after finishing a busy season, before making major changes to how you organise work, or when you simply want a copy of a completed year.
The JSON file captures the HoursKit record as a package, so you do not need to assemble a backup from screenshots, spreadsheets, and scattered notes.
A shift is easier to recognise when the jobs, templates, settings, and related details travel with it.
A local export preserves that surrounding structure, giving your archive more value than a bare list of hours. You can keep the file with your own files in the location and organisation system you prefer.
Import the JSON file through HoursKit when you need to work with a saved copy again. The format gives your own data an intentional archive and return path.
Check the file you select so you know which snapshot you are bringing back, especially if you keep more than one backup over time.
iCloud helps keep your current entries available across your iPhone and iPad. JSON export serves a different purpose: a portable copy you choose to create and retain.
It works well for a finished tax year, a long project, or any set of hours you want to file away independently from the app’s day-to-day use. In that sense, it is a filing habit you control, built from the data already in your tracker.
Related pages
Export a local JSON copy of your HoursKit records and bring it back into the app when you need it.
For iPhone and iPad