Importing your history

What this covers: exporting from Strong or Hevy, reading the import preview, and the YAML program format.

Getting the file out of your old app

Strong — Settings → Export data. You get a CSV, one row per set.
Hevy — Settings → Export data, same idea.

Importing

Settings → Data.
Paste the CSV (or pick the file) and choose whether it was exported in kg or lb.
Read the preview. It tells you how many sessions will be created, which exercise names matched the library, and which ones would be created as custom exercises.
Fix anything that matched wrong, then import.

The preview is a dry run — nothing is written until you confirm. Sets keep their weight, reps, distance, duration, RPE, and notes where your old app exported them.

Unmatched exercise names

Names are matched against the built-in library and its aliases. Anything that doesn't match becomes a custom exercise, so your history stays complete; you can merge it into a library exercise afterwards. On the free plan custom exercises are capped, so a messy export is worth tidying before you import.

Programs as code

Your workouts and routines export as YAML you can read, diff, and keep in a repository. Import it back and you get a diff first: what would be created, updated, or left alone. It's the same round trip the CLI and the API use.

routine: Push Pull Legs
workouts:
  - name: Push A
    exercises:
      - Barbell Bench Press: 3x5 @ 80kg
      - Overhead Press: 3x8

That's an illustration of the shape, not a spec — export your own program to see the exact format your account produces.