WorkoutPort blog

Sync Apple Health workouts older than 30 days to Strava

If you just connected Apple Health to Strava, your older workouts may not appear in its import list. Strava’s built-in importer is limited to the past 30 days and recordings from Apple’s Workout app. Strava documents both limits; checked on 16 October 2026.

WorkoutPort uses a separate Strava connection and can send older workouts that are still available to it in Health. Start with one old activity, then a small date range. You do not need to turn on automatic uploads to send a selected workout.

Check that the old workout is actually available

Find the activity in Health first. Then allow WorkoutPort to read workouts and the related data you want to send. In WorkoutPort, choose a date range that includes the activity and let that history load. An empty recent view does not establish that the older record is missing.

If the workout exists only in the recording app, look for that app’s direct Strava sync or file export. WorkoutPort cannot recreate a Health record it cannot read. If it was recorded by another app, the source restriction may also explain why Strava’s importer skipped it.

Send one representative workout

  1. Connect the intended Strava account in WorkoutPort.
  2. Find an older workout you can compare with the original, and use its manual Strava upload action.
  3. Open the resulting activity in Strava. Check its date, sport, elapsed time, and any distance, route or sensor data you expect.
  4. If the result is useful, select a small batch from the same source and date range.

A gym session may correctly have no map. A ride that originally had GPS needs a different check: verify that the route is available before assuming a summary-only result is complete. Our strength-workout example explains what a basic activity can contain.

Keep the history batch separate from future sync

Suppose you want September’s runs from one recording app, then automatic uploads for new runs from today. Treat those as two selections:

Fictional example: setup on 16 October
PurposeSelectionAction
Fill the September gapOne source, running, 1–30 SeptemberManually send a checked batch.
Keep new runs in syncThe same source and sport, from 16 OctoberPreview and save a rule; enable auto-sync when ready.

WorkoutPort’s new rules start from today by default. To include earlier dates in a rule, deliberately change that date and load the relevant history before trusting its match preview. A preview of loaded workouts is not a count of your entire Health store.

Check uncertain uploads before retrying

Keep one upload path for the same activities. If another app already sends them directly, avoid an overlapping bulk transfer. Check possible duplicates and uncertain results in Strava before retrying; changing a file name does not make it a different workout.

Keep the original history available until you have compared the transferred batch. For a larger move, use our five-point migration check. The steps here describe supported selection and upload behavior, not a completed real-account migration or a promise that unavailable data can be restored.