Coming from TrainingPeaks
Your numbers were never in TrainingPeaks.
They came from your watch. TriHonu reads them straight from Garmin — every year of them, not a copy of a copy. What TrainingPeaks holds that Garmin doesn’t is what you and your coach wrote, and that comes across too.
What comes across
Your training history
Straight from Garmin, as far back as your account goes. TrainingPeaks’ FIT export and metrics.csv are its copy of that same watch data — you don’t need them, and you shouldn’t have to trust a copy.
What you and your coach wrote
Corrected session titles, coach comments, your own notes, RPE and feel — attached to the right session on the right day. This is the part that exists only in TrainingPeaks, and the part worth moving.
Nothing taken on trust
You see exactly what would change before a single row is written, including an honest count of what cannot come across. Run the same file twice and the second run changes nothing.
How it goes
Connect Garmin
TriHonu imports your history — activities, sleep, HRV, weight. This is where your training actually lives.
Export from TrainingPeaks
One file matters: workouts.csv, from a TrainingPeaks Workout Export. You can leave the rest of the zip alone.
Upload, review, apply
Settings → Coming from TrainingPeaks. The plan comes first; nothing is written until you say so.
What it won’t do
The import never creates a session. It attaches TrainingPeaks’ writing to activities Garmin already gave you — so a session you logged in TrainingPeaks but never recorded on a watch has nothing to attach to, and sessions you planned and never did are skipped. Both are counted and shown to you before you commit, rather than discovered afterwards. And your titles are not blindly overwritten: Garmin’s own names are often the better ones, so a TrainingPeaks title only wins when it actually says more.
Nobody goes the distance alone.
TriHonu is invite-only while it’s in beta. Ask for a place and we’ll be in touch.