Apple Watch and a bike computer: keeping one clean training history
You can record a ride on both an Apple Watch and a bike computer without wanting two copies in Strava. Keep both originals if they are useful, then choose which recording should supply each destination and give it one upload path.
The choice depends on the data you want. A computer recording might have power and cadence; a Watch recording might have the heart rate you need. Inspect the actual files before choosing. Uploading both does not combine their best fields into one activity.
Choose the recording before connecting more apps
Here is a fictional setup: the computer records 07:00–08:10 with power and cadence. The Watch records 07:02–08:12 with wrist heart rate. These are illustrative sensor assignments, not a device comparison.
For cycling analysis, this rider chooses the computer’s recording because it contains the desired power data. The Watch workout stays useful in Apple Health. Each file lasts 70 minutes; treating them as separate rides could count 140 minutes of training.
| Destination | Recording to use | Path |
|---|---|---|
| Strava | Computer | Garmin Connect → Strava |
| Apple Health | Watch | Apple’s Workout app → Health |
| Private archive | Both originals | Save and label each source |
Garmin is one concrete example. A different computer needs its own companion-app connection. If the Watch file has the data you value most, choose it for Strava and stop the computer’s automatic Strava transfer instead. The Garmin Activities permission applies to Garmin activities generally, so account for other workouts you want to sync.
Set up one path to Strava
- Connect the chosen computer account. For Garmin, Strava documents Settings → Connect an App or Device → Garmin → Connect Garmin. Check the account during Garmin’s sign-in flow. The Activities permission in Garmin Connect controls automatic syncing. Garmin connection instructions.
- Stop the alternate Watch upload. In Strava, open Settings → Manage Apps and Devices → Health and turn Automatic Uploads off for this setup. Avoid manually importing the Watch copy of a ride already sent by the computer. This is an account-wide choice: Watch-only runs and walks will also need a deliberate import or another selected path.
- Check other transfer apps. If WorkoutPort also sends workouts to Strava, review the selected workouts and rules. Leave this overlapping Watch ride out of that transfer. Start with a manual review before applying a broad rule.
Strava’s native Health connection accepts workouts recorded with Apple’s Workout app within the past 30 days. Workouts written into Health by another app do not qualify for that route. That makes it unsuitable as a general bridge for older history or another recorder’s files. Apple Health and Strava documentation.
Make a separate choice for Apple Health
For the example above, turn Strava’s Send to Health off under Settings → Manage Apps and Devices → Health. Then check whether another connected app can also write Workouts to Health. Adjust that app’s workout-writing permission if you want the Watch recording to be the only workout entry. Turning Send to Health off also stops other Strava activities using that connection. Keep that consequence in mind when choosing your setup. Apple explains how to review connected apps and their Health access.
Changing one Strava setting cannot stop a separate app from writing to Health. Also, Strava documents that routes from third-party recordings, such as Garmin activities, do not sync back to Health through its connection. Check the route at the destination if you need it there.
Check the next ride before relying on the setup
After the chosen recording has synced, open the resulting activity. Check the account, start time, duration, route and important sensor streams. Confirm that the alternate recording has not arrived through another connection.
A duplicate warning is useful, but it does not tell you which recording has better data. Strava’s upload API can reject a duplicate activity; that is not a promise to merge the computer’s power and the Watch’s heart rate. Our local duplicate-check example also shows why a matching activity can still be missing a sensor stream.
If both copies have already arrived, pause the extra transfer path and save both originals before choosing which destination entry to keep. Check for notes or photos attached to just one copy. If an upload’s outcome is unclear, inspect that attempt before trying again through a different app.
If you transfer a recording by file, the FIT, GPX and TCX comparison shows how to check which fields arrived.
Connection instructions checked against the linked primary documentation on 12 October 2026. Menu labels and integration limits can change; consult those pages if your version differs.