How To Import Strava Activity To Garmin | Clean Sync Without Headaches

You can move Strava workouts into Garmin by exporting a GPX/FIT file, then importing it to Garmin Connect so the session lands in your activity list.

If you track on Strava but want your training log inside Garmin Connect, you’re not stuck. You can get the activity across with a clean file export and a manual import, then tidy up the bits that often get messy: time zones, duplicates, missing heart rate, and odd splits.

This walk-through keeps it practical. You’ll learn which file type to grab, where the import button hides, what data will and won’t carry over, and how to avoid creating a double entry that wrecks weekly totals.

What You Need Before You Start

Get these basics lined up first. It saves rework.

• Access to the activity on Strava (web is easiest for exporting).
• A Garmin Connect account that you can sign into on a computer browser.
• The right file type for the data you care about (more on that next).
• A quick plan for duplicates if the same workout already exists on Garmin.

If your workout came from a Garmin watch in the first place, importing it back into Garmin can create a copy. In that case, the cleaner move is to fix the original sync path, not re-import the same session.

Pick The Right Export File Type

Strava exports can come out as GPX or TCX, and some activities also allow an “original” file download. The best choice depends on what you want to preserve when the workout lands in Garmin Connect.

GPX Works For Maps And Basic Stats

GPX is a safe pick when you mainly want the route and basic timing. It carries GPS points and can rebuild distance and elevation in Garmin Connect, yet it can drop richer sensor data.

TCX Can Keep More Structure

TCX often includes laps, cadence, and some extra fields beyond a plain GPX. If your session has structured splits that matter, TCX may import with fewer surprises.

Original FIT Is Best When Available

If Strava offers the original upload file and it’s a FIT, that’s usually the closest match to what devices record. FIT tends to hold more metrics (power, heart rate, cadence) in a way Garmin understands.

How To Import Strava Activity To Garmin On Any Device

This is the core workflow: export from Strava, then import into Garmin Connect. Do it once, then set a repeatable habit so you don’t waste time each week.

Step 1: Export The Activity From Strava

1. Open Strava on a computer browser and go to the activity page.
2. Open the action menu (often shown as three dots).
3. Choose an export option such as GPX or TCX.
4. Save the file somewhere you can find fast (Downloads is fine).

Strava documents the export options and what each format contains on its help page for Exporting your data and bulk export. Use that page if your menu labels look different, since Strava tweaks UI names from time to time.

Step 2: Import The File Into Garmin Connect

1. Sign in to Garmin Connect on a computer browser.
2. Find the manual upload or import option for activities.
3. Select the file you exported from Strava (FIT, GPX, or TCX).
4. Wait for the upload to finish, then open the imported activity to check the details.

Garmin lists supported file types and file limits in its support article on How do I manually upload an activity I recorded to Garmin Connect?. If your upload fails, this page is also where Garmin spells out size caps and common constraints.

Step 3: Verify The Imported Activity Before You Move On

Open the activity in Garmin Connect and check these items right away:

• Date and start time match what you expect (time zone issues show up here).
• Distance looks reasonable compared to Strava.
• Map loads and isn’t missing chunks.
• Heart rate and power appear if they were recorded.
• Sport type is correct (run, ride, walk, indoor).

If any of those look off, fix it now while the file is fresh in your mind. Once you import a batch of workouts, spotting the bad one gets harder.

Common Outcomes And What Data Carries Over

Not every field survives the trip from Strava to Garmin Connect. The format you export sets the ceiling on what can come through, and the platform import rules also shape what gets saved.

Use this table as a quick expectation check. It’s not a promise of identical results for every device, since recording sources vary.

Data Item	Usually Transfers When	What To Watch For
Route map	GPX, TCX, or FIT includes GPS points	Indoor sessions may import with no map
Elapsed time	All formats	Time zone shift can change the calendar date
Moving time	FIT or TCX with motion data	Some imports show elapsed only
Heart rate	Original FIT or TCX that contains HR stream	GPX export can arrive without HR
Power	Original FIT that contains power	Estimated power on Strava may not exist in the export
Cadence	FIT or TCX with cadence	May appear as blank if the sensor was not paired
Splits / laps	TCX or FIT contains lap markers	Auto-laps can rebuild differently after import
Calories	FIT often carries it; platforms can recalc	Totals can differ if Garmin recalculates from profile
Elevation gain	All formats, recalculated from points	Barometer vs map-based gain can differ

Fix The Four Issues That Trip People Up

Most imports “work,” then feel wrong once you compare totals. These are the four snags that cause the most confusion, plus how to straighten them out.

Duplicate Activities

If the workout already exists in Garmin Connect, importing the Strava file creates a second entry. Your weekly distance doubles and your training load charts can swing.

