Can you get your training data out? We read every help center

Every workout you log is a small deposit into a record you are going to want later. The useful question is not whether an app lets you see that record today. It is whether you can take it with you when the app raises its price, changes hands, or stops being the one you want.

So we went and read the help center of every major Android tracker, including our own, and asked one question of each: is there a documented way to get your training history out, and what shape does it come in? Below is what each vendor actually says, with the ones we could not confirm marked as exactly that.

Strong: CSV, out only

Strong is the clearest of the group. Its help center says workout data exports to “a spreadsheet friendly CSV format”, and tells you where the button is: Settings, then Export Strong Data on iPhone, or Settings, then Export Data on Android.

There is a hard limit stated in the same article, and it is worth knowing before you rely on the file as a backup: exported files cannot be imported back into Strong. The CSV is for reading elsewhere, not for restoring. Strong also documents no way to import a workout history from any other tracker; its integrations are all syncing, to Apple Health, Google Fit, Health Connect and nutrition apps, rather than migration.

One thing Strong says that we wish more apps said: your workout data is available whether you subscribe or not, and you will never be locked out of it. Export is not listed among the PRO features.

Hevy: an export exists, in a format nobody publishes

Hevy documents two exports, Export Measurements and Export Workouts, at Profile, then Settings, then Export & Import Data. What its help center never states anywhere is what file format you get. CSV appears in that article only in the context of importing a Strong file, not describing Hevy’s own output.

There’s a more interesting question underneath. Hevy’s free tier is capped at three months of data history, where Pro gets all time. Whether that cap also truncates what an export contains is not documented either way. If you are on the free tier and considering leaving, that is the thing to test before you cancel, not after.

On the way in, Hevy is unusually generous and unusually specific: it imports from Strong, and only Strong. The file must be a direct export from Strong, it must be in English, and you get exactly one import. Support will send you a sample CSV in the Strong format if your data is somewhere else, but says plainly it will not help you troubleshoot it.

Fitbod: no export documented at all

This one surprised us enough that we checked it several ways. We enumerated every section of Fitbod’s help center and ran full-text searches across it. Searching for csv returns nothing. Searching for export, export workout data and download your data returns only unrelated articles.

Fitbod’s one data-policy article covers what it stores and how account deletion works, and says nothing about export, download or portability. The documented ways data moves are syncing rather than exporting: Apple Health, Health Connect on Android, a Fitbit connection on iOS, and share links for individual workouts.

Jefit: we couldn’t check, so we’re not saying

Jefit has a support article titled “How Can I Export My JEFIT Data?”. We know it exists because it’s indexed. We couldn’t read it: its support host refused every connection we attempted, across several methods. Jefit’s reachable support and FAQ pages mention export, import, CSV and backup nowhere at all.

Plenty of blogs describe a Jefit export flow. Every one of them is a third party. Rather than repeat an unverified claim about somebody else’s product, we’re leaving this row blank and suggesting you open that article yourself. If Jefit’s export works well, that is to Jefit’s credit and we would rather say so from their own words than from a blog’s.

FitTrack: JSON out, and CSV in from three of the apps above

Ours writes every workout, weigh-in, measurement and setting to a single JSON file in a folder you choose, from Settings, then Export to File. It is plain text you can open in any editor, and Import from File reads it back on a new phone. Both directions are free on the free tier and on Pro, because charging for the exit is the kind of thing this app exists to not do.

On the way in, FitTrack reads the CSV that Hevy, Strong or FitNotes exports, from Settings, then Backup, then Import training history. You pick the file through Android’s own file picker; there’s no login to the other app and no request made to it. The sessions merge into your history rather than replacing it, and importing the same file a second time doesn’t duplicate what’s already there, which matters because the usual way a migration goes wrong is running it twice.

Two honest limits remain. JSON is a better archive format than CSV and a worse spreadsheet, so if your plan is to chart your own numbers in Excel, you’ll do a conversion step that a Strong user doesn’t. And what comes across is the training log: sets, reps, loads and dates. Body measurements, custom metrics and routines stay behind, because the exports those apps produce don’t carry them.

The table

Read from each vendor’s own help center. Where a vendor does not state something, this says so rather than guessing.

What to actually do

Whichever app you use, including if it is not this one, do the export once this week rather than on the day you decide to leave. You will find out immediately whether the file contains what you assumed it does, while you still have a working account and a support channel to ask. A backup you have never opened is a hypothesis.

And if you are choosing an app now, treat the exit as a feature. An app that documents its export, states the format, and does not put it behind a subscription is telling you something about how it expects to keep you.

Vendor documentation was read on the date at the top of this article. Help centers change, and a claim that is true today may not be in six months, so check the source before relying on it.