How to Migrate from TrainerRoad Without Losing Workouts

Start With the Real Goal

When athletes migrate from TrainerRoad, the obvious concern is simple: do not lose the workouts. The more useful goal is narrower and more practical: keep the data that still changes training decisions.

A completed ride file tells you what happened. FTP changes, skipped workouts, notes, substitutions, illness, travel, equipment changes, and plan edits explain why it happened. If those pieces disappear, the new platform may show a clean training history while quietly misreading the work.

The right move is to treat the migration like a controlled block transition. Back up the raw files, document the decisions that shaped the block, rebuild only the future sessions that matter, and validate the import before you resume structured training.

Pre-Migration Checklist

Do this before cancelling, disconnecting accounts, or relying on the new platform as your training record.

• Export or retrieve completed activity files where available
• Check TrainerRoad completed activity pages for downloadable files, then check connected services for originals or synced copies
• Save FIT files when available, with TCX as a fallback if your next platform accepts it better
• Screenshot calendar blocks that show workout placement, skipped days, substitutions, and planned progressions
• Record current FTP and any historical FTP changes you can still see
• Save notes on key workouts, especially failures, unusually good days, illness, travel, fueling issues, or equipment changes
• Document the intent of the next training block before rebuilding it elsewhere
• Disconnect duplicate sync paths so the same ride does not arrive from multiple services
• Import and validate a small sample set before resuming training

That last step is the safety valve. If a sample import exposes duplicate rides, missing heart rate, or wrong dates, fix the workflow before you move the full history.

Know What Is Portable and What Is Not

The cleanest migration starts by separating training data into categories.

Completed rides

Completed rides are usually the most portable part of the migration because they often exist as activity files. If you can access FIT or TCX files, keep them. They are the closest thing to the original record of power, cadence, heart rate, elapsed work, and device behavior.

Look for completed ride files in a few places:

• The completed activity page in TrainerRoad, if an export or download option is available
• Garmin Connect, if the ride was recorded on a Garmin device or synced there
• Strava, if TrainerRoad or your device sent the activity there
• TrainingPeaks, if it received completed rides from TrainerRoad, Garmin, or another source
• intervals.icu, if it has already pulled the completed activity from another service
• Your head unit, cycling computer, watch, phone, or computer storage, if that device recorded the original session

If you have multiple copies, keep the file that appears closest to the original recording source. A synced copy can be useful, but an original head-unit or trainer-recorded file is often the best starting point for preserving channels cleanly.

Planned workouts

Planned workouts are less portable. A future workout may have a name, targets, intervals, calendar placement, and notes, but it may also sit inside TrainerRoad-specific plan logic. That logic can include progression, substitutions, adaptation decisions, and the relationship between surrounding sessions.

Do not expect that entire layer to transfer cleanly. You may be able to recreate the workout definition, but the reason it was placed there often needs to be rebuilt manually.

Workout definitions

A workout definition is the structure of a session: intervals, targets, recoveries, and sometimes cadence prompts or text. This can sometimes be recreated in another platform if the session is important enough.

But the workout name is not the adaptation. If the next platform has a similar threshold or VO2 max workout, that may be enough. Chasing an exact name match can create false precision while missing the larger objective.

TrainerRoad-specific plan logic

This is the least portable layer. Adaptive decisions, progression context, plan phase, and why a workout was substituted are not just files. They are interpretation. If that interpretation matters, capture it in plain language before you leave.

A useful note is simple: 'This block was moving from sweet spot durability toward race-specific threshold work, with one reduced week due to travel.' That single sentence may be more valuable than recreating every future workout title.

Back Up Completed Rides Before You Cancel

Before cancelling access or disconnecting integrations, make a complete backup of completed work.

Start inside TrainerRoad. Open recent completed rides and check whether each activity has a downloadable file. Save the file with a clear naming pattern that includes the date and a short workout description. If the file is available as FIT, keep that as the primary copy. If TCX is the only practical option, save it too. Do not rely only on screenshots, calendar summaries, or totals.

