Five years of lifting data, one acquisition away from a dead file.

The morning the log stops belonging to you

Five years of training data feels permanent until the company holding it changes hands. The lifter opens the app before a heavy squat day and finds a new login flow, a new price sheet, or a banner with a shutdown date on it. Every top set since their first real program is in there. So is every RPE note, every deload that worked and every block that didn't.

And this happens. Fitness apps get acquired, folded into bigger platforms, repriced, or switched off. Sometimes the export option is easy to find. Sometimes it's buried, or it arrives too late, or it never shows up at all.

Different companies. Different causes. The lifter gets the same result each time: the log stops compounding the day somebody else's plans change.

The hostage-log problem

A long training log gets more valuable with every entry. Year one tells you what you lifted. Year five tells you how you respond to a volume block, how long a peak holds, and which lift stalls first when sleep falls apart. You can't rebuild that record, because you can't go back and train 2022 again. (The case for using that history rather than just storing it is in [Your training history is the experiment](/articles/your-history-is-the-experiment).)

The threat that ends the compounding isn't a clunky import screen. It's the company. Acquisition, pivot, or shutdown turns the log into one of two things. A hostage: still there, but repriced, moved behind a new tier, or reshaped by an owner with different priorities. Or a dead file: exported in a hurry and readable by nothing that understands it.

Call it the hostage-log problem. Most lifters don't think about it until it's already happening to them.

Is a CSV export enough to protect your training data?

Logger apps usually answer data risk with a checkbox: we support CSV export. That's true, and on its own it means very little. A file proves the data can leave. Whether it arrives in usable shape is a separate question.

Most writing about logger data, including earlier coverage of import friction, treats failure as technical: a broken parser, a timezone bug, a column that didn't map. Those problems are real. But an acquisition doesn't break the parser. It changes who decides what the export contains, which tier it lives on and how long it stays available.

So the useful questions are harder than "is there a button." Can you query your history after it leaves? Do RPE and set context survive, or does everything flatten into weight and reps? Does the receiving app understand what it got, or does it file five years of squats under a lift name it's never seen?

Six landing pages, one sentence

Competitors' own marketing is the clearest sign that lifters feel this risk right now. Look at how the rivals to the two biggest incumbent loggers pitch themselves. Many of them run near-identical "switch from" copy aimed squarely at those apps' users.

Marketers write whatever copy converts. When that many of them land on the same promise, it tells you lifters with long histories are worried about getting stuck, and "bring your data" is the line that moves them.

But switch copy only sells the arrival. It rarely mentions how you'd leave next time. A logger that imports your history and then holds it the same way the last one did has just moved the hostage to a new building.

How an acquisition plays out for a five-year log

Here's how it can go. A lifter four-plus years into a 5/3/1-style progression, with a few hundred sessions logged, gets the email. The app has been acquired, the old version is being retired, and export is open until a date a couple of months out.

The export works. The file opens. Then the problems start. The RPE column is empty because the old app kept RPE in a field the export skipped. Warm-ups and top sets share rows with no set type, so every session reads like a pyramid of working sets. Bodyweight entries mix pounds and kilos with no unit column.

The import into the next app goes worse. "Squat (Barbell)" and "Back Squat" don't match, so the history splits into two separate lifts. The estimated-max chart starts over from week one. Every number technically made it across. The continuity, which is what made those numbers worth keeping, got lost on the way.

Choose a logger the way you'd choose a bank

If the hostage-log problem is real, the order of questions changes. In year one, features matter less than the exit, because the exit is the only part of the app that has to keep working after the company stops caring about you.

Before session one, check three things. Export is on the free tier, where a new owner can't quietly put it behind a paywall. The format is one other loggers already read. And access to your history doesn't depend on a renewal someone else gets to reprice.

Then actually run an export. Once per training block is enough. If you've opened a file and re-imported it once, you know it works as a backup. If you never have, you're hoping it does.

Test the exit in year one. By the time the shutdown email lands, the terms are someone else's.

How Platepusher handles the exit

No logger can promise its company will never be sold, and Platepusher doesn't claim otherwise. What a logging app can do is make leaving uneventful.

CSV export is one tap, free on every tier, and written in Strong's exact column shape, so the file lands in a format other loggers already import. Partly. Platepusher's CSV export includes set-level notes and workout-level notes, alongside date, workout, exercise, set order, weight, reps and timed-set seconds. It has no RPE column, so an article shouldn't say the export includes RPE. The plan CSV export also carries notes but no RPE. The free tier keeps full history, CSV in and out, and the watch companion. Row Level Security at the database layer blocks cross-user reads even if the app itself has a bug. Server-side backups mean a dead phone doesn't cost a year of lifting.

Pricing comes in three shapes: monthly $4.99, yearly $29.99 or lifetime $99.99, with the same Pro features on each (the reasoning is in [the subscription-trap breakdown](/articles/subscription-trap-fitness-apps)). Lifetime deals with the hostage half of the problem. A license paid once has no renewal date to reprice. It won't stop a shutdown, and nothing can. That's what the export is for.

The lifter picks the tier. The history is theirs to take either way.