Importing TrainingPeaks biometrics (CSV)

What this import does

The same CSV importer (core/services/csv_importer.py) also recognises TrainingPeaks biometrics exports. Each row in the file becomes a MetricHistory entry: weight, HRV, resting HR, or other tracked biometrics.

Expected CSV format

The importer detects this format by looking for all three of these columns in the headers:

• Timestamp
• Type
• Value

If your TP biometrics export has those columns, it will be recognised.

How to export from TrainingPeaks

In TP, go to your athlete metrics export and select Biometrics. Pick a date range, save as CSV.

How to import

1. Open the activity upload page.
2. Use the CSV import section.
3. Pick the athlete.
4. Drop the file.
5. The importer creates a MetricHistory row for each biometric reading and reports a summary.

What gets created

Each row creates a MetricHistory entry with:

• metric_type mapped from the TP Type field (weight, hrv, resting_hr, etc.).
• value from Value.
• date from Timestamp.
• source tagged as the CSV import.

What does NOT get created

• New activities (use the FIT zip import for those).
• Sport thresholds (FTP, CSS, run threshold). The biometrics CSV is for body composition / recovery markers, not performance metrics. Performance thresholds should come from assessments or the calculators.

Caveats

• Duplicate rows on the same date and same metric type may produce duplicate MetricHistory entries depending on the unique-constraint setup. Inspect after import and clean up if needed.
• The Hub's metric types are predefined; if your TP export contains an unrecognised metric type, that row is skipped.

See also: Importing TP workout notes, Importing TP activities (FIT zip).