Then check connected services. Garmin Connect, Strava, TrainingPeaks, and intervals.icu can act as secondary backups if they received the completed activity. Your head unit or watch may also hold the original file, especially for outdoor rides. If you used a computer or phone app for indoor sessions, check local storage or the device export options before wiping anything.

Pay special attention to:

• Completed indoor ride files
• Outdoor rides that were part of the plan
• Tests and benchmark sessions
• Workouts with failures, backpedals, pauses, or manual reductions
• Calendar screenshots showing workout placement
• Personal notes attached to important sessions
• Skipped workouts that changed the shape of the block

Skipped workouts are not empty space. They often mark fatigue, illness, travel, work stress, or poor fueling. If those notes vanish, the block can look smoother than it was. That matters because a coach, algorithm, or future review may assume you absorbed the full load when you actually adapted the plan to survive it.

Preserve FTP Changes, Zones, and Equipment Context

FTP is not just a profile setting. It is the translation layer between the plan and the body.

Before importing into the new platform, write down your current FTP and any historical FTP changes you can still recover. Include why each change happened if you know it: a test, a manual adjustment, a race result, a block of failed workouts, or a stretch where workouts became too easy.

This prevents a common failure mode. If old threshold work is interpreted against your current FTP instead of the FTP used at the time, the session can look easier or harder than it really was. That can distort how you read progress, durability, and fatigue across the block.

Do the same for zones if you use custom settings. Different platforms may classify intensity differently, so the same ride can land in a different bucket after import. That does not automatically mean the file is wrong, but it does mean you should check the assumptions before trusting the dashboard.

Also document power-source changes. Moving from trainer power to a crank, pedal, or hub power meter can masquerade as a fitness change. If the numbers jump or dip around the same time your recording source changed, that is not a training insight until you rule out measurement drift.

Useful context to save:

• Current FTP
• Historical FTP changes and the reason for each change
• Any custom zone settings you care about preserving
• Power source changes
• Heart rate strap changes if the data quality changed
• Indoor trainer or head-unit changes
• Notes on heat, illness, travel, or fueling during key workouts

If you later use a tool like the FTP estimator, these anchor files and notes help keep the estimate grounded in the actual conditions of the work.

Rebuild the Future Plan From Intent

Future workouts are where migrations often get messy. The instinct is to copy the calendar exactly. That is rarely the best use of time.

Instead, identify what the next block was supposed to accomplish. Was the goal aerobic volume, threshold durability, VO2 max repeatability, race-specific cadence work, or recovery before an event? Once that is clear, rebuild the key sessions in the new platform around the same physiological target.

Start with the anchors:

• Key interval sessions
• Long endurance rides
• Recovery days that protect quality
• Race simulation or event-specific sessions
• Tests or benchmark days

Then rebuild the surrounding week so the stress and recovery sequence still makes sense. If a hard workout originally sat before an endurance day, do not reverse that order casually. The order changes the fatigue state, and the fatigue state changes the training effect.

This is also the moment to edit the plan if your goals changed. Do not preserve a block built for an old event just because it is on the calendar. Migration should carry forward useful history, not lock in stale assumptions.

Prevent Duplicate Syncs Before Importing

Duplicate sync paths are one of the easiest ways to corrupt a clean migration.

If TrainerRoad sends a ride to Strava, Garmin sends the same ride to Strava, and the new platform also pulls from Strava, one completed workout can become multiple activities. That inflates training load, makes the week look harder than it was, and can push recovery recommendations in the wrong direction.

Before importing, decide which service owns each type of file.

A simple setup might be:

• Head unit or trainer app records the original activity
• Garmin Connect or Strava stores the completed file
• The new training platform pulls from one chosen source
• Analysis tools like intervals.icu receive data downstream rather than feeding the same ride back upstream

The exact workflow matters less than having only one path for each completed activity. After import, search for duplicate rides on the same day with similar duration and power. Delete or merge duplicates before you resume structured training.

