Repsy

From Strong to Repsy, without losing a single set

Strong exports your history as CSV, and Repsy reads both the current format and the legacy 11-column one — including files from people who have used the app for years. Weight, reps and date go into the calculation that picks your next load.

Exporting from Strong

CSV (current layout and the older 11-column one)

  1. Open Strong and go to Settings.
  2. Choose "Export Data" / "Export Strong data".
  3. Share the CSV with yourself or save it to Files.
  4. Upload the CSV in Repsy: Profile → Import history.

What comes across

  • Every set: weight, reps and the date you did it.
  • Your personal records, recalculated from what came in.
  • How many times a week you were actually training.
  • The exercises you did most, matched against the Repsy catalogue.
  • All of it feeds your first generated plan — it starts out knowing your loads.

What doesn't (and why)

  • Progress photos and body measurements: they aren't in the apps' exports.
  • Cardio without load lands as a session but produces no weight suggestion.
  • An exercise name that isn't in the catalogue is kept as free text — the history survives, it just doesn't become a chart.
  • Nothing is written before you approve the preview. If the file came out wrong, discard it.

What happens after the import

Your plan starts calibrated

Generation uses the frequency and the loads that came from the import instead of asking everything again — and instead of starting from an empty bar.

The first set opens with a weight in it

Where there is history, the weight field is pre-filled with what you lifted last time on that exercise, set by set.

The next cycle comes out of your numbers

When you close a cycle, the next one is built from the load you actually recorded — imported counts exactly like typed here.

Questions

My Strong export is old. Will it still work?

Yes. The reader recognises the current format and the legacy 11-column one. If the file matches neither, it still falls back to the generic spreadsheet reader, which maps your columns and shows a preview before anything is stored.

Strong keeps my records. Do they come across?

Records are recalculated from the imported sets, so they reappear — derived from what actually came in the file rather than copied off a screen.

What about the routines I built in Strong?

The import brings the HISTORY (what you performed). The plan itself Repsy generates from those loads, your goal, and the training frequency the history itself reveals.

Do I need to pay to import?

No. History import is free and passes through no plan gate. The limits are technical: files up to 15 MB and a handful of imports per day.

What if my app isn't listed?

Export to CSV, spreadsheet or PDF and send it anyway. Repsy tries the dedicated readers first; when none recognises the format, it maps your file’s columns and applies that map deterministically. You see the preview before anything is saved.

If I import twice, does it duplicate?

No. The same file sent again is rejected by its content (not its name), so re-uploading by mistake never doubles your history.

My export is in pounds. Does that work?

It does. The Hevy, Strong and Jefit readers handle pounds and kilos — the conversion happens while reading, not afterwards.

Can I keep using the other app?

Yes. The import is a copy of what already happened; nothing is deleted in the source app. You just cannot keep both in sync in real time.

Years of Strong should not end up as a parked file

Bring the CSV and watch your first Repsy plan come out with your real loads — not an empty bar and a questionnaire.