How to Migrate from GoldenCheetah Cleanly

Image generated by our model.

All posts

goldencheetah

How to Migrate from GoldenCheetah Cleanly

A practical GoldenCheetah migration guide for preserving ride files, power history, zones, models, and the context behind your training data.

November 18, 2026 By Neverchill Team Written by our model, not by a person.

Why the migration has to be deliberate

If you are planning to migrate from GoldenCheetah, the risk is not just losing a few old ride files. The bigger risk is losing the continuity that makes your training history useful.

GoldenCheetah is not only a place where activities live. It is also where your athlete profile, zones, critical power settings, custom charts, and model assumptions shape how those activities are interpreted. Move the ride files without preserving that context and the new platform may show the same workouts while telling a different training story.

That matters because endurance training is trend-driven. Fitness, fatigue, durability, pacing, and repeatability all depend on clean historical data. If a migration strips sensor streams, duplicates activities, shifts timestamps, or resets zones without warning, future analysis starts from a distorted baseline.

The goal is not simply to complete a GoldenCheetah export. The goal is to preserve the information that actually drives decisions.

Pre-migration checklist

Do this before changing anything in GoldenCheetah or importing a large archive into a new platform.

  • Back up the full GoldenCheetah athlete directory, not only exported activities
  • Copy original activity files from your head unit, cloud sync folder, downloads folder, or device archive where they still exist
  • Record current critical power, FTP, power zones, heart rate zones, athlete settings, and sport settings
  • Screenshot the key charts you use to judge training load, peak power, critical power, fatigue, freshness, and zone distribution
  • Export a small representative activity set first, then test-import 5 to 10 rides into the destination platform
  • Verify the test import at the trace level before running the full import
  • Run the full import only after you know which file format and settings work cleanly

That sequence is slower than simply dumping every file into a new platform, but it protects the signal. The most expensive migration mistake is not a failed import. It is a successful-looking import that quietly changes the data you make decisions from.

Back up GoldenCheetah before touching exports

Start with a full local backup. GoldenCheetah keeps each athlete as a library or athlete folder on your computer, and that folder can include far more than the activities you see in the diary. It may include settings, chart configuration, cached data, imported files, downloaded files, and other athlete-specific material depending on your setup.

Find the athlete directory from inside GoldenCheetah first. On most setups, use the application preferences or options area to confirm the athlete library location. If you are not sure where it is, search your computer for the athlete name used in GoldenCheetah and confirm that the folder contains GoldenCheetah athlete data rather than only exported ride files.

Then close GoldenCheetah completely. Do not copy the library while the application is open and writing data. Once it is closed, copy the entire athlete folder to a separate location such as an external drive, cloud backup folder, or dated local archive.

The practical rule is simple: before exporting, create a backup that lets you put GoldenCheetah back exactly as it was. If the migration goes sideways, you want recovery to mean replacing a folder, not rebuilding years of settings by memory.

What GoldenCheetah data is worth preserving

Before exporting anything, separate your data into three practical categories.

Activity files

These are the individual rides and workouts. For cyclists training with power, the priority is preserving the original sensor data as completely as possible.

If the original FIT files still exist from your head unit, training app, device sync folder, or prior download archive, copy those first. They are the closest link to what the recording device captured. GoldenCheetah can import and export activity data, but you should not assume every installation can recreate a rich original FIT file after the fact.

If original FIT files are unavailable, use GoldenCheetah exports as the next layer. Depending on your version, selected activity, and build, export options may include FIT, TCX, CSV, PWX, or similar activity formats. Treat these as migration files, not as proof that every original field survived unchanged.

Athlete configuration

GoldenCheetah settings influence interpretation. Athlete profile details, sport categories, power zones, heart rate zones, critical power configuration, and metric preferences all affect how the same ride appears in analysis.

If your new platform uses a different threshold concept, a different model, or a different way of calculating training load, the same ride history can produce different signals. That is not automatically wrong. It just needs to be understood rather than discovered later when your trends look strange.

Derived performance history

Critical power curves, peak power values, modeled fitness, fatigue, freshness, and zone distribution are derived from activity data plus assumptions. Preserve them as reference material through screenshots, chart exports, or notes, but do not expect every platform to recreate them exactly.

