Importing TrainingPeaks activity history (FIT zip)

What this import does

TrainingPeaks lets you export a full activity history as a ZIP file containing .fit.gz (gzip-compressed FIT) files, one per workout. Grepiac's activity uploader accepts this ZIP directly and processes each file inside.

How to export from TrainingPeaks

1. In TP, go to your athlete's calendar.
2. Use the bulk activity export (typically under settings or via TP's customer support if not exposed in the UI).
3. Save the resulting ZIP locally.

How to import in Grepiac

1. From the coach dashboard, click Upload activities.
2. Pick the athlete.
3. Drop the ZIP file.
4. Grepiac: * Extracts the FIT.gz files inside. * Decompresses each to a plain FIT. * Runs the standard FIT parser on each. * Creates one Activity row per file.
5. The upload page shows a summary of files processed, activities created, and any that failed.

Bring in the notes & comments too

The FIT zip carries the activity data (power, HR, pace, laps). It does NOT carry the coach/athlete comments, the workout description, RPE, or feeling — TrainingPeaks keeps those in a separate export.

To bring those across, use the workout notes CSV import, after the activities are in (the notes match to existing activities):

1. In TP, export the Workouts report as a CSV for the same date range you just imported.
2. On the same Upload activities page, pick the athlete and drop the CSV.
3. Grepiac matches each row to an existing activity by date + sport and appends the description, coach comment, athlete comment, RPE, and feeling to that activity's notes (visible on the activity and as the note badge on the calendar). Rows with no matching activity are reported as "unmatched".

Full walkthrough: Importing TrainingPeaks workout notes (CSV). Order matters: import the activity files first, then the notes CSV.

Hard caps

There are limits on the size of any single ZIP to keep the import bounded. A single export with several years of data may need to be split into multiple smaller exports (half-year or full-year chunks typically work).

If a ZIP fails with a "too large" error, split the date range and re-export.

What gets created per FIT

For each FIT inside the ZIP:

• One Activity row with all extracted metrics (AdjP, IF, Load, mmp_curve, etc.; see Activity FIT parser metrics).
• One ActivityLap per lap in the file.
• The source file stored on disk for later re-parsing if needed.

What does NOT get imported

• TP workout notes, RPE, feeling: use the workout notes CSV for those.
• Biometrics: use the biometrics CSV.
• Macrocycle plan structure from TP. You build the plan in Grepiac separately.

Common gotchas

• Files with no power data still import; they just have no power metrics.
• Old TP files (pre-2017 or so) sometimes use a non-standard FIT extension that the parser does not recognise. These rows are reported as failed.
• Duplicate uploads: if the same FIT was already uploaded, the importer may create a duplicate Activity. Check for duplicates after the import.

Recommended workflow for a new athlete

When taking on an athlete with a TP history:

1. FIT ZIP first for activity history.
2. Workout notes CSV second to populate the notes on those activities.
3. Biometrics CSV third for weight / HRV / RHR history.

This produces the cleanest result.

See also: Activity FIT parser metrics, Importing TP workout notes, Importing TP biometrics.