Switching from TrainerRoad or TrainingPeaks to N+One: A Migration Checklist for Cyclists
5 min read
Move from TrainerRoad or TrainingPeaks to N+One with a clear checklist: export files, map settings, import workouts, validate data, and run a 7-day test week.
On this page
Photo by Mattia Cioni on Unsplash.
Moving from TrainerRoad or TrainingPeaks to N+One works best when you export, map, import, and validate in one clear migration.
This guide is a practical migration checklist for workouts, files, settings, and schedule flow. It does not make medical claims or promise a fitness result from changing software; the goal is to keep your training data clean and your first week calm.
Before you touch settings, make a plain inventory of what lives in TrainerRoad or TrainingPeaks. Start with your current FTP, zones, recent ride files, planned events, and any coach notes tied to key weeks.
Treat this as your account setup step, not a data dump. If you are new to the app, pair this audit with your first N+One setup so profile fields match the files you bring in.
Your old platform holds context that may not move cleanly through one export. Save a local archive first, then decide what should become active training data inside N+One.
Note current FTP, zones, test date, and weight if used by your files.
Export calendar or plan data before you change dates or delete sessions.
Save key workout files such as .fit, .tcx, or .zwo when available.
Download recent ride files and keep one untouched archive folder.
This keeps the move focused on one clear migration, not a hunt through old screens.
In N+One terms: your training history is system memory, and cleaner memory makes the next decision easier to trust.
Photo by Oleg Kukharuk on Unsplash.
Export the raw files before you rely on screenshots or copied text. Ride files, calendar exports, workout files, and coach notes each answer a different question during the move.
Prioritize files that keep power, cadence, elapsed time, and interval targets intact. For activity imports tied to third-party services, verify imported power data before you use it to judge workouts.
TrainingPeaks and TrainerRoad may name exports differently, and available formats can vary by account and device setup. If an export option is missing, save the clearest local copy and mark what you could not move.
Export structured workouts that you plan to reuse in the next block.
Save calendar or plan files to preserve dates and session order.
Download raw ride files rather than relying only on summary charts.
Copy coach notes, race targets, and plan PDFs into your archive.
Export raw files and a calendar backup from your old platform before changing anything.
Photo by Mattia Occhi on Unsplash.
Bring the files that shape near-term choices: recent rides, current settings, key workouts, and planned events. Leave old sessions in the archive when they no longer help you choose this week’s work.
Set FTP, zones, goals, and events before you judge whether the plan looks right. The profile and training goals guide can help you place those anchors in the right fields.
Do not chase a perfect copy of every past screen. A clean working model beats a cluttered import that hides the sessions you will actually ride.
Import recent .fit or .tcx rides first, then inspect the activity view.
Rebuild key workouts when an old file does not map cleanly.
Enter current FTP and zones before scaling workout targets.
Add travel, illness, or race context as notes rather than hidden assumptions.
The goal is continuity, not a perfect museum of your old platform.
In N+One terms: bring the active signal, keep the archive, and avoid letting stale data steer fresh choices.
Once the files are in place, rebuild the week around anchor sessions first. These are the workouts that define the shape of your plan, such as intervals, endurance rides, and event-specific days.
Keep the early schedule familiar while you test the move. If you want to understand how the system turns goals into sessions, review how weekly plans are built before you edit the whole block.
Avoid making a platform change and a training change at the same time. When too many inputs shift together, it becomes harder to know what caused the new output.
Recreate the most important weekly anchor sessions first.
Keep session order close to your old plan during the test week.
Add race dates and goal notes before filling low-priority rides.
Check workout targets after FTP and zones are set.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Knowledge base — Help articles — N+One knowledge base explains how to browse category articles, access how-tos, training and troubleshooting, and when to use the public KB vs in-app...
- Welcome to N+One — Get started with N+One: an AI cycling coach for adaptive training, readiness and recovery. Learn where to go next in the Beta web app.
- Easy AI Cycling Coach — How N+One Makes Coaching Accessible — N+One is an easy AI cycling coach that turns complex training science into simple, personalized daily guidance. Learn how conversational AI, adaptive...
Validation is where the migration becomes real. Pick one familiar structured workout and one easy ride, then check whether targets, timestamps, and device data look sane.
Use the N+One ride view to compare the imported file against what you expected from the old platform. For a faster daily check, the 60-second dashboard scan helps you catch obvious mismatches before they shape your week.
If the numbers look off, do not assume your fitness changed overnight. First check file source, zone settings, FTP entry, device pairing, and time zone.
Ride one familiar workout and confirm target steps load as expected.
Check power, cadence, elapsed time, and file source after upload.
Compare session feel with the notes you saved from the old plan.
Fix FTP, zone, or time settings before judging the new week.
This protects the first week from bad settings masquerading as training insight.
In N+One terms: your threshold did not disappear; the software anchors around it may have shifted.
Most migration problems are small, but they can still skew your week. Missing intervals, duplicate rides, wrong dates, and mismatched FTP settings are the usual suspects.
Fix one issue at a time, then rerun the same check. If a smart trainer or device is part of your setup, use smart trainer setup checks before blaming the workout file.
Keep a short log of what you changed during the first week. That log helps you avoid solving the same import issue twice.
Missing intervals: rebuild the workout manually from the saved target steps.
Wrong FTP scaling: update FTP, then review targets by percent.
Date shifts: check time zone settings on both platforms.
Duplicate rides: keep the file with the best device data.
After the test week, review whether your plan, files, and daily flow now feel stable. Look for obvious gaps rather than trying to prove the new platform in one ride.
If you work with a coach, send the migrated plan, key ride files, and notes from your test week. If you are self-coached, compare two important sessions with a side-by-side workout review.
This is also the right moment to clean up habits. Set your device syncs, calendar links, and account routine so the next week runs without extra checks.
Review the test week before adding more old workouts.
Send files and notes to your coach if you have one.
Check calendar sync and device links one final time.
Lock settings once the first week looks stable.
If you want day-to-day guidance without second-guessing, let N+One translate your latest training and recovery context into one clear next decision.
In N+One terms: once the system is stable, the next decision can be simple again.
Day 1 — Inventory and export: Save FTP, zones, plan exports, workout files, recent ride files, and coach notes in one local archive.
Day 2 — Import ride history: Bring recent .fit or .tcx files into N+One, then confirm power traces and timestamps look correct.
Day 3 — Recreate anchor workouts: Rebuild the main weekly sessions first, keeping interval structure and target percentages clear.
Day 4 — Enter profile and FTP: Set athlete profile, FTP, zones, race targets, and planned events before reviewing the plan.
Day 5 — First validation ride: Complete one familiar workout or benchmark ride, then compare targets and file data against your archive.
Day 6 — Fix issues: Correct interval mapping, FTP scaling, time zones, duplicate files, and any device sync gaps.
Day 7 — Review and sync: Review the test week, then share the migrated plan and key rides with your coach or trusted peer.
A clean migration follows one order: export, map, import, validate, then ride a short test week before you fully commit. Keep the archive untouched, rebuild the sessions that matter, and let N+One work from current settings rather than stale clutter.
No. Keep a full archive, but only import the history that helps current decisions. Recent ride files, current settings, planned events, and key workouts matter more than every old session.
Rebuild the important workouts manually from the saved targets. Preserve interval intent, target percentages, and duration rather than forcing a broken file into the new plan.
Do not change FTP just because you changed platforms. Enter the current value first, validate targets with familiar rides, then adjust only if your normal testing process supports it.
Yes, if those links are part of your routine. After connecting them, verify one uploaded activity and one calendar item before you rely on the sync for the week.