GUIDEHow to move an Apple Health export to Garmin Connect and Strava

My Apple Watch routes exported without heart rate. How do I get both into Garmin Connect and Strava?

An Apple Health export keeps each workout in two places: the route in a GPX file with no heart rate, and the heart rate inside export.xml, a file of hundreds of megabytes. Add your export.zip: RouteMerge writes one TCX and one GPX per workout with the route and the heart rate together, right in your browser.

Apple: “You can export all of your health and fitness data from Health in XML format” (Apple Support, iPhone User Guide). In the two real exports we checked, the routes came out as GPX files without heart rate, and the heart rate was inside export.xml.

  • Nothing uploaded: location and heart rate stay on your device
  • Route and heart rate in one file per workout
  • Folders sized for Strava’s manual upload

At a glance

What RouteMerge does and doesn’t do

  • Works withThe export.zip of Apple Health, the unzipped folder, or export.xml plus the .gpx route files.
  • MakesOne TCX and one GPX per workout with route and heart rate together. A TCX with heart rate for workouts without a route. workouts.csv. Folders of 15 or 25 files for Strava.
  • Runs onAny current desktop browser: Windows, Mac, Linux. Nothing to install. The page fits a phone screen, but an export of hundreds of megabytes is a job for a computer.
  • FreeThe full list, the full workouts.csv sheet and 5 workouts converted per run.
  • Full$9 one-time. Every workout, any number of exports. No subscription.
  • PrivacyNothing is uploaded. We watched the browser’s network log during a conversion: no request carried the file.
  • Doesn’tWrite FIT files. Move steps, sleep, weight or rings. Upload anything to your account: you upload the files. Invent heart rate where the watch stored few samples.
  • Not testedThe upload to Garmin Connect and Strava: we have not done it ourselves. The files validate against the official TCX and GPX schemas.
TCX and GPX are file types listed for manual upload by
  • Garmin Connect
  • Strava
1 file

per workout, with its route and its heart rate

What the export holds
859 MB

the largest real export.xml we read, as a stream

How
5

workouts converted free per run, with the full list and the full sheet

Try it
$9

once, every workout, no subscription

Pricing

The problem

The route is in one file. The heart rate is in another.

You export your Health data to take your Apple Watch workouts to Garmin Connect or Strava. The export has everything, but not together.

Routes without heart rate

Each workout-routes/route_….gpx holds position, altitude, time and speed. There is no heart rate in it.

Heart rate inside export.xml

One Record line per sample, among every step, sleep and energy record you ever logged. In the exports we checked the file was 859 MB and 455 MB.

One workout, several routes

A workout can be split over several route files: one run in the 2020 export has four. Which files belong to which workout is written only in export.xml.

How it works

Three steps. No account, no upload.

  1. Step 1

    Export from the Health app

    On your iPhone: Health, your picture or initials, Export All Health Data. Send export.zip to your computer. Step by step

  2. Step 2

    Add export.zip

    Drop it on this page. You see every workout with its route files and heart-rate samples, and can click one to see its route. Nothing is uploaded.

  3. Step 3

    Download and upload by folder

    You get one TCX and one GPX per workout in folders of 15 or 25 files, the number Strava’s website takes per upload, plus workouts.csv.

Convert

Add your Apple Health export.zip

Everything runs on this page. Your location and heart-rate data never leave your device.

Drop your Apple Health export.zip here

Or the unzipped apple_health_export folder, or export.xml together with the .gpx route files. Nothing is uploaded.

Strava’s website takes up to 25 files at a time for subscribers and up to 15 for non subscribers (Strava Help Center). Only export.xml and the route files are read; export_cda.xml and the rest are skipped.

Free: the full list, the full workouts.csv sheet and 5 workouts converted per run. Unlock every workout for $9.

Standard files

Each workout, in the two formats upload pages ask for.

Plain XML that follows the public schemas: TrainingCenterDatabase v2 for TCX, and GPX 1.1 with the heart rate in Garmin’s gpxtpx:TrackPointExtension. The values in this example are made up; the structure is what the tool writes.

  • tcx/batch-01/2024-05-10 0655 Running.tcxTime, position, altitude, distance and heart rate per point. Each route file of the workout, and each pause, starts a new track.
  • gpx/batch-01/2024-05-10 0655 Running.gpxThe same workout as GPX 1.1, with gpxtpx:hr on each point that has a sample. Upload one or the other, not both.
  • workouts.csvEvery workout: local start, activity, active time, watch distance, route distance, route files, GPS points, points with heart rate, samples, file, and notes such as “route file not in the export”.
2024-05-10 0655 Running.gpx
<trk><name>Running 2024-05-10</name><type>running</type><trkseg>
<trkpt lat="40.781200" lon="-73.966500">
 <ele>31.2</ele>
 <time>2024-05-10T10:56:07Z</time>
 <extensions><gpxtpx:TrackPointExtension>
  <gpxtpx:hr>151</gpxtpx:hr>
 </gpxtpx:TrackPointExtension></extensions>