This is the key migration distinction: activity files are the source material, while models are interpretations of that material. Protect both, but validate them differently.

Export original files first, then GoldenCheetah files

A clean GoldenCheetah migration should have layers.

Copy original activity files where they exist

Look outside GoldenCheetah before relying on a converted export. Check the folders or services that originally fed your library: head-unit downloads, sync folders, training app exports, email attachments, backup drives, and device archives.

Preserve those original files in a separate folder before importing anything into the new platform. If you later discover that an exported file is missing laps, GPS, elevation, or developer fields, the original file gives you a fallback.

This is especially important for FIT guidance. The best approach is not to assume GoldenCheetah can always export a perfect rich FIT file. The better approach is to preserve original FIT files where they exist, then use TCX, CSV, PWX, or other GoldenCheetah exports as secondary references depending on what GoldenCheetah and the destination platform support.

Export selected activities from GoldenCheetah

Use GoldenCheetah to export a controlled sample before exporting the entire library.

In the activity list, diary, or sidebar view, select a small group of representative rides. Use the activity export command from the menu or right-click context menu, depending on your GoldenCheetah version. Export the same sample in the richest activity format supported by both GoldenCheetah and the destination platform. If more than one useful format is available, export more than one version for testing rather than guessing.

In practical terms:

  • Try FIT when GoldenCheetah offers it and the destination platform imports it cleanly
  • Try TCX when GPS structure, laps, or compatibility matter
  • Use CSV when you need to inspect the exported values or troubleshoot sensor streams
  • Keep any original device files separate from GoldenCheetah-generated exports
  • Do not mix multiple versions of the same ride into the full import until you know how the destination platform handles duplicates

The export format is not the win. The win is a file that imports with the data streams you need intact.

Export chart data where useful

GoldenCheetah charts and models may not move cleanly into another platform. For the charts you actually use, preserve a reference copy.

For visual comparison, take screenshots. For charts that allow data export, use the chart context menu or available export option to save the underlying values as CSV. This is useful for reference, but do not treat a chart CSV as a substitute for the activity archive. It tells you what GoldenCheetah calculated. It does not necessarily preserve the ride.

Record zones, CP, FTP, and settings before import

Do the settings audit before the migration, not after. Once you are inside a new system, it becomes harder to know whether a discrepancy came from the export, the import, or the new platform's calculations.

Record the settings that shape interpretation:

  • Athlete name and profile details
  • Bike and sport categories
  • Power zones
  • Heart rate zones
  • Current CP and FTP values if you use both
  • Critical power model settings
  • Metric preferences
  • Custom charts, fields, or filters you rely on

This is also the right time to decide what you actually trust. Many athletes carry old zones forward long after their physiology has changed. Migrating outdated settings perfectly is not a win.

The cleanest approach is to preserve the old state, recreate it in the new platform if continuity matters, and then make any changes intentionally. If you later update threshold with an FTP estimator or a testing protocol, you will know exactly where the break in interpretation occurred.

That matters when evaluating trends. If zone distribution changes after migration, it may reflect different training. It may also reflect different zone boundaries. Documentation keeps those two explanations separate.

Test import before the full migration

Do not make the first import the whole library. Pick a small set that represents the edge cases in your training history.

Choose rides such as:

  • A structured interval workout with power targets
  • A long endurance ride
  • A race or hard group ride
  • An indoor trainer session
  • A ride with meaningful elevation changes
  • A file from an older recording device
  • A manually imported or edited activity

Import that sample into the destination platform. Then compare each ride against GoldenCheetah.

Do not stop at the activity summary. Open the ride and inspect the trace. Confirm that power, heart rate, cadence if used, GPS, elevation, laps, pauses, and timestamps appear as expected. A ride can show duration and average power while still losing the data that made it useful.

If one export format drops information, test another before proceeding. FIT may be the best option when original FIT files exist and the destination platform handles them well. TCX may behave better in some workflows. CSV may be better for inspection than for complete activity reconstruction. The right answer is the format that preserves the needed fields in the destination platform, not the one that sounds best in theory.

Run the full import in a controlled way

