Beyond Garmin Connect
How to Export Your Suunto Data — and What It Leaves Out
August 1, 2026
What Suunto actually lets you export
Two formats, one workout at a time: FIT and GPX. Suunto's own support documentation lists nothing else — no TCX, no KML, no CSV per workout — and it documents no self-service way to download your whole history from inside the app.
That is the honest headline, and it is narrower than most guides on the internet will tell you. Everything below is traced to a Suunto page I read and linked. Where the only evidence I could find was a user report on Suunto's community forum rather than official documentation, I say so instead of dressing it up as a step.
| Route | Gets you | Format | Documented by Suunto? |
|---|---|---|---|
| Three-dot menu on a workout | One workout | FIT or GPX | Yes |
| Partner services sync | New workouts, ongoing | Platform-native | Yes |
| Request to Suunto customer support | Your account data | JSON, NDJSON, GPX, FIT, CSV | Yes (EU Data Act notice) |
| In-app "Export data" under account settings | Zip of your history | FIT, GPX, JSON | No — user reports only |
Exporting a single workout
This is the one route Suunto documents clearly, and it works the same way on both platforms.
Open the workout in the Suunto app, tap the three dots in the top right corner, choose your format, then save the file to your device or open it directly in another app. That is the whole flow, quoted almost verbatim from Suunto's export FAQ.
Android has its own support article with a slightly more explicit path: go to your Calendar (the second icon on the lower bar), select the training you want, press the three-dot menu in the upper right, and choose the FIT download. Suunto notes you may need to grant the app access to photos, media and files first, after which the download starts automatically.
FIT or GPX
Suunto describes three things you can produce:
FIT contains "all the relevant information from your workout: location, time, timestamps, heart rate, power, cadence, etc." This is the one to take. Anything you can do with GPX you can also do after the fact with a FIT file, and the reverse is not true.
GPX (workout) carries location and time, plus heart rate where it exists. Useful when a receiving platform refuses FIT.
GPX (route) is location only: a line on a map for navigation, not a training record.
One limit worth knowing before you plan a migration: recordings without GPS, which includes most indoor and strength sessions, can only be exported as FIT. There is no GPX to produce when there was never a track.
If you want to do anything serious with the files afterwards, the FIT parsing libraries and desktop tools in our roundup of Garmin data analysis tools are format-agnostic. A Suunto FIT file and a Garmin FIT file both open in python-fitparse and GoldenCheetah.
Is there a bulk export?
Officially: not one you can trigger yourself.
Suunto's EU Data Act notice is the most concrete page the company publishes on this. It says you can retrieve your product and related-service data — including raw sensor measurements and pre-processed data — through the Suunto app, through Sports Tracker, or by submitting a request to Suunto Customer Support. It names the formats: JSON, NDJSON, GPX, FIT and CSV. It also states that data is retained up to 10 years or until account deletion.
The Suunto privacy policy covers the GDPR side: a right of access, a right to a copy in a structured, commonly used, machine-readable format, and a right to have it transmitted elsewhere. Requests go in writing or by email to Suunto Oy, with privacy@suunto.com as the published address. Neither page commits to a response deadline, and multiple threads on Suunto's own forum describe waits of weeks.
So the documented bulk route is: email them and wait.
There is a second route that users on Suunto's community forum describe repeatedly, most recently in January 2026: an in-app export under account settings that mails you a zip of FIT, GPX and JSON files. I could not find it in any Suunto support article, so I am not going to write it as a step list.
Here is the opinion, and I will stand behind it: an export path that exists only in forum posts is not a feature. Garmin's bulk export is slow and clunky, but it is written down, in the same place every time, and you can point a nervous user at the page. Suunto's is folklore. For a company whose legal pages correctly describe your right to portable data, leaving the mechanism undocumented is a choice, and it is the wrong one.
The Movescount lesson
Suunto used to run Movescount. It is gone. Per Suunto's own transition page, watch customisation was pulled on 30 November 2021 and "after January 10th, Movescount will be closed." I tried movescount.com while writing this on 1 August 2026: the domain still resolves, and the server does not answer.
Two things follow from that, and only one of them is Suunto's fault.
The first is not: platforms retire. Movescount got a phased wind-down, a one-way import tool into the Suunto app, and years of warning. That is a more careful shutdown than most services manage, and Suunto deserves the credit.
The second is a live problem. Suunto's support site still hosts a page titled "How do I transfer my Move history from Suunto Movescount to Suunto app?" which reads, in the present tense, "the service is now enabled for all Suunto users to import their Movescount history." It carries no date and no closure notice. Third-party documentation inherited the same rot: Runalyze's Suunto help article still tells you to create a data export at movescount.com/settings#export, a URL that has not answered a request in years.
If you kept a Movescount account and never ran the migration, that history is not sitting somewhere waiting for you. Assume it is gone, then be pleasantly surprised if support finds something. And take the general lesson: the archive you control is the only archive with a guaranteed uptime. That argument applies with more force the longer your history runs, which is why it matters most to the people doing multi-year ultra buildups where a decade of data is the whole point.
Third-party sync, and which direction it flows
Suunto documents partner connections under Suunto App → Profile → Partner services. What actually moves depends on the partner, and the sync direction is where most people get surprised.
Strava is one-way for activities, and it does not backfill. Strava's own help page says the integration sends workouts to Strava after they sync to the Suunto app, and that historical activities do not come across — you export FIT or GPX files from the three-dot menu and upload them on the Strava website by hand. Routes flow the other way, from Strava to the watch, but that is navigation data, not training history.
TrainingPeaks is two-way, and Suunto's own documentation disagrees with itself about this. The TrainingPeaks partner page states flatly that training plans created in TrainingPeaks are not synchronised to Suunto watches. The newer SuuntoPlus Guides FAQ says structured workouts and plans do flow from TrainingPeaks to the watch as guides. The Guides route is the current one; the partner page is stale. The same FAQ page notes TrainingPeaks does not capture every Suunto metric, naming swimming strokes and recovery time.
Intervals.icu is listed by Suunto as a SuuntoPlus Guides partner for planning and real-time guidance, and its own announcement thread documents uploading planned workouts to Suunto watches with power, heart rate, pace and cadence targets. Activity download from Suunto is described as live in intervals.icu's forum rather than in a support article.
Runalyze documents a direct Suunto app connection under Automatic Sync, and answers "can I synchronise my entire activity history" with yes, via a tool on its synchronisation page. That makes it the most promising backfill route I found that does not involve emailing anyone, though I have not run it.
What is not in the export
This is the part worth reading twice, and it is the same shape of gap that makes Garmin Connect's own limitations frustrating.
Daily and wellness data. Suunto's export documentation is scoped entirely to workouts. Sleep, body resources, daily heart rate and steps are prominent features of the watch and the app — Suunto documents sleep tracking and body resources in detail — and none of it has a documented per-item export. It appears in the customer-support request route, not in the three-dot menu.
Derived metrics and their history. Recovery percentage, training load balance, fitness estimates. A FIT file records what the sensors saw; it does not carry the platform's interpretation of it over time. Suunto's TrainingPeaks documentation admits as much when it says recovery time does not carry across.
That history is often the most valuable thing you own, and it is the thing that never survives a migration. In our own study of estimated VO2max on 42 Garmin accounts with at least 180 days of data, the metric moved across a median range of 9.9 points over each athlete's full history, and the median year-over-year change was 2.0 points. Cohort caveat: these are self-selected Garmin users who connected a training-analytics service, so likely fitter and more data-curious than average. The number is not Suunto's, and I am not claiming it transfers. The structural point does: a several-point trend line built over years is a real signal, it lives in the platform rather than the file, and no export format has a field for it. That is a large part of why your watch data is worth more than it looks.
Suunto and Garmin, side by side
Neither company comes out of this clean.
Garmin gives you more formats per activity — FIT, TCX, GPX and KML, though no CSV — and a documented full-account archive you can request yourself, which is the whole subject of our Garmin export guide. Suunto gives you FIT and GPX, and routes the full archive through a support request.
Where they converge is the interesting part. Garmin's bulk archive also omits training status history and gives you summarised rather than granular physiological trends. Both companies will hand over the sensor data and keep the interpretation. The difference between them is one of documentation quality, not philosophy.
If the reason you are exporting is that the app is not telling you anything useful about your own training, a file is not the fix. That is the case for the platforms built on top of this data, and for calculators like our race pace predictor that work from times you already know rather than from a metric a vendor owns.
Frequently asked questions
Can I export a Suunto workout as TCX?
Not from the Suunto app. Suunto documents FIT and GPX only. If a platform demands TCX, convert a FIT file locally with a third-party tool.
Does connecting Strava import my old Suunto workouts?
No. Strava states the connection does not sync historical activities. You export them as FIT or GPX and upload them on the Strava website individually.
Can I still get my Movescount data?
Movescount closed after 10 January 2022 and the site no longer responds. If you did not migrate before then, treat the data as gone and raise it with Suunto customer support as a data-access request rather than a recovery ticket.
How long does a Suunto data request take?
Suunto publishes no target. Its privacy policy grants the right of access without a stated deadline, and forum reports describe waits measured in weeks.
Does the Suunto export include sleep and recovery?
Not through the per-workout export, which covers workouts only. Suunto's EU Data Act notice does list broader product and service data as available through customer support, in JSON, NDJSON, GPX, FIT or CSV.
If you own a Suunto watch and have never pulled a file out of it, do one thing this week: export your single most important session as FIT and put it somewhere you control. Not because Suunto is going anywhere — because Movescount taught everyone who used it that the question is never whether a platform is trustworthy today.
Sources: Suunto export FAQ · Android FIT download · EU Data Act notice · Privacy policy · Digital service transition · Suunto digital services timeline · Strava help: Suunto app and Strava
