Your training history is the most valuable thing in any workout app. Kaltro imports it on your device, with a preview before anything is saved — your sessions, sets, reps, weight, RPE, and notes come across. Some logbook extras stay behind: rest times, body measurements, progress photos, and routine or template structure don’t transfer. Personal records and estimated-1RM charts aren’t copied from the file either — Kaltro derives them on-device from the history you bring.

How to export your data from Strong

  1. 1 In Strong, open Settings → Export Strong Data.
  2. 2 Get the exported file into Files on your iPhone.
  3. 3 Open Kaltro, go to Settings → Import, and select the file.
  4. 4 Confirm whether your weights are in lbs or kg, review the preview, and commit. Duplicates are flagged for you.

How to export your data from Hevy

  1. 1 In Hevy, open Profile → Settings → Export & Import Data → Export Data, then tap Export Workouts.
  2. 2 Get the exported file into Files on your iPhone.
  3. 3 Open Kaltro, go to Settings → Import, and select the file.
  4. 4 Review the preview and commit. Nothing saves until you do.

Coming from any other app (generic CSV)

Kaltro also reads a generic CSV. If your current app can export a spreadsheet of your workouts with columns for date, exercise, weight, and reps, Kaltro can map it — and it shows a preview so you can check the mapping before anything is saved. Exercise names it doesn’t recognize become custom exercises, so nothing is dropped.

New to structured training, or just want a file to test the import with? Try one of our free workout-template CSVs — download it, then import it exactly like a Strong or Hevy export.

Export steps checked against Strong’s and Hevy’s help pages, October–November 2026.

Still deciding? Read the dated comparisons of Kaltro and Strong and Kaltro and Hevy, or start from switching to Kaltro.

Ready when you are — jump to getting started ↓

What carries over

Every cell below is checked against Kaltro’s shipped import parsers. Where a source app doesn’t include a field in its export, Kaltro can’t import it — so this table shows the gaps as well as the wins.

What transfers when you import from each source, field by field. Verified against Kaltro’s import parsers, July 2026.
Field Strong CSV Hevy CSV Generic CSV In Kaltro after import
Workout date Yes Yes Yes (7 formats auto-detected) Workout start; an unparseable date skips that row
Session duration No (not in export) Yes No Hevy only
Workout / routine name Yes Yes Yes (optional) Groups rows into one workout by date and name
Exercise name Yes Yes Yes Matched to the 275-exercise library; unmatched names become custom exercises, so nothing is dropped
Weight Yes (you confirm lbs or kg) Yes (unit auto-detected) Yes Weights import at full precision and display in lbs or kg — your choice
Reps Yes Yes Yes Stored
RPE Yes (clamped 1–10, 0.5 steps) Yes, if present Yes, if mapped RPE only — RIR is not recognized
Set type Working + warm-up heuristic Full: normal / warm-up / failure / drop set / rest-pause Working (+ heuristic) or mapped Hevy preserves 5 types; Strong and generic end up working or warm-up unless a column supplies more
Per-set notes Yes No (dropped) Yes Strong and generic only
Workout notes Yes Yes (description) No Stored with the workout
Exercise notes No Yes No Hevy only
Superset grouping No Yes No Hevy only
Distance (cardio) Yes (unit assumed) Yes No Stored in meters
Set duration Yes (seconds) Yes Yes, if mapped Seconds
Personal records Not in file Not in file Not in file Derived on-device from your imported sets, not imported
Estimated 1RM Not in file Not in file Not in file Derived on-device from your imported sets, not imported

What doesn’t carry over

  • Rest times — no parser reads a rest column.
  • Body measurements and bodyweight logs — these live in separate export files.
  • Photos and progress pictures.
  • Routines, folders, and template structure — an import brings your workout history only, never reusable templates.
  • Strong session duration and Hevy per-set notes.
  • RIR — only RPE is recognized.
  • Any unmapped columns.

What the engine does with your history on day one

Your imported history isn’t just a record to scroll — it’s what the engine reasons from, immediately.

  • Baselines per lift. The engine reads at least three sessions of a lift’s history before it suggests a progression, so importing your recent history gives it a running start instead of a cold read.
  • Personal records, derived on-device from your imported sets — not carried in from the file.
  • Estimated-1RM charts for each lift, derived on-device from the history you brought, so each lift’s chart has something to show from the start.

Import FAQ

Will importing overwrite my existing workouts?

No. Import only adds new workouts. Likely duplicates are flagged and deselected by default, and nothing is saved until you confirm from the preview.

How far back does it import?

Your full history. There’s no cap on how many workouts an import brings in or how far back it goes.

Do I need Kaltro Pro to import?

No. Import isn’t a paid feature and isn’t limited by the free tier — there’s no row or workout cap. Bring your whole history for free. Every workout you import is kept. On the free plan, analytics cover the last 90 days; Kaltro Pro adds your full analytics history.

What about units — lbs or kg?

Kaltro asks you to confirm lbs or kg when you import from Strong, and detects Hevy’s unit automatically.

Stuck? If a file won’t import or the preview looks wrong, email it to feedback@kaltro.fit (or describe its columns if you prefer not to share it) and we’ll help you get your history across.

Ready?

Ask for TestFlight access. Once Kaltro is on your iPhone, import your history and pick up exactly where you left off.

Or email feedback@kaltro.fit — we add testers by hand.