Import a Sample Set First

Do not move everything and hope the new calendar is right.

Import a small representative sample first. Choose an easy endurance ride, a hard interval session, a test or benchmark workout, an outdoor ride, and one session with important notes or unusual execution.

Compare each imported file against TrainerRoad, your backup, or the connected service that stored the original. You are looking for systematic errors, not perfection on every label.

Check whether:

• The ride appears on the correct day
• The full session imported rather than a partial file
• Power is present where it should be
• Cadence is present where it was recorded
• Heart rate is present where it was recorded
• Indoor and outdoor rides are categorized sensibly
• Notes or tags survived where you need them
• The new platform used the correct FTP or zone assumptions
• Duplicate syncs did not create multiple versions of the same ride

If the sample set is broken, stop. Fix the source, file type, or sync path before importing the rest.

Verify Power, Cadence, and Heart Rate After Import

Power is the main language of structured indoor training, but not every file tells the same story. Check whether the recorded power came from the trainer, a power meter, or another source. If your setup changed during the block, note it in the new platform.

Cadence explains how the power was produced. If cadence disappears during import, you lose a useful execution signal, especially for low-cadence strength work or high-cadence efforts.

Heart rate is slower and noisier than power, but it helps explain fatigue, heat load, fueling, and aerobic response. A workout completed at target power with unusually elevated heart rate is not the same training read as a workout completed comfortably.

These checks matter because migration errors can look like fitness changes. Missing heart rate can make aerobic control invisible. A changed power source can look like sudden improvement. Duplicate files can inflate load. Lost notes can hide the reason a block was reduced.

Final Validation Table

Use this before calling the migration finished.

Original data field	Where to find it before leaving	Where it should appear after import	Problem it prevents
Completed ride file	TrainerRoad activity page, connected services, head-unit storage	Activity detail page in the new platform	Missing or partial workout history
FIT or TCX file	Downloaded backup folder or device export	Imported activity file with full channels	Reliance on screenshots or summaries
Workout date	TrainerRoad calendar and backup screenshots	Correct calendar day in the new platform	Misread training sequence
Power data	Original file, Garmin Connect, Strava, TrainingPeaks, intervals.icu	Power chart and interval detail	False fitness trend or unusable intervals
Cadence data	Original activity file or connected service copy	Cadence channel in ride analysis	Lost execution context
Heart rate data	Original activity file or connected service copy	Heart rate chart and session summary	Thinner fatigue and fueling interpretation
FTP history	TrainerRoad profile, test results, manual notes	Athlete settings, history note, or coach note	Old workouts judged against the wrong threshold
Workout notes	TrainerRoad calendar, screenshots, manual log	Notes field or migration note	Lost illness, travel, fatigue, or fueling context
Planned block intent	Calendar screenshots and your written summary	Rebuilt plan notes in the new platform	Copying workouts without preserving purpose
Sync path	Account integrations and connected services	One clear source feeding the new platform	Duplicate rides and inflated training load

Set Up Future Training So History Stays Connected

Once the import is clean, make the next phase easy to interpret.

Write a short migration note in your training log. Include when you moved platforms, what was imported, what was rebuilt manually, and which fields may be incomplete. If power source, FTP, zone model, or sync workflow changed at the same time, say so clearly.

Then maintain a lightweight habit after each training block:

• Back up important completed files
• Record FTP changes with the reason behind them
• Keep notes on key workouts, not every workout
• Mark equipment changes that affect power or heart rate interpretation
• Review whether planned training still matches the event target

The platform should organize the work. It should not be the only place where the meaning of the work exists.

The Bottom Line

To migrate from TrainerRoad well, move the useful training record rather than trying to recreate the platform.

Completed files preserve what happened. FTP history explains how intensity was defined. Notes explain why the plan changed. Rebuilt future sessions keep the next block aimed at the right adaptation.

If you export the raw files, document the key decisions, prevent duplicate syncs, and validate a sample before training resumes, you can leave TrainerRoad without losing the thread of the work.