</trkpt>
workouts.csv
Start (local),UTC offset,Activity,Active time,Route files,GPS points,Points with heart rate,…
2024-05-10 06:55:40,-04:00,Running,0:41:12,2 of 2,2431,2398,…
2024-05-12 18:02:11,-04:00,Yoga,0:30:00,0,0,0,…

What you get

Every workout of the export, as a file you can upload.

Route and heart rate are both in your export. RouteMerge puts them in the same file, as they were recorded, and tells you what was missing.

Route and heart rate together

One TCX and one GPX per workout: GPS points with altitude, distance and heart rate, named like 2024-05-10 0655 Running.

Real heart rate only

Each point gets the sample nearest in time, at most 10 seconds away. No sample, no value: never a zero and never an estimate.

Several routes, one file

When a workout has more than one route file, they are joined in time order as segments of the same activity.

Workouts without a route too

Strength, yoga, indoor sessions: a TCX with time, heart rate, distance and calories, in their own no-route folders.

Folders sized for Strava, and a sheet

Files come in batch-01, batch-02… with 15 or 25 each, so one folder is one upload. workouts.csv lists every workout.

Stays on your device

Location and heart rate are sensitive. The export is read in your browser and nothing is sent anywhere.

What we do differently

Four things, each checked on a real export.

No promises here, only what we ran and measured on two real Apple Health exports.

WhatWhat RouteMerge doesWhat we checked
Reads the whole ZIPNot only export.xml: the route files in workout-routes/ too, and the links between themEvery route reference of both exports was found among the files: 5 of 5 and 23 of 23
Joins route and heart rateOne file per workout with bothEach point’s heart rate compared with a separate search of the nearest record in export.xml, and several checked by hand
Joins several routes of one workoutOne activity, one segment per route fileA run with four route files came out as one TCX and one GPX with its 2,675 points
Reads a very large export.xmlAs a stream, without loading it wholeA real file of 859 MB: 186 workouts and 168,910 heart-rate records found, with about 155 MB of memory in our test
Standard outputTCX v2 and GPX 1.1All 258 files written from the two exports validate against the official schemas
Data leaves your deviceNeverNo request with the file in the browser’s network log during a conversion

Pricing

Free for 5 workouts per run. $9 once for all of them.

Start free

Free

$0

The full list, the full workouts.csv sheet and 5 workouts converted per run.

Merge my workouts
  • Full list of every workout found
  • The full workouts.csv sheet
  • 5 workouts as TCX + GPX, to try an upload
  • No account

ONE-TIME

RouteMerge Full

$9 USD

one-time · every workout · any number of exports

Unlock every workout, $9
  • Every workout converted
  • Your whole history in one ZIP
  • Run it again whenever you want
  • No subscription
Secure checkout by Stripe. The full version unlocks in the browser you pay from. Questions: support@cedanolabs.org.

FAQ

Questions about moving Apple Watch workouts to Garmin Connect and Strava

Want the long version? Read the guide.

Read the guide
How do I move my Apple Watch workouts to Garmin Connect or Strava?

Export your data from the Health app on your iPhone (your picture or initials, then Export All Health Data), which gives you a file called export.zip. Add it to RouteMerge on a computer. You get one TCX and one GPX file per workout, with the GPS route and the heart rate in the same file, sorted into folders of 15 or 25 files. Then you upload those files yourself with the manual upload of Garmin Connect or Strava. RouteMerge does not connect to either account.

Why do the route files in my Apple Health export have no heart rate?

Because the export stores them apart. In the two real exports we checked, each file in the workout-routes folder holds position, altitude, time, speed and accuracy for every point, and no heart rate. The heart rate of the same workout is in export.xml, as separate records with their own timestamps. To get both in one file, each GPS point has to be matched with the heart-rate record nearest in time. That is what RouteMerge does.

Where is the heart rate in an Apple Health export?

In export.xml, inside the apple_health_export folder of export.zip. Each sample is a Record element of type HKQuantityTypeIdentifierHeartRate with a start date and a value in beats per minute. They sit among every other record of your Health data, and they are not in time order: in both exports we tested, the heart-rate records go back in time thousands of times along the file, so they have to be sorted before matching.

My export.xml is huge. Will it work?

The file is read as a stream, piece by piece, and only the heart-rate records and the workouts are kept, so it is never loaded whole. We ran the tool’s code on two real exports whose export.xml is 859 MB and 455 MB: in our test with Node 22 on a Mac the larger one was read in about a second and the process used about 155 MB of memory. In the browser (Chrome) we tested with trimmed copies of the same two exports, about 70 MB each, not with the full files, so we cannot give you a browser time for a file that size. A progress bar shows the megabytes read.

