Before you import a single set, ask how you'd get it back out.
One-tap import is how trackers win switchers. Before you hand any app years of training history, check how that history gets back out.
One tap in, and then what?
The onboarding screen on a new strength tracker in 2026 usually carries the same offer: bring your history over from your old app in one tap.
So a lifter three years into training taps it. Every squat single, every RPE 8 that was really a 9, every note about the left knee on a cold morning lands in the new app before the kettle boils. It feels good. The whole past arrives intact.
Then nobody asks the follow-up question. If this app gets acquired, reprices, stops shipping updates, or stops fitting how you train in year five, how does that history leave?
Right now, before the first session is logged, is the only point where that question costs nothing to answer.
The Exit-First Test
Judge a tracker by its export before you hand it your import. Call it the Exit-First Test.
The reasoning is simple. Your logged history is the one controlled experiment you've been running on yourself: which rep ranges moved your bench, how much weekly volume your squat tolerates before it stalls, what a deload actually buys you. Nobody else has that dataset. A generic program can't give it to you. And it compounds, because a pattern that's invisible in eight months of logs can be obvious across four years.
An app that makes that record easy to bring in and hard to take out is holding your lab notebook. So the test asks one thing before you commit: can I get all of it back, in a form I can actually use, without asking anyone's permission?
Why one-tap import is the wrong thing to be impressed by
The category has trained lifters to think about portability at the exit door. You notice it on the way out, usually annoyed, usually after the app has already changed under you.
One-tap import doesn't fix that. It just points the pipe in the other direction. Import is a switching tool, built to pull history away from an incumbent and into a newcomer, and it's genuinely good at that job. But it tells you nothing about the pipe running back out, which is a separate piece of engineering and a separate business decision.
Import is a sales feature. Export is a promise.
An app that advertises the first loudly and the second quietly has already told you which one it expects you to use.
Import is a sales feature. Export is a promise.
What the 2026 import wave actually shows
Several trackers launching or relaunching this year have put 'import from the big incumbents in one tap' at the top of their marketing. That's a real shift. Portability used to be something lifters discovered they cared about on the way out. Now it's a headline differentiator, which means the category has conceded that your training history is the asset worth competing for.
Read those landing pages with the Exit-First Test in mind. Look for the matching sentence about export. Is it on the homepage or buried in a help doc? Does it name a format? Does it say which tier gets it?
There's also a legal floor, and it has a ceiling. In the EU, GDPR Article 20 gives people the right to receive their personal data in a 'structured, commonly used and machine-readable format.' That's a right to a file. It isn't a guarantee the file carries set-level weight, reps, RPE, and dates in a shape your next tool can read, and that second thing is what a lifter actually needs.
A legal export and a useful export aren't the same file
GDPR Article 20 requires personal data in a structured, commonly used and machine-readable format. It says nothing about keeping set-level detail, failed reps, RPE, or session notes in a column shape another tracker can import. Test the actual file.
Three questions to ask before you log your first set
Run the test before the program starts. A lifter shortlisting two trackers ahead of a new 5/3/1 block logs two throwaway sessions in each: a squat day with a top set, backoffs, an RPE note, and one missed rep. Then they export from both and open the files on a laptop, outside either app.
Question one: what comes out? A plain CSV or similar open format, one row per set, with columns for date, exercise, weight, reps, RPE, and notes, passes. A PDF summary, an image share, or a file that quietly drops the missed rep doesn't.
Question two: whose data model is it? If the columns match a shape other tools already read, your history can move. If it's an undocumented format only the same app can reimport, the file exists but the door's still locked.
Question three: can you read your history with the app deleted? Open the file in a spreadsheet and find your best triple from the test session. Under a minute means you own the record. Longer, or not at all, and you're renting it.
One more check, and it takes seconds: is export free on the tier you'd actually use, or does it sit behind the paywall?
Question
Passing answer
Red flag
What format does it export?
Open format (CSV or similar), one row per set, with date, exercise, weight, reps, RPE, notes
PDF summary, image share, or a file that drops failed reps or notes
Whose data model is it?
Column shape other tools already read
Undocumented format only the same app can reimport
Can you read it with the app deleted?
Opens in any spreadsheet; your best set is findable in a minute
Needs the app, an account, or a support ticket to view
Is export free on your tier?
Available on every tier, including free
Export is a paid feature or a one-time request
The Exit-First Test. Run it with two throwaway sessions before committing real history.
What changes if export comes first
If the Exit-First Test is right, the evaluation order for a new tracker flips. The import button becomes the least interesting thing on the screen, because every newcomer has one. The export screen becomes the first place you look.
It changes what pricing means, too. An app you can leave in five minutes has to keep earning the renewal, the annual plan, or the lifetime purchase on what it does with your data today. An app you can't leave doesn't have to.
And it protects the experiment. Year-five questions, like which block structure actually moved your total or how your top sets respond in the weeks after a deload, need the whole record in a form you can sort, chart, and argue with. Lose the export and you can only ask those questions inside one company's screens, on its terms.
How Platepusher answers the three questions
Platepusher was built to pass its own test. Export is a one-tap CSV in Strong's exact column shape, the shape this year's one-tap importers are built around, and it's free at every tier, including the free one. Every set, weight, rep, and date comes out as plain rows you can open in any spreadsheet with the app deleted.
Import runs the same way. Drop a CSV from Strong or Hevy and every lift, every set, every date lands as native data, so the history you bring in is something the plateau flag and the charts read from day one instead of an archive you scroll past.
Your records live on a SailQuery-operated database with server-side backups, so one dead phone doesn't cost a year of lifting, and Row Level Security at the database layer keeps each lifter's rows isolated from every other account. Pricing comes in three shapes, monthly $4.99, yearly $29.99, or lifetime $99.99, with no price hike on existing buyers. Whichever you pick, the exit stays open.
That's the design. The record is yours, and the door works in both directions.
Run the Exit-First Test on Platepusher: log a session, export it, open the file. Then bring the rest of your history over.
Platepusher exports a one-tap CSV in Strong's exact column shape, free at every tier. The free tier ships full history, CSV in and out, and Apple Watch logging. Strong and Hevy history imports as native data, so the plateau flag and charts read your past from the first session. Monthly $4.99, yearly $29.99, or lifetime $99.99, with no price hike on existing buyers.