Once the test import is clean, run the full migration with the same logic.

Keep the import folder organized by source and format. For example, keep original device files separate from GoldenCheetah exports. If you import both an original file and a converted export for the same ride, the destination platform may create duplicates. That can inflate volume, load, and apparent consistency.

A practical sequence is:

  • Import original files first when they are available and complete
  • Check whether the destination platform detects duplicates
  • Use GoldenCheetah exports to fill gaps, not blindly duplicate the whole archive
  • Keep CSV exports available for troubleshooting rather than making them the primary import unless the destination platform requires it
  • Pause after each batch and check the calendar before continuing

This controlled approach makes errors easier to isolate. If everything is imported at once, a missing data stream or duplicate pattern can be hard to trace back to a specific source.

Verify the migrated library

Quality control is the most important step after import. This is not busywork. Small data errors can distort long-term trends, especially when they affect key workouts, race files, or high-load training blocks.

Start with calendar coverage. Compare GoldenCheetah and the new platform side by side. Look for blank periods that should contain rides, unexpected clusters of duplicate rides, and activities that landed on the wrong day.

Then inspect the files that matter most. Key workouts, races, tests, long endurance rides, and unusual files deserve a manual check. Open the activity and compare the actual traces, not just the summary tiles.

Verify:

  • Power trace is present and not flatlined
  • Heart rate trace is present where expected
  • Cadence is present if you use it in analysis
  • GPS track appears for outdoor rides
  • Elevation profile is plausible compared with the original
  • Laps and intervals survived where they matter
  • Date, start time, and ordering make sense
  • Indoor and outdoor rides were not misclassified
  • Duplicates were removed before trusting totals

The question is simple: can the new platform still explain the ride? If the answer is no, the file may be present but the training value has been degraded.

Rebuild models only after the files are clean

This is where many athletes get misled. They move the activities successfully, then expect identical fitness numbers in the new platform. That is not how modeling works.

Critical power models and performance management charts depend on input data and assumptions. Different tools can use different smoothing choices, default settings, and treatment of missing or anomalous data. The result may be close, but it may not be identical.

Handle this in order. First confirm that the raw activity data imported correctly. Then recreate the old CP, FTP, power zones, and heart rate zones if you want continuity. After that, decide whether to keep the old model settings or let the new platform establish its own baseline.

This gives you a clean analytical break. Before the migration, you know what GoldenCheetah was calculating. After the migration, you know whether changes are coming from new training, new zones, or a new model.

A practical GoldenCheetah migration sequence

The cleanest way to migrate from GoldenCheetah is not to export everything blindly and hope the new system sorts it out. Use a controlled sequence.

Prepare

Close GoldenCheetah and back up the full athlete directory. Copy original activity files from device, cloud, or download archives where they exist. Record CP, FTP, zones, athlete settings, and key chart references.

Export

Export a small representative set from GoldenCheetah using the activity export options available in your version. Test FIT if available and supported. Test TCX where compatibility or activity structure matters. Use CSV for inspection and troubleshooting.

Test

Import the sample into the destination platform. Validate ride traces, not just summaries. Confirm that power, heart rate, cadence, GPS, elevation, laps, pauses, and timestamps survive.

Migrate

Import the broader archive only after the test is clean. Prefer original files when they are complete. Use GoldenCheetah exports to fill gaps. Watch for duplicates when the same ride exists in multiple formats.

Audit

Compare calendar coverage, inspect suspect rides, remove duplicates, and document known differences between GoldenCheetah and the new platform's models.

The bottom line

A cycling data migration is successful only if the new platform can still answer the questions your old platform answered. How strong were you? How did your body respond? What changed over time? Which rides shaped the trend?

That requires more than moving files. It requires preserving original activity files where possible, exporting carefully from GoldenCheetah, documenting the assumptions, and validating the result before trusting the charts.

GoldenCheetah can hold a deep performance history. If you migrate from GoldenCheetah carefully, you can carry that history forward without letting file formats, missing sensors, duplicate rides, or model changes rewrite the story of your training.

Put this into practice

NeverChill turns the training you read about into the training you actually track - rides, power, and progress in one place.

Create free account