A workout has several route files. What happens?

They are joined in time order into one file, each route file as its own segment. In the 2020 export we tested, one run has four route files: it became one TCX and one GPX with all 2,675 points, in five segments (the four routes, and a pause of the workout that falls inside one of them). No distance is added across the gap between two segments.

How is heart rate matched to the route?

Each GPS point gets the heart-rate sample that is nearest in time, if that sample is at most 10 seconds away. If there is none that close, the point has no heart rate: nothing is invented, nothing is interpolated and nothing is filled with zeros.

Why do some workouts have heart rate on only a few points?

Because the export holds few samples for them. In the exports we tested, some workouts with a route have hundreds of heart-rate samples and others have one, two or three for the whole workout (15 of the 23 workouts with a route in the 2025 export): a 47-minute run from 2017 has two. With two samples, only the points within 10 seconds of them get a heart rate (42 of 2,675 in that run). The sheet shows, for every workout, how many samples were stored and how many points have one.

What about workouts without a route?

They become a TCX with the start time, the active time, the distance and the calories of the workout, and its heart-rate samples as points without position. They go in separate no-route folders and have no GPX, because a GPX point needs a position. A workout with no heart-rate samples either becomes a TCX with the totals only. We have not tested how Strava or Garmin Connect treat a TCX without positions.

Can I upload the files to Strava?

Strava's help page says: “You can upload files through the Strava website: up to 25 at a time for subscribers and up to 15 at a time for non subscribers. Strava accepts TCX, FIT, and GPX files, and each file must be 25 MB or smaller.” That is why the files come in folders of 15 or 25. Upload the TCX or the GPX of a workout, not both: they are the same activity.

Can I import them into Garmin Connect?

Garmin's help page for manual uploads says the import “Supports .fit (up to 50MB), .gpx, or .tcx (up to 25MB)” and that files must contain fewer than 99,999 data points. The sheet flags any workout over that number of points. We have not tested an import into Garmin Connect ourselves.

Has the upload to Strava or Garmin Connect been tested?

No. We have not uploaded these files to either service, and we would rather say so. What is tested: on two real exports, every TCX validates against Garmin's TrainingCenterDatabase v2 schema and every GPX against the GPX 1.1 schema, the points of each file are the points of its route files, and the heart rate of each point is the real sample nearest in time. The free version converts 5 workouts per run, so you can try an upload with your own account before paying.

Does it make FIT files?

No. It writes TCX and GPX, which are the other two file types that Strava's and Garmin's help pages list for manual upload.

Does it move steps, sleep, weight or activity rings?

No. Only workouts: their route, heart rate, time, distance and calories. Every other record in export.xml is skipped.

Which time zone are the files in?

Times inside TCX and GPX are UTC, which is what both formats expect. File names and the sheet use the local time of each workout, taken from the time zone the export stores with it. Some workouts have none (13 of 186 in the 2020 export we tested, 10 of 47 in the 2025 one); those are named with the UTC offset written in export.xml, which is the offset the phone had when the export was made, so a summer workout exported in winter can be named one hour off. The sheet marks them.

Which activity types are kept?

A TCX file can only say Running, Biking or Other. Runs become Running, rides become Biking, and everything else (walks, hikes, strength, yoga) becomes Other; you can change the type after uploading. The original activity name is in the file name, in the TCX notes and in the sheet.

What happens with altitude?

It is copied from the route file. Where the route file marks the altitude of a point as not valid (a negative vertical accuracy, written with an altitude of 0), the point is written without altitude instead of at sea level. In one walk of our test exports that was 767 of 1,328 points.

What if a route file is missing?

If export.xml links a workout to a route file that is not in what you added, the workout is still converted with what there is, and the sheet says “route file not in the export” with the name of the file. Add the whole export.zip rather than export.xml alone and this does not happen.

Are my files uploaded anywhere?

No. The export is read by JavaScript on this page, on your device, and the ZIP is built there too. There is no upload step and no account. We checked the browser's network log during a conversion: no request carried the file. 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.

Does it work on a phone?

The page fits a phone screen, but we have not run a conversion on a phone, and an export of hundreds of megabytes is a job for a computer. Send export.zip to a Windows, Mac or Linux computer and use a current browser there.

How does the $9 full version work?

Free gives you the full list, the full workouts.csv sheet and 5 workouts converted per run: the first five by date that have a route. The full version is a single $9 payment, with no subscription and no account, and converts every workout, for any number of exports. It unlocks in the browser you pay from.

Is this an Apple, Garmin or Strava product?

No. RouteMerge is an independent tool by Cedano Labs LLC. Not affiliated with Apple, Garmin or Strava.

Take your workouts with you, heart rate included.

Add your Apple Health export.zip, check the workouts found, and download a TCX and a GPX for each. Free: the full list, the full workouts.csv sheet and 5 workouts converted per run.