Polar Flow to Strava sync: what it carries, and what it quietly drops

How the connection actually works

It runs in one direction, Flow to Strava, and it fires when Flow itself syncs rather than on a schedule of its own. You connect it from Flow's Settings under the Partners tab, click Connect beside Strava, and authorize through a Strava login [Polar Strava Sync]. From then on sessions are synced to Strava when you sync them to Polar Flow.

That coupling matters more than it looks. The trigger is your Flow sync, not a background job at Strava's end, so a ride sitting on a watch you have not synced is not late — it has not been handed over yet. Riders who leave the watch un-synced for a few days and then wonder why Strava is behind are seeing the design rather than a fault.

It is also worth being precise about the direction, because the reverse assumption causes real confusion. Nothing travels from Strava back into Polar Flow. A ride recorded on a different head unit and uploaded to Strava will never appear in your Flow diary, and no Strava data feeds Polar's Training Load Pro or its zone calculations. Flow's picture of your training is built only from what Polar recorded.

For anything the automatic sync refuses, Polar's answer is manual: those sessions can be transferred to Strava with Polar Flow's export function [Polar Strava Sync]. That works, and it is a per-session chore rather than a backfill, which is why almost nobody does it for more than a handful of rides.

The four things that never arrive

Polar lists the exclusions plainly. Previously recorded sessions require manual export rather than syncing automatically, manually added training sessions do not sync, sessions without sample data do not sync, and sessions synced from Polar group solutions or third-party applications do not sync [Polar Strava Sync].

The pre-link exclusion is the one that costs most. Connecting Flow to Strava does not backfill your history — the connection starts working from the moment you make it, and everything before it stays in Flow unless you export it by hand. A rider with three years of Polar riding who links Strava today has a Strava account that starts today. If both accounts matter to you, link them on day one rather than when you first need the data somewhere else.

The sample-data rule is more specific than it sounds and is the one that catches indoor riders. To sync, a session has to contain sample data needed to draw curves, from GPS, heart rate, altitude, cadence or power [Polar Strava Sync]. Any one of those is enough, so a trainer session with a heart-rate strap qualifies. A session with a duration and nothing else does not, which is exactly the shape of a ride logged from memory.

That connects directly to the third exclusion, because a manually added session is usually a session with no samples. If you add a ride to your Flow diary by typing in the time and the sport, Strava will not receive it. The same applies to anything that arrived in Flow from a Polar group product or another service rather than from your own device.

The fourth item is not an exclusion so much as a silent omission: calorie data is not transferred from Polar Flow to Strava, although Strava calculates its own figure for cycling and running [Polar Strava Sync]. So the number is not missing on Strava, it is simply a different number, computed by a different model from a different input. Comparing the two is meaningless, and neither should be treated as a measurement.

Which one should a training app read?

Both, if you can, and for different reasons. Strava holds your archive and can be bulk-exported [Strava Data Export]. Polar holds the live feed and the sensor detail. The relevant asymmetry is that Polar's public API hands over no history at all when you first connect it [Polar AccessLink API].

That last point is worth stating exactly, because it is the mirror image of the Strava exclusion above. Polar's API returns only exercises uploaded to Flow in the last 30 days, and only those uploaded after your account was registered with the connecting client [Polar AccessLink API]. Both conditions apply together. At the moment you connect, nothing satisfies them, so a Polar-only connection starts from zero and fills forward. The 30 days is how long the live feed keeps a ride available, not a window into the past.

So the two platforms fail in opposite directions and the fix is the same in both cases: connect early. A rider who links Strava to Flow on day one has an archive that any training service can read. A rider who connects Polar to a training service today gets an excellent feed of everything from today, and should connect Strava alongside it if their history matters.

There is a real cost to reading only one of them, and it is not tidiness. Whether a training year works is largely decided by whether the easy rides stayed easy and the hard ones stayed hard [Seiler 2010], and that is an audit you can only run over a complete record. A ledger missing every pre-link ride, every manually logged session and every sample-less trainer effort will systematically under-count the easy end, because those are exactly the sessions people log by hand.

Polar's own metrics inherit the same problem from the other side. Cardio Load is calculated from heart rate and session duration [Polar Training Load Pro], so it scores only what the watch recorded with a strap. Training with a Polar means holding two partial records in your head unless something reconciles them. That reconciliation is the job we take on: we read the rides, deduplicate what arrives twice, and build the plan from the merged picture rather than from whichever feed happened to be complete.

Quick answers

Sources cited in this guide

1. 01
   Polar Strava Sync. How can I automatically sync my data from Polar Flow to Strava?. Polar Support.
2. 02
   Polar AccessLink API. Polar AccessLink API. Polar Developers.
3. 03
   Polar Training Load Pro. Training Load Pro. Polar Support.
4. 04
   Strava Data Export. Exporting your Data and Bulk Export. Strava Support.
5. 05
   Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.

More inside Training with a Polar

Other articles in this series

1. 01

   Does Polar have a cycling training plan?

   Polar's own plan menu lists five options and not one is cycling-specific. What each actually does on a bike, and what Polar says about the gap.

   →
2. 02

   TrainingPeaks workout not syncing to Polar Flow?

   Polar documents the rules that silently block a structured workout: a 20-phase cap, zone remapping to five, sport-type mismatch, and once-a-day sync.

   →
3. 03

   Polar FTP without a power meter: what still works

   Polar's Cycling Performance Test needs a power sensor and runs on eight watches. What an HR-only Polar rider can anchor training to instead.

   →
4. 04

   Training with just a Polar H10 and no watch

   An H10 and a phone is a complete free training stack for a cyclist. What Polar Beat records, what the strap's memory does, and where it stops.

   →
5. 05

   Is Polar FitSpark any good for cyclists?

   FitSpark cardio sessions run in any sport profile, so they do work on the bike. Why a daily suggestion is still not a cycling training plan.

   →