Switching from Hevy
A Hevy export has one row per set. For each set Athverge reads the workout, the exercise, the weight, the reps, the set type and your RPE, and where they are present also the distance, the time and your notes.
Warm-up sets, sets to failure and drop sets come in as the same set type. A set type the app does not know becomes a normal set, so nothing disappears.
If the file’s header says kilos or pounds, the app uses that. If it only says "weight", you choose the unit yourself before you import. Older and newer files both work: the app finds the columns by name, not by position.
Switching from Strong
From a Strong export, too, Athverge reads one row per set: date, workout, exercise, set order, weight, reps, distance, seconds, notes and RPE.
The weight is the most sensitive point. Newer files do not say whether it is kilos or pounds. If the unit is in the header, that wins; otherwise you choose it yourself before you import. A bench press in pounds that came in as kilos would skew your records for good.
The app recognises a warm-up set by a W in the set order. It also reads older exports with semicolons instead of commas.
Switching from MyFitnessPal
From MyFitnessPal comes the nutrition summary: one row per meal per day, with calories, protein, carbohydrates, fat and fibre.
If your export only gives day totals, each day comes in as one row under a meal you choose yourself. If a total row sits next to the meals of the same day, the app skips it; otherwise every day would count twice.
Meal names in Dutch, English, Spanish or German are recognised. Anything the app does not know goes under Snacks.
