Hevy CSV export
Export Hevy workout data before you switch trackers.
Hevy makes workout export possible, but a CSV export is still not the same thing as a complete migration plan. You need to know what file you have, what data it contains, and what the destination app accepts.
Use this page before deleting anything, cancelling a subscription, or assuming your next app can read a Hevy file directly.
Step-by-step checklist
- 1
Export workouts from Hevy settings.
- 2
Export measurements separately if you care about bodyweight or body measurements.
- 3
Store both files before changing apps.
- 4
Open the workout CSV and check dates, exercise names, weights, reps, RPE, and notes.
- 5
Check whether the destination app imports Hevy CSV directly or needs a Strong-format file.
- 6
Run a validation pass before import.
- 7
Import, then compare recent and older workouts against the original CSV.
Workout export vs measurement export
Hevy documentation separates workout export and measurement export. That matters because a training-history migration often fails quietly when users move workouts but forget bodyweight or measurement history.
If your strength standards, volume trends, or bodyweight-ratio calculations depend on bodyweight, export measurements before leaving the app.
| File | What it helps preserve | Migration risk |
|---|---|---|
| Workout export | Exercises, sets, reps, weights, duration, workout notes | Usually the main file. |
| Measurement export | Bodyweight and body measurements | Easy to forget, often separate. |
| Routine templates | Saved workouts you plan to repeat | May not be represented the same way as history. |
Why Hevy CSV may need conversion
Hevy's own import documentation says the supported import path is Strong CSV. That does not mean a Hevy export is useless. It means your destination app needs to know the Hevy format, or you need to transform the file into a format it accepts.
Before trying a conversion, identify what your target app requires: exact headers, date format, weight units, set order behavior, and whether custom exercises can be created automatically.
What to spot-check
After import, inspect workouts with custom exercises, supersets, timed sets, assisted bodyweight movements, and mixed units. Basic barbell sets are usually the easy case.
If only your cleanest workouts import correctly, your progress charts will look fine at first while older or unusual training disappears from the record.
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
Can I import a Hevy CSV into Hevy?
Hevy's current help articles describe importing Strong CSV, not importing a Hevy workout export back into Hevy. Treat Hevy exports as portability files for analysis or another app.
Should I export measurements too?
Yes if bodyweight or body measurement history matters to you. Workout export and measurement export can be separate files.
Can another app import Hevy directly?
Only if that app supports Hevy's export format. Otherwise, the file must be converted into the destination app's expected columns.
RepStack for iPhone
Import once. Train from clean history.
RepStack keeps your old work useful by turning history into targets, PRs, and progression decisions.