• If Garmin already has the workout from a device sync, keep the Garmin original and skip the import.
• If the Garmin original is missing chunks and the Strava file looks cleaner, keep the imported version and delete the broken one in Garmin Connect.

Time Zone Drift

When an activity imports with the wrong date or time, it’s usually a timestamp and time zone mismatch in the file metadata. If your workout lands on the wrong day, your streaks and weekly summaries can break.

• Check your Strava profile time zone and your Garmin Connect profile time zone match your current setting.
• Re-export as a different format (TCX vs GPX) if one format imports with a shift.
• If you travel often, confirm the activity’s local time in Strava before exporting.

Missing Heart Rate Or Power

This one usually comes down to the export format. A GPX focused on GPS points may not carry sensor streams the way a FIT does. If your goal is to preserve heart rate zones or power curves, try to download the original file when Strava allows it.

If the original file isn’t available, TCX can be the next best shot. After import, open the charts view in Garmin Connect and confirm heart rate and power show up before you file it away.

Sport Type And Indoor Sessions

Indoor sessions can import with limited context. A treadmill run might show distance as zero if the file lacks that field. Strength sessions can land as “Other” if the export is thin.

• Edit the activity type in Garmin Connect after import so your stats don’t mix sports.
• If an indoor session has no distance by design, accept it and use duration-based views for progress.
• If you rely on Garmin training status, keep in mind that some imported workouts may not count the same way as device-recorded ones.

Batch Imports Without Losing Your Mind

If you have months of Strava history you want inside Garmin Connect, importing one by one can feel like a slog. The trick is to batch the work, keep a clean file folder, and run checks at set points so you don’t import junk for an hour and notice after the fact.

Set Up A Simple Folder System

Create one folder on your computer, then split by sport or month. Keep file names readable. A pattern like YYYY-MM-DD_Run or YYYY-MM-DD_Ride makes it easy to spot missing days.

Import In Small Sets

Try 10 to 20 files per session. After each set, scan your Garmin Connect activity list for the date range you just imported. You’re looking for blank maps, weird durations, or a sudden spike from duplicates.

Stop And Correct Patterns Early

If you notice that GPX imports always lose heart rate for you, switch to TCX or original files right then. Don’t keep importing a format that drops the data you care about.

Troubleshooting When Garmin Connect Rejects The File

Garmin Connect can refuse a file for reasons that feel random until you know what it checks. Use this table as a fast diagnostic list before you burn time re-exporting the same workout again and again.

What You See	Likely Cause	What To Try Next
Upload fails right away	Unsupported format or oversized file	Export a different format or choose the original file if it’s smaller
Upload completes, no activity appears	File lacks an “activity” section Garmin expects	Try TCX or original FIT; avoid stripped GPX from non-GPS sessions
Activity appears with no map	No GPS track in the file	Confirm the session recorded GPS; export from the activity page again
Wrong distance	Gaps in GPS points or recalculation differences	Try original FIT; check that the export is from the correct activity
Wrong date	Timestamp or time zone mismatch	Check profile time zone settings, then re-export in another format
Heart rate missing	Export format lacks HR stream	Use original file when present; try TCX next
Power missing	Power not recorded in source file	Confirm your sensor data exists in Strava charts; use original FIT if present

Make The Result Look Clean Inside Garmin Connect

After import, a minute of cleanup makes your Garmin log feel like it belongs there. This is where you protect your stats from weird labels and missing context.

Edit The Title And Sport Type

Rename the activity with a short label that helps later, like “Hill repeats” or “Long easy ride.” Also set the sport type correctly so your personal records and trends stay accurate.

Add Notes You’ll Use Later

If you track gear wear, training blocks, or route notes, add them now. Garmin Connect notes can help you recall why a session felt tough when you review a month later.

Check Privacy Settings

Imported activities follow your Garmin Connect sharing settings. If you keep your training private, confirm the visibility matches your preference before you move on.

When Manual Import Is The Wrong Fix

Manual import is great for one-off transfers and backfilling history. It’s not the best answer for every scenario.

• You record with a Garmin device already: keep Garmin as the source of truth and let it sync out, not back in.
• You need training status and load metrics to behave the same: device-recorded sessions often integrate more cleanly than imported files.
• You change devices often: pick one platform as the master log and use exports only when you switch ecosystems.

If your main goal is “all workouts in one place,” importing select sessions that matter most can be a better use of time than trying to mirror every single entry.

A Simple Repeatable Routine For Future Workouts

Once you’ve done this a couple times, the routine can be simple:

1. Export the activity from Strava in the richest format you can get.
2. Import it into Garmin Connect the same day, while details are fresh.
3. Scan the map, time, and sensor charts.
4. Fix sport type and title, then move on.

That’s it. No mystery steps. Just a clean file in and a quick check that saves you from a broken training log later.