GUIDEHow to move adidas Running history to Strava

Your adidas Running years, as files Strava accepts.

The adidas Running (Runtastic) export is a ZIP with thousands of JSON files, and Strava cannot import it. RunTidy reads that ZIP and writes one GPX or TCX file per session, with the route, heart rate and original date, sorted into folders ready for Strava’s upload page. Right in your browser.

  • Nothing uploaded, ever
  • No adidas or Strava login
  • Every sport, not only running

At a glance

What RunTidy does and doesn’t do

  • Works withThe adidas Running / Runtastic data export ZIP (export-YYYYMMDD-000.zip), or the folder you unzipped it into.
  • ConvertsEvery session to one file: GPX with the GPS route, time, elevation and heart rate; TCX for sessions with no GPS. Plus a sessions.csv list of everything.
  • Runs onAny current browser on Windows, Mac, Linux, Chromebook or Android. Nothing to install.
  • Free5 sessions per run, with the full preview. Full: $9 one-time, every session.
  • PrivacyNothing is uploaded. No adidas login and no Strava login.
  • Doesn’tUpload to Strava for you or ask for your Strava account: you upload the files yourself. Sessions recorded without GPS do not gain a map.
Each file carries, where the export has it
  • GPS route
  • Date & time
  • Elevation
  • Heart rate
  • Sport
  • Notes
1 file

per session, named by date and sport

See the names
0 bytes

of your runs sent to any server

How it works
5

sessions converted free, with the full list of your export

Try it
$9

once, every session, no subscription

Pricing

The problem

You exported your runs. Strava won’t take the export.

adidas Running gives you all your data, and that part works. What arrives is not something another app can read.

Thousands of JSON files

Each session is a small JSON file named with a date and an id. Strava’s upload page accepts GPX, TCX and FIT files, not these.

One run, up to four files

The sport, time and totals are in one file. The route is in GPS-data, the pulse in Heart-rate-data, the altitude in Elevation-data. They have to be joined.

No official way in

Strava’s help says there is currently no official way to move your activity history from Runtastic to Strava. The open-source converters run from a command line.

How it works

Three steps. No unzipping, no command line.

  1. Step 1

    Export your data from adidas Running

    On runtastic.com: Account & Data → Export Data. adidas emails you a link to a ZIP named like export-20261121-000.zip. Step-by-step guide

  2. Step 2

    Open the ZIP here

    RunTidy lists every session it finds: date, sport, duration, distance, GPS or not, heart rate or not. Filter by sport and year to check that your history is all there.

  3. Step 3

    Download and upload in batches

    One new ZIP with folders batch-01, batch-02… On Strava: + → Upload activity → File, select one folder’s files, repeat. How to upload

Convert

Open your adidas Running export

Everything runs on this page. Your location and health history never leave your device.

Drop your export .zip here

The ZIP from adidas Running, as downloaded, or the folder you unzipped. Nothing is uploaded.

Free: 5 most recent sessions and the full list. Convert every session for $9.

Standard formats

Plain GPX 1.1 and TCX. Nothing proprietary.

The two open formats that sports watches and training sites exchange, and two of the three that Strava’s upload page accepts. In our tests the GPX output is validated against the official GPX 1.1 schema.

  • GPX for sessions with a routeOne track, with latitude, longitude, elevation and UTC time on every point, and the sport in <type>.
  • Heart rate matched by timeEach GPS point gets the closest heart-rate sample (within 10 seconds), in gpxtpx:hr, the field Strava documents for heart rate.
  • TCX for sessions without GPSStart time, duration, distance, calories, average and maximum heart rate. Treadmill and gym sessions keep their numbers.
batch-01/2019-05-14_0732_running.gpx
<trk><name>Running 2019-05-14 07:32</name><type>running</type>
<trkpt lat="48.20817" lon="16.37382">
  <ele>171</ele>
  <time>2019-05-14T05:32:07.000Z</time>
  <extensions><gpxtpx:TrackPointExtension>
    <gpxtpx:hr>148</gpxtpx:hr>
  </gpxtpx:TrackPointExtension></extensions>
