How to Sync “Historical Data” When Moving to a New Health Platform

Switching your primary fitness tracking ecosystem—such as moving from iPhone to Android, upgrading from a Fitbit to a Garmin, or adopting an Oura Ring—often feels like starting over from scratch. When you pair your new device, your previous years of workouts, step counts, and sleep stages do not automatically transfer over.

Ecosystems are designed to sync forward from the day you set them up, and operating systems intentionally restrict the automatic transfer of legacy databases. However, you can migrate your historical fitness records using export tools, bridge software, and file imports.

Quick Answer

Historical health data does not sync automatically across platforms due to API restrictions and format differences. To move past data, use a dedicated migration bridge like RunGap (on iOS) or Health Sync (on Android) to transfer records between accounts, or export your historical files as .FIT or .GPX archives and upload them directly into your new platform.


Device & Signal Snapshot

  • Migration Routes: Apple Health to Google Health Connect, Fitbit to Garmin, Garmin to Apple Health, Samsung Health to Wear OS/Google.
  • Supported Historical Data: Workouts, GPS routes, heart rate tracks, step counts, body weight.
  • Non-Transferable Data: Proprietary recovery scores (Body Battery, Readiness), workout badges, personal records, and sleep stage classification algorithms.
  • Risk Level: Moderate (improper imports can cause duplicated historical steps and skewed multi-year averages).

Why Historical Data Doesn’t Move Automatically

When you connect a new service to Apple Health or Google Health Connect, you might expect your complete history to populate immediately. It does not transfer automatically for three specific reasons:

                 [New App Connected to Health Connect / Apple Health]
                                          │
        ┌─────────────────────────────────┼─────────────────────────────────┐
        ▼                                 ▼                                 ▼
[API Guardrails]                  [Schema Differences]              [Database Locks]
Health Connect limits reads to    Different definitions for         Exporting raw XML or JSON
the past 30 days for newly        sleep stages, VO2 max, and        requires active conversion
authorized applications.          active versus total calories.     before an import can process.
  1. The 30-Day API Window: Google Health Connect enforces a privacy safeguard that prevents newly installed apps from querying data older than 30 days [1]. This prevents new apps from scanning years of personal health history in the background.
  2. Proprietary Data Schemas: Apple HealthKit, Garmin, and Samsung Health store metrics differently. For instance, Apple tracks Heart Rate Variability using SDNN, whereas Garmin, WHOOP, and Oura calculate HRV using RMSSD [2]. Because these mathematical formats differ, health databases will not blindly merge them.
  3. Walled Ecosystems: Manufacturers want you to stay within their hardware family. While exporting your raw data is legally mandated under consumer privacy laws, companies have little incentive to build simple, one-click import tools for competing platforms.

If your switch also involves setting up a new smartphone, follow How to Transfer Your Smartwatch to a New Phone Without a Factory Reset to keep your watch connected without wiping local storage.


Step-by-Step Migration Paths

Method 1: The Cross-Platform Bridge (Health Sync & RunGap)

The most reliable way to migrate historical data without using a computer is through a specialized mobile bridge app.

  • Moving from Android to iPhone (or Garmin/Fitbit to Apple Health):
    1. Download RunGap on an iOS device.
    2. Open RunGap and navigate to Accounts & Settings.
    3. Log in to your source accounts (e.g., Garmin Connect, Polar, Suunto, or Strava) and your destination account (Apple Health).
    4. Enable Use as Source for your old service, and Use as Destination for Apple Health.
    5. Go to the main menu, select Activities, tap the upper-right settings icon, and select Update Activities.
    6. Use the “Swag Bag” feature to batch-export historical workouts, complete with sensor data and GPS routes, directly into HealthKit.
  • Moving from iPhone to Android (Apple Health to Health Connect/Samsung Health):
    1. Download Health Sync from the Google Play Store on your Android phone.
    2. Select your source: choose Apple Health (which requires installing the Health Sync companion app on your old iPhone to extract the database).
    3. Select your destination: choose Health Connect or Samsung Health.
    4. When prompted to configure historical sync, select your date range.
    5. Note on Android: Because Health Connect restricts background bulk imports [1], Health Sync transfers older records in controlled intervals to avoid triggering operating system limits.

If you run into permission errors while setting up Health Connect on newer Android devices, see Fixing “Health Connect” Sync Issues on Android 16.


Method 2: Bulk File Export and Import (FIT / GPX)

If you are moving to platforms like Garmin Connect or Strava, you can bypass mobile apps entirely by importing files directly through web portals.

[Old Service Web Portal] ──> [Request Data Archive / Export .FIT] ──> [New Service Portal] ──> [Upload Files]
  1. Garmin Connect: Log into Garmin Connect on a web browser, click the cloud icon (or Activity list), and select Import Data. You can drop up to 99 .FIT, .GPX, or .TCX files at once.
  2. Strava: Log into Strava via a desktop browser, select the + icon at top right, and click Upload Activity > File. You can upload batches of 25 files at a time.
  3. Apple Health Full Archive: On your iPhone, open Health, tap your Profile Icon, scroll down, and tap Export All Health Data. This generates an export.xml archive. Because raw XML files cannot be read directly by Garmin or Android devices, you will need a third-party conversion tool to parse the data into individual .FIT files.

What Transfers Cleanly vs. What Gets Left Behind

Before migrating your history, keep these platform limitations in mind:

Data TypeMigrates Successfully?Technical Reason / Limitation
GPS Workout TracksYesStandard .GPX and .FIT coordinate formats.
Workout Heart RateYesTime-stamped pulse samples transfer cleanly.
Step CountsPartialTransfers as total numbers, but hourly distributions may be lost.
Sleep StagesRarelyAlgorithms differ; most apps will only import total sleep duration.
VO2 Max & Training LoadNoProprietary to device firmware; new platforms require new activities to calculate baselines.
Badges & ChallengesNoLocked to the original brand’s ecosystem.

If you notice that your daily step counts duplicate after importing past records, follow the steps in Apple Health vs. Google Fit: Fixing the “Double Counting Steps” Bug to correct device prioritization.


Bottom Line

Historical health data will not transfer automatically when you switch platforms because of privacy safeguards and incompatible data formats. Use a bridge app like RunGap or Health Sync to move past records, or export raw .FIT files directly from your old service’s web portal to carry your workout history into your new platform.