
Switch from TrainerRoad or TrainingPeaks to N+One with a clear cyclist migration checklist: export, map zones, import workouts, verify syncs, and monitor two weeks.
On this page

Photo by Markus Spiske on Unsplash.
Start by exporting everything, then import and verify in N+One over a two-week window.
A structured move keeps your training log, recent tests, zones, workout files, and coach notes from drifting apart. This guide stays practical because the only grounding source provided is a PubMed search page, not a specific physiology paper. Where evidence is not available, it avoids firm claims about adaptation and focuses on clean data handling.
You may be switching because your workflow changed, your coach setup changed, or you want one place for training and recovery context. Start with your N+One account setup so profile fields match the data you bring across.
The first two weeks are not a fitness test. They are a check on files, zones, workout shape, device sync, and how the new view labels your work.
Late-season riders often move platforms after goal events, when the risk of disrupting a key race week is lower. If you are heading into base, keep the training pattern familiar while the software settles.
Expect load views to differ; do not map values one-to-one.
Match workouts by name, goal, and intensity, not platform ID.
Re-enter block notes and coach cues by hand.
Back up key rides before you change anything.
In N+One terms: treat the first two weeks as a reconciliation phase, then trust the next decision.

Photo by Munbaik Cycling Clothing on Unsplash.
Before you touch settings, make one folder for the move and keep it unchanged. If you also use Strava, review how N+One reads imported Strava history before you decide what to sync.
Save ride files, workout files, calendar exports, test notes, and coach comments as separate items. Screenshots can help, but raw files are easier to check later.
Name the folder with the date, then copy it to cloud storage and a local drive. That gives you a fall-back if a file maps poorly or a subscription is paused too soon.
Export up to the last year if available.
Download key FIT, TCX, CSV, and ERG files.
Save FTP, zone, RPE, illness, and travel notes.
Keep one cloud copy and one local copy.
Export your historical data and archive a copy before changing platforms.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Training load values can look different after a move because each platform may group, label, or display data in its own way. Do not treat a new chart as proof that your body changed overnight.
Use week-over-week trends, similar ride types, and known hard sessions as anchors. The aim is not a perfect copy of the old dashboard, but a stable working model.
If you are unsure what matters each day, use the N+One Today card as your short check. Keep the old platform open until your main numbers make sense.
Compare trends, not one isolated load score.
Check hard rides, races, and long rides first.
Mark major efforts with clear notes.
Build a fresh baseline across the validation window.
Workout files are not the same as workout intent. A file may move across, yet still lose warm-up steps, target ranges, or planned rest blocks.
Open several representative sessions before you ride them. Include one easy endurance ride, one interval workout, one long ride, and any race-like session you plan to reuse.
When a workout imports poorly, rebuild it instead of forcing a broken file. Preserving the stimulus matters more than preserving the old file name.
Inspect interval length and target range.
Check warm-up and cool-down blocks.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Profile and Training Goals — Keep your athlete profile and training goals accurate so N+One's AI personalizes workouts—update FTP, preferences, and targets in Settings.
- Your First Integration Order: Strava, Garmin, WHOOP — What to Connect First — Connect Garmin, Strava, and WHOOP in the right order: primary device first, Strava second, recovery data after the ride stream is clean.
- Invite a Training Partner Mentally: Use Shared Goals Without Shared Accounts — Use shared goals with a training partner without sharing accounts. Set one goal, two progress signals, privacy boundaries, and a 7-day starter protoc...
A plan is more than a row of workouts. It also holds race dates, travel weeks, coach cues, and the reason a workout exists.
Move the context that shapes choices first. Add goals, dates, and limits in your profile, then use trackable goal setup to keep the plan tied to real outcomes.
If you work with a coach, send a short migration note after the first import. Include what moved cleanly, what was rebuilt, and what still needs review.
Move coach notes into plan comments.
Set zones before bulk edits.
Rebuild broken workouts in N+One.
In N+One terms: preserve session intent over exact file shape.
Your FTP or critical power value should not be copied blindly if the test date, protocol, or recent training context is unclear. A wrong anchor can make every target feel slightly off.
Use two familiar sub-threshold sessions during the validation window before you change all zones. If both sessions feel and read as expected, the anchor is likely usable for planning.
If you need a new test, use the same protocol you have used before when possible. Changing the test and the platform at once makes the result harder to read.
Verify imported FTP or CP before broad zone changes.
Use two familiar sub-threshold rides as checks.
Retest only with a repeatable protocol.
Keep early targets conservative if unsure.
Rebuild blocks, not just single workouts.
Add race dates and travel constraints.
Book one short review in the first week.
The validation window is where you catch small errors before they shape your block. Track device sync, file source, workout targets, sleep notes, and how the session felt.
Use a short daily scan rather than a deep audit after every ride. The 60-second dashboard review is enough when the basics look stable.
Do not raise load while core settings are still in doubt. First fix the file, threshold, zone, or device issue, then resume normal progression.
Log sleep, soreness, and fatigue each day.
Check sync after every key ride.
Compare similar sessions before and after the move.
Pause load increases if numbers diverge.
In N+One terms: make the system stable before asking it for a harder next step.
Most migration issues are setup errors, not rider errors. Wrong dates, missing intervals, duplicate files, and stale zones can all make a normal week look strange.
Fix one issue, then rerun the same check. If you change zones, file source, and workout structure together, you will not know which fix worked.
Keep old subscriptions active until the validation window is complete. Once N+One is stable, pause the old tool and keep the archive untouched.
Short intervals: edit blocks by hand.
Load jump: check window and import scope.
Missing notes: paste coach context into the plan.
Duplicate rides: keep the best device file.
Export up to 12 months of activity history and download FIT, TCX, CSV, or ERG files for key sessions.
Save recent test results, FTP or CP notes, RPE, illness, travel, and coach comments in one migration folder.
Import workouts into N+One, then inspect interval structure on five representative sessions before riding them.
Standardize intensity zones in N+One to match your chosen power or heart rate basis before bulk updates.
Verify threshold settings with two familiar sub-threshold sessions during the validation window before changing every target.
Recreate coach notes, goal dates, macrocycle blocks, and priority session flags inside N+One.
Sync devices and confirm future rides write to N+One or through your chosen cloud bridge.
Monitor subjective recovery and week-over-week trends for two weeks, without raising load while settings are uncertain.
Resolve mismatches by editing workouts, smoothing abrupt load changes, and retesting only when needed.
Schedule a brief coach-athlete review after the validation window to finalize thresholds and plan progression.
Start by exporting everything, then import and verify in N+One over a two-week window. Keep the archive untouched, rebuild the sessions that matter, confirm thresholds with familiar rides, then resume progression once the system is stable.
No. Keep a full archive, but bring in the history that helps current decisions. Recent rides, tests, key events, and recurring workouts matter more than a perfect copy of every past file.
Not automatically. First verify the imported value with familiar sub-threshold sessions. Retest only if the old value is stale, unclear, or clearly mismatched to current training.
Wait until the two-week validation window is complete. Confirm files, zones, workouts, device sync, and coach context before you pause or cancel the old subscription.
Keep the handoff simple. Share the exported files, rebuilt blocks, key notes, and validation findings so your coach can review the plan without guessing what changed.