</trkpt>
sessions.csv
Date (local), Sport, Duration, Distance (km), File, Status
2019-05-14 07:32, Running, 0:52:10, 10.02, batch-01/2019-05-14_0732_running.gpx, converted to GPX
2019-05-16 18:05, Cycling, 1:31:44, 38.60, batch-01/2019-05-16_1805_cycling.gpx, converted to GPX
2019-05-19 09:10, Treadmill, 0:30:00, 5.00, batch-01/2019-05-19_0910_treadmill.tcx, converted to TCX

What you get back

One file per activity, and a list to check that nothing is missing.

RunTidy reads the original ZIP directly and joins the several JSON files of each session. What the export recorded is kept; what it never recorded is not invented.

Routes, dates and pace

Every GPS point keeps its position, elevation and exact time, so distance and pace come out of the track the way you ran it.

Heart rate where it exists

Samples from Heart-rate-data are matched to the GPS points by time. Sessions without a sensor simply have none.

All sports, not only running

Cycling, hiking, walking, swimming, skiing, yoga, strength… The sport goes into the file and into its name.

A manifest you can read

sessions.csv lists every session of the export: date, sport, duration, distance, notes, the file it became, or why it was not converted.

Folders sized for Strava

Files come in batch-01, batch-02… with 25 files each (or 15), the amounts Strava’s upload page takes at a time.

Local, and no account access

The export is read in this browser tab only. You upload the files to Strava by hand, so nobody gets access to your Strava account.

Compared

Other ways to convert the export.

There are good free, open-source converters. They are scripts: you install a runtime and work in a terminal. Details below are from each project’s own README, checked on November 21, 2026.

FeatureRunTidyfcrespel/runtastic-export-converterGiacomoGarbin/runtastic-gpx-converternonstoptimm/run-history-migratorGriffsano/RuntasticConverterThe .gpx files already in the export
CostFree for 5 sessions, $9 once for allFree, open sourceFree, open sourceFree, open sourceFree, open sourceFree
What you installNothingJava (OpenJDK); command line. The repository is archived (read-only)Python; command linePython; command linePython; command lineNothing
InputThe export ZIP as downloaded, or the unzipped folderThe unzipped export folderThe export ZIPThe unzipped export folderThe unzipped export folder—
OutputGPX (with route) and TCX (without), one per session, in folders of 25GPX or TCXA ZIP of GPX filesTCX files and a manifest; optional upload through Strava’s APIRenamed GPX files and statistics, for import into the self-hosted workout-tracker appGPX, named with the session id
SportsAll, written into each fileAll; a few types mappedEvery track written as runningRunning onlyAllAll, in adidas’s own words
Sessions without GPSConverted to TCXNot checkedNot checkedSkippedAdded as manual workouts in workout-trackerNo file
Files leave your deviceNeverNeverNeverOnly if you use its Strava API uploadNever—

“Not checked” means we did not verify that point. About the last column: the export already has a .gpx file for sessions with a GPS trace. We have not tested uploading those to Strava, and Strava’s help says the export’s files are not formatted for direct upload.

Pricing

Free for 5 sessions. $9 once for all of them.

Start free

Free

$0

Convert your 5 most recent sessions and see the full list of everything in your export.

Convert my runs
  • Preview table of every session, with filters
  • 5 most recent sessions as GPX or TCX
  • sessions.csv with every session
  • No account

ONE-TIME

RunTidy Full

$9 USD

one-time · every session · any number of exports

Convert every session, $9
  • Every session in the export
  • Batch folders of 25 or 15 files
  • Run it again on future exports
  • No subscription
Secure checkout by Stripe. The full version unlocks in the browser you pay from. Questions: support@cedanolabs.org.

FAQ

Questions about moving adidas Running to Strava

Want the long version? Read the guide.

Read the guide
Can Strava import an adidas Running (Runtastic) export directly?

No. Strava's help page "Runtastic and Strava" says there is currently no official way to move your activity history from Runtastic to Strava, and that the files of the export are not formatted for direct upload. Strava does accept GPX, TCX and FIT files through its upload page. RunTidy turns the export into GPX and TCX files, and you upload them yourself.

What does RunTidy read from the export?

The Sport-sessions folder. Each session has one JSON file (sport, start time, time zone, duration, distance, calories, average and maximum heart rate, notes) and up to three companion files with the same name: GPS-data (the route, as JSON and often also GPX), Heart-rate-data and Elevation-data. RunTidy joins them by the session id at the end of the file name. Photos, shoes, sleep and the other folders are not read.

Which sessions become GPX and which become TCX?

A session with a GPS route (at least two GPS points and a distance) becomes a GPX 1.1 file: one track with latitude, longitude, elevation and time on every point, heart rate where it was recorded, and the sport in the type field. A session with no route, such as a treadmill run, a workout typed in by hand, strength training or yoga, becomes a TCX file with the start time, duration, distance, calories, average and maximum heart rate, and the heart-rate samples if there are any. TCX files from RunTidy have no map, because there is no route to draw.

Does heart rate carry over?

Yes, when the export has it. For each GPS point RunTidy takes the heart-rate sample closest in time from the session's Heart-rate-data file, if one is within 10 seconds, and writes it in the Garmin TrackPointExtension field (gpxtpx:hr), which Strava's upload documentation lists as heart rate. Sessions recorded without a heart-rate sensor have no heart rate, and RunTidy does not make one up.

Will Strava file each activity under the right sport?

RunTidy writes the sport into each file: the type field in GPX, the Sport attribute in TCX. Strava documents sport detection from files for running, biking, hiking, walking and swimming in TCX; it does not document how it reads the sport from GPX. So check the first batch after uploading: you can change the sport of an activity on Strava. For any other sport (yoga, strength training, skiing and so on) the sport name is in the file name, the activity title and sessions.csv.

Why are the files split into batch folders?

Strava's bulk upload takes a limited number of files at a time. Its help page says subscribers can upload up to 25 files at a time and other accounts 15, and that each file must be 25 MB or smaller. RunTidy puts the files into folders named batch-01, batch-02 and so on, with 25 files each, or 15 if you choose that. You select one whole folder per upload.

Is my export uploaded anywhere?

No. The ZIP is read and the new ZIP is built by JavaScript on this page, on your device. There is no upload step. The only network requests are for the page itself, cookieless page analytics, and the payment check if you buy the full version, which sends a payment ID and never a file. This matters here: the export holds years of your location and health history.

Do I have to give RunTidy access to my Strava or adidas account?

No. RunTidy never asks for a login, a password or an API authorization. You download the export from adidas Running yourself and you upload the converted files to Strava yourself, through Strava's own upload page.

Does it work with old Runtastic exports?

It reads both layouts that we have seen in real exports: the older one, with distance and pulse at the top of the session file and timestamps written as text, and the current one, with those values inside a "features" list and timestamps in milliseconds. It was tested on real sessions recorded between 2011 and 2023. adidas can change the format at any time, so sessions.csv tells you, session by session, what was converted and what was not.

Are the dates and times kept?

Yes. Every GPS point keeps its exact moment, written in UTC as the GPX and TCX formats require. File names and sessions.csv use the local time of each session, from the time zone offset adidas Running stored with it, so a run you started at 7:32 in the morning is named 0732 wherever you run the tool.

How many sessions can it handle at once?

The whole export in one run. Session files are read one at a time and the new ZIP is compressed, so thousands of sessions are fine on a normal computer. The technical ceiling of the output is 65,535 files and 4 GB.

Does it upload the files to Strava for me?

No. RunTidy stops at the files. Uploading is done by you on Strava's upload page, one batch folder at a time. That is on purpose: it means RunTidy never needs access to your Strava account.

How does the $9 full version work?

The free version converts your 5 most recent sessions per run, and the preview table and sessions.csv list every session in the export, so you can see what you would get. The full version is a single $9 payment, with no subscription and no account, and converts every session, in any number of exports. It unlocks in the browser you pay from.

Take your running history with you.

Open the export ZIP from adidas Running and get every session back as a file Strava accepts. The first 5 are free.