Migration guide
Import workout history
LiftJot reads supported files locally. You see a preview and choose how overlapping dates are handled before the app changes your log.
Import performed history, not plans. Routines, templates, profiles, measurements, and social data are not imported.
Supported sources
Hevy
Use an English workout-history CSV export. LiftJot supports the metric and imperial formats Hevy has produced, including older exports that lack newer optional fields. Performed sets and supported supersets are imported.
Strong
Use an English workout-history CSV export. Older Strong exports do not record whether weights are kilograms or pounds, so LiftJot asks you to choose before it inspects the file. When an export declares its units in the headers, those headers take precedence.
FitNotes Android
Use a local FitNotes Android backup file—not a CSV. LiftJot previews exercises, mappings, collisions, settings that can be carried over, warnings, and source concepts it cannot represent, all before anything is imported.
FitNotes 2 iOS
Use the official Workout CSV export from FitNotes 2 by getfitnotes.com. This is a different product from the separate app named “FitNotes - Workout Tracker.”
FitNotes - Workout Tracker
Use that app’s workout CSV export. LiftJot reads the values and units the file declares instead of guessing them from exercise names.
Steps
- Create the supported export or backup in the source app and save it somewhere your device can reach.
- In LiftJot, open the data controls and choose the matching import source.
- Select the file. For an older Strong export, choose the unit system used when the history was logged.
- Review incoming dates, sets, exercise matches, warnings, and overlaps.
- Choose one overlap policy for matching dates, then confirm.
- Review the imported workouts before continuing normal training.
Safety behavior
LiftJot reopens and rechecks the file you chose before committing anything, prepares and checks a safety copy of your existing record, validates the planned result, and writes the import as a single step. If validation, the safety copy, or the write fails, your existing training record is left unchanged.
After a successful import, a one-tap undo is available for as long as the imported data has not been changed. The most recent safety copy stays available for a full restore, with a warning. After a later import, LiftJot makes a best-effort attempt to remove older safety copies, so earlier ones may remain. These files are configured to be excluded from operating-system backup. Clearing your workout history and running a full restore do not delete them, and there is no in-app list or deletion control for them. This safety data stays on your device: it is not an upload, and it is not a claim that any operating-system transport happened.
Local processing and file care
LiftJot does not upload the selected import file to a developer server and does not modify the source file. Your file provider may process access under its own terms. Treat workout exports as private: first contact support without attaching the source file.
If a file is rejected
Export formats change. LiftJot rejects a file it cannot interpret safely instead of guessing. Email liftjot@gmail.com with the source app, the export type, your LiftJot version, your platform, and the exact error. Attach the file only if we ask for it and you choose to share it.