Export Strong datainto Fire Your Coach.

A Strong export is twelve columns wide. Four of them rebuild your lifting history.

Strong is a fast set logger, and it does the decent thing on the way out: your history exports as a plain CSV that you own. This page is about the move itself: what's in that file, what carries over, and where the conditioning goes once it lands. If you're still deciding, how Fire Your Coach compares with Strong is the page for that. This one assumes you've decided.

Free · No in-app purchases
HOW THE EXPORT WORKS

Three Steps From Strong Export To Rebuilt History.

01

Export The CSV

In Strong, open Settings and export your workout data. You get one file covering your logged sessions, with twelve columns: Date, Workout Name, Duration, Exercise Name, Set Order, Weight, Reps, Distance, Seconds, Notes, Workout Notes and RPE. One thing the file doesn't record is its unit. Strong writes whatever your app was set to, kilograms or pounds, and never labels it.

02

Import It

Pick Strong as the source and drop in the file. Strong writes Workout Name, Exercise Name and Set Order; Hevy writes exercise_title and weight_kg, and the importer checks the headers match what you chose. Before anything is saved you get a preview: the row count, the date range in the file, how many weight values parsed, and a check on kilograms or pounds. Files up to 10 MB.

03

Get The History Back

Every exercise name is matched against the exercise library, and every set keeps its own weight, reps and date. From those rows Fire Your Coach reads your working weights, sessions per week, push and pull balance, and top lifts with an estimated one-rep max. It also compares the last four weeks in the file against the four before them. Your first plan starts from those numbers rather than an empty form.

WHAT MOVES WITH YOU

What A Strong CSV Carries. What It Leaves Behind.

What Carries Over

  • Every set, on its own date. Weight and reps are read per row, and the date is kept per set. A set you did in March stays a set you did in March
  • Exercise names, resolved. Each name is matched against the exercise library by exact match, alias or normalized form. Names the library doesn't recognise are kept and flagged for review rather than dropped
  • One unit, throughout. Pounds convert to kilograms on the way in, so imported sessions and everything you log afterwards compare directly. You see whichever unit you prefer
  • The shape of your training. Sessions per week, the date range, a split read from your last twelve sessions, and how your sets divide between push and pull. Read from the rows, not asked in a form
  • Your top lifts. The heaviest working set per exercise from its most recent session, with an estimated one-rep max, ready to set the starting weights

What The Import Leaves Behind

  • RPE. Strong exports an RPE column. The importer doesn't read it today, so imported sets arrive without effort ratings
  • Notes. The per-set Notes and the per-session Workout Notes are both in the file. Neither is read
  • Distance and Seconds. Strong records both for cardio and timed work. Neither is imported, so a cardio row marks the day as a training day but its distance and time stay in the file
  • Workout names, duration and set order. Sessions are rebuilt from dates, not from the routine name you gave them, so two workouts on the same calendar day merge into one
  • The conditioning you ran elsewhere. EMOMs and Tabatas you ran from a timer app were never in Strong's file, so there's nothing for the import to carry
Strong's columns, and what the importer reads
Column In Strong's file Read on import
DateYesYes
Exercise NameYesYes
WeightYesYes, as kg
RepsYesYes
RPEYesNo
Notes, Workout NotesYesNo
Distance, SecondsYesNo
Workout Name, Duration, Set OrderYesNo
THE GAP

The lifts come across. The conditioning was never in there.

Strong keeps every set you log, and the export hands all of it over. What it can't hand over is what Strong never held. The EMOMs, the Tabatas and the intervals ran in a timer app, and the timer app kept nothing once the round was over.

So the history that arrives is the lifting half of your training. That's enough to set the starting weights for your first program. It isn't the whole week, which is why the plan builder asks about the conditioning you do instead of guessing it from the file.

The file holds the lifts. The week held more than that.

AFTER THE IMPORT

The history lands first. Then both halves go in one plan.

The first thing you get is a read on the file: how often you've been training, your heaviest working sets and their estimated one-rep maxes, which way your push and pull volume tilts, and whether your last four weeks were heavier or lighter than the four before. None of it was entered by hand. It came out of the CSV.

Strong stays where it is. Importing copies the file. It doesn't move or delete anything, and the imported history can be removed again if you want it gone. Keep logging lifts in Strong if that's where you're happy, or log here, where tap-to-complete sets and a rest timer that starts itself are built for one hand mid-session.

From here the conditioning has a place. The plan puts the lifts and the conditioning in the same weeks, in the method of a coach you follow. Tabatas, EMOMs and intervals run inside the session with a timer in the app, and they're logged beside the squats. Before the first set it asks how you feel. With Apple Health connected, last night's sleep, HRV and resting heart rate fill in the answer, and each finished workout is saved to Apple Health.

WHAT YOU KEEP
The Lifts Come With You. The Conditioning Starts Here.
FREQUENTLY ASKED

Strong export, import, and what carries over.

In Strong, open Settings and export your workout data. Strong writes a single CSV with twelve columns: Date, Workout Name, Duration, Exercise Name, Set Order, Weight, Reps, Distance, Seconds, Notes, Workout Notes and RPE. That file is portable. Import it into Fire Your Coach and confirm whether your Strong app was set to kilograms or pounds. Your sessions, exercises, loads and reps are rebuilt as training history.

Four columns do the work: Exercise Name, Date, Weight and Reps. Every set is kept with its own date, every exercise name is matched against the exercise library, and pounds convert to kilograms on the way in. From those rows Fire Your Coach reads working weights, sessions per week, split, push and pull balance and a volume trend. RPE, notes, distance and duration are in Strong's file but aren't read today.

No. Importing copies your CSV into Fire Your Coach. It doesn't move or delete anything. Strong keeps its data, you keep the exported file, and Fire Your Coach keeps the rebuilt history. If you change your mind, you can remove the imported history from Fire Your Coach.

Yes. Strong exports in whatever unit your app was set to and the CSV doesn't record which one, so Fire Your Coach asks you to confirm kilograms or pounds before anything is saved. Pounds convert to kilograms on import, and the display then shows whichever unit you prefer. Confirming it matters: the wrong unit corrupts every starting load in your first plan.

Only part of what Strong logged. The importer reads exercise, date, weight and reps, so a cardio row marks the day as a training day but leaves its distance and time in the file. EMOMs and intervals you ran from a timer app were never in the file. From your first session here, they run inside the app and are logged beside the lifts.

MAKE THE MOVE

Export it once. Bring the whole history.

In Strong: Settings, then export your workout data. In Fire Your Coach: import the CSV, confirm kilograms or pounds, and check the preview before it saves. Your history sets the starting weights, and your first plan is written around the lifts and the conditioning you do.

Free · No in-app purchases