Supported apps

Supported apps

• Hevy: CSV import and API sync
• Strong: CSV import
• Lyfta: CSV import and API sync
• Motra: Excel (.xlsx) import, pick it from the platform list on the home page
• Other apps: generic CSV import with automatic column detection

What LiftShift needs from exports

To build your analytics, LiftShift needs a few data points from your workout export. Every supported app provides these in its own format, and LiftShift\u2019s parser handles the conversion automatically.

• Exercise name: The name of the movement you performed (e.g. \u201cBench Press\u201d, \u201cSquat (Barbell)\u201d).
• Date: When the workout took place, in a standardised format.
• Reps and weight: How many repetitions you performed and at what load, so LiftShift can calculate volume, intensity, and estimated 1RM.

Common import pitfalls

Regardless of which app you\u2019re coming from, these issues come up often. Check the troubleshooting section on your app\u2019s page for specifics.

• Non-English dates: If your phone\u2019s locale is set to a language that formats dates differently (e.g. DD/MM/YYYY instead of MM/DD/YYYY), some exports may use that locale. LiftShift attempts to detect the format automatically, but mismatches can cause import errors.
• Unit headers: Some exports include unit suffixes in column headers (like \u201cweight_kg\u201d or \u201cweight (lbs)\u201d). LiftShift strips these, but unusual formats can sometimes confuse the parser.
• Exercise name variations: If you rename exercises or use custom names, LiftShift\u2019s muscle mapping may not recognise them. Standard names from each app\u2019s exercise library work best.