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 observed metric and imperial unit-bearing formats, including older exports without newer optional columns. Performed sets and supported supersets are imported.
Strong
Use an English workout-history CSV export. A legacy 12-column export does not identify whether weight values are kilograms or pounds, so LiftJot asks you to choose before inspection. When a supported Strong export declares units in its headers, those headers take precedence.
FitNotes
Use a FitNotes Android .fitnotes SQLite backup with database schema version 22—not a FitNotes CSV. LiftJot previews exercises, mappings, collisions, settings that can be carried over, warnings, and unsupported source concepts before import.
Steps
- Create the supported export or backup in the source app and save it somewhere your device can access.
- In LiftJot, open Settings → Data controls and choose the matching import source.
- Select the file. For a legacy 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 imported workouts before continuing normal training.
Safety behavior
LiftJot reopens and rechecks the chosen source before committing, creates a named safety backup, validates the planned result, and writes the import in one transaction. A failed validation, backup, or write leaves the existing training record unchanged.
After a successful import, one-tap undo is available while the imported training state has not been changed. A discoverable safety backup remains available for a full restore under the app’s recovery rules.
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 shape it cannot interpret safely instead of guessing. Email liftjot@gmail.com with the source app, export type, LiftJot version, platform, and exact error. Attach the file only if later requested and you choose to share it.