Hevy

Import options

LiftShift supports two ways to bring in your Hevy data:

• CSV import: Export your workout history from Hevy as a CSV file and upload it to LiftShift. This gives you the most complete data, file imports are never capped. All analysis runs locally in your browser.
• Hevy API sync: Log in with your Hevy email and password, or paste a Hevy Pro API key. LiftShift pulls your newest workouts through your own backend proxy and keeps your dashboard up to date. Very long histories can be capped by the source API, when that happens the app shows a “Showing newest history only” banner.

How to export your Hevy data

1. Open the Hevy app on your phone.
2. Go to your Profile tab (the person icon in the bottom-right corner).
3. Tap the Settings gear icon in the top-right.
4. Scroll down and tap Export Data. Hevy will generate a CSV file containing your full workout history.
5. Save or share the CSV file to your computer, then upload it to LiftShift\u2019s import page.

What LiftShift reads

LiftShift parses the following columns from your Hevy CSV export:

• Exercise name (the exercise_title column)
• Workout date and time (the start_time column)
• Set-level data including weight in kg, rep count, set type, RPE, duration, and distance
• Workout-level metadata such as title, description, and notes

File import runs entirely in your browser. Login and API-key sync pass through your own backend proxy, which only forwards requests to Hevy and stores nothing.

Troubleshooting

Date parsing

Hevy exports dates in ISO 8601 format (e.g. 2024-01-15T08:30:00Z), which LiftShift parses automatically. If you see date-related import errors, your phone\u2019s locale may be affecting the export format. Try switching your phone\u2019s language to English (US) temporarily before exporting, or check that the start_time column in your CSV uses a standard format.

Only newest workouts synced

Login and API-key syncs pull your newest workouts first and the source API caps how far back one sync can go. When the cap hits, the app shows a “Showing newest history only” banner and totals reflect the partial history. For the complete log, import a Hevy CSV export instead.

Charts look wrong

If metrics like training volume or 1RM estimates don\u2019t match what you expect, the most common cause is inconsistent exercise naming. If you\u2019ve renamed exercises in Hevy or used custom names, LiftShift\u2019s muscle mapping may not group them correctly. Standard Hevy library names produce the most accurate results. Check the muscle heatmap to see if exercises are being mapped to the right muscle groups.

Units

Hevy stores all weights in kilograms internally. LiftShift displays weights in the unit you choose in your dashboard settings. If your Hevy profile uses pounds, the CSV export still contains kilograms. LiftShift converts them to your preferred unit during import. Make sure your unit preference is set correctly in LiftShift\u2019s settings before importing.

Combining Hevy with other apps

LiftShift lets you combine data from multiple apps into one unified dashboard. If you\u2019ve used Hevy alongside Strong or Lyfta, import both exports and LiftShift merges the workout histories, deduplicates overlapping sessions, and gives you a single view of your entire training history. See the How it works page for details on multi-source merging.

What analytics you get

• Training volume: Total weight moved per workout, per week, and per muscle group, with rolling window comparisons.
• Personal records (PRs): All-time bests, 1-month bests, and premature PR detection with drought alerts.
• 1RM estimates: Estimated one-rep max for every exercise, updated after each workout.
• Muscle heatmaps: Visual breakdown of which muscles your training emphasises, with 7-day rolling windows and volume zone scoring.
• Set-by-set feedback with 19 coaching scenarios, badges, tooltips, and suggestions based on your performance quality.
• GitHub-style yearly consistency heatmap showing streaks, consistency scores, and workout day highlights.