Strong to Hevy
Move from Strong to Hevy without guessing why import failed.
Strong to Hevy is one of the few migration paths with official importer support, but it still breaks often enough that lifters search forums when the button does nothing or workouts look incomplete.
Use this checklist before importing, because Hevy documentation says imports are limited and formatting support is narrower when the CSV is not a direct English Strong export.
Step-by-step checklist
- 1
Set Strong to English if your device/app language changes export headers.
- 2
Export Strong data and save the original file.
- 3
Open Hevy > Profile > Settings > Export & Import Data > Import Data.
- 4
Choose Import Strong CSV and select the exported file.
- 5
Wait for the import to finish before closing the app.
- 6
Open recent workouts and custom-exercise workouts to compare against the CSV.
- 7
If the import fails, do not keep re-saving the file blindly; validate the original export first.
The import path
Hevy's documentation describes a direct Strong CSV import. The important constraint is that the file must be a Strong export and the export must be in English.
That English requirement explains a lot of forum confusion: a CSV can look valid to a spreadsheet while still failing an importer that expects exact header names.
| Requirement | Why it matters | Fix |
|---|---|---|
| Strong direct export | Hevy support is built around this format | Export from Strong settings. |
| English headers | Importer expects known column names | Switch app/device language before export. |
| One prepared file | Hevy documents a limited import workflow | Clean and validate before importing. |
| Custom exercise review | Matched exercises may become duplicate custom exercises | Spot-check and merge/rename where possible. |
What Hevy will not solve for you
Hevy can ingest a Strong-style history file, but it cannot know that your 'DB Row', 'Dumbbell Row', and 'One Arm DB Row' were meant to be the same movement unless the importer has a clear match.
The cleaner your old exercise naming is, the cleaner your new charts will be.
The post-import audit
Check one recent workout, one workout from years ago, one workout with custom exercises, and one workout that includes assisted bodyweight or timed work.
If those all match, your migration is probably usable. If they do not, fix the source file before building months of new history on a bad import.
Tools
Validate before you import.
Sources
Checked against current app docs.
Hevy import documentation
Used for Strong CSV import constraints, English export requirement, and Hevy export behavior.
Hevy previous workout import tutorial
Used for the current Hevy import flow and one-import limitation.
Strong export documentation
Used for Strong export steps and the note that exported files cannot be imported back into Strong.
FAQ
Fast answers
Why does Strong to Hevy import fail?
The common causes are non-English Strong exports, changed headers, spreadsheet delimiter changes, custom exercise issues, or a CSV that was edited and resaved incorrectly.
Does Strong to Hevy import routines?
Treat the migration as workout-history focused. Saved routine templates and completed workout history are not the same data.
Can I import Strong measurements into Hevy?
Hevy documentation separates workout and measurement exports; the Strong CSV import path is primarily for workouts. Verify measurements separately before relying on them.
RepStack for iPhone
Import once. Train from clean history.
RepStack keeps your old work useful by turning history into targets, PRs, and progression decisions.