How to export your Fitbit data in 2026: heart rate, sleep, and the July 15 deadline
If you're looking for the old fitbit.com dashboard export, it's gone — the Fitbit app became Google Health on May 19, 2026, and most export instructions still floating around the web point at screens that no longer exist. Your data is still exportable today, through three routes: a full archive via Google Takeout, a quick date-range export in the app, and per-workout TCX files. But two deadlines land on July 15, 2026 — days from now — so if you have an unmigrated legacy Fitbit account or history in any removed feature, export first and read the details after.
What changed in May 2026 (and why most guides are now wrong)
Google announced on May 7, 2026 that the Fitbit app would become the Google Health app, and the switch rolled out automatically on May 19. Fitbit lives on as the hardware brand; the software is Google Health now. The transition also removed a long list of features: badges (including your historical collection), groups and the community feed, direct messages, custom profiles, Sleep Profile and the monthly sleep animals, snore detection on Sense and Versa 3, and the estimated oxygen variation graph. The fitbit.com web dashboard had already been retired earlier.
The practical consequence: any guide that tells you to visit the fitbit.com dashboard or dig through the old Fitbit app's settings is describing software that no longer exists. Here is what works as of July 2026.
The two July 15, 2026 deadlines
- Unmigrated legacy Fitbit accounts. If you never moved your Fitbit account to a Google account, Google begins permanently deleting that account's data on July 15, 2026. Sign in, export everything, and migrate — in that order.
- Removed-feature data. History tied to features cut in the transition — badges, group activity, community posts, Sleep Profile history — can be exported until July 15, 2026. After that it's deleted for everyone, migrated or not.
Your core health data — steps, heart rate, sleep, workouts — carried over into Google Health automatically and is not scheduled for deletion. The deadlines are about the legacy account data and the retired features.
Route 1: Google Takeout — the full archive
This is the complete export: every reading your tracker ever synced.
- Go to takeout.google.com and sign in with the Google account your Fitbit data lives in.
- Click Deselect all, then scroll down and check Fitbit only. (The checkbox still says Fitbit, not Google Health — the label hasn't caught up with the rebrand.)
- Click Next step, choose delivery by email link and .zip, and click Create export.
- Wait for the email. Small archives arrive in minutes; years of intraday heart rate can take hours.
You'll download a zip with a folder per data domain — physical activity, sleep, SpO2, and so on. It is thorough and free, but it is JSON, not spreadsheets — more on that below.
Route 2: the in-app export — quick, recent, CSV-capable
For a recent window rather than your whole life, the app export is faster: open Google Health → profile → Settings → Export your data, pick the date range, the data types, and the file format (CSV or JSON), and download to your phone or Drive. If you still sign in with a legacy Fitbit account (no Google migration), the account settings expose the same idea as a Data Export page — use it before July 15, because that whole account is on the deletion list.
Route 3: per-workout TCX files (GPS routes)
Individual GPS activities export separately: open the workout in the app, tap the three-dot menu, and choose Export as TCX. TCX imports cleanly into Strava, Garmin Connect, and most training tools. This is per-activity only — there's no bulk TCX export.
What the exported files actually look like
| Data | File | Format | Granularity |
|---|---|---|---|
| Heart rate | One file per day | JSON | Intraday — a reading roughly every 5 seconds during activity |
| Resting heart rate | Daily summary series | JSON | One value per day |
| Sleep | One file per night | JSON | Start, end, and seconds per stage (Awake, Light, Deep, REM) |
| Steps / distance / calories | Daily and intraday series | JSON (CSV via in-app export) | Per minute or per day |
| GPS workouts | One file per activity | TCX | Full route and samples |
The heart rate files are the ones that surprise people with size: at a reading every ~5 seconds, a multi-year archive runs to hundreds of files and gigabytes of JSON.
Turning Fitbit JSON into CSV
Excel and Google Sheets can't meaningfully open nested JSON, so you have two options. For recent data, just use the in-app export and pick CSV. For the full Takeout archive, a few lines of Python flatten a day of heart rate into rows:
import json, csv, glob
rows = [(r["dateTime"], r["value"]["bpm"]) for f in glob.glob("heart_rate-*.json") for r in json.load(open(f))]
csv.writer(open("heart_rate.csv","w")).writerows([("time","bpm"), *rows])
Sleep files follow the same pattern — pull startTime, endTime, and the stage summary out of each night's JSON. If you'd rather not script it, that's exactly the gap the Apple Health route below closes for iPhone users.
On iPhone? The Apple Health route
If you're on an iPhone — or moving from Fitbit to an Apple Watch — it usually makes more sense to get your health data into Apple Health and treat that as the single source you export from.
Being honest about the plumbing: Google Health can connect with Apple Health, but there's no dependable built-in path that writes your Fitbit history into Apple Health. What works today is a third-party sync app (search the App Store for "Fitbit to Apple Health" — several established options exist, free and paid) that copies steps, heart rate, sleep, and weight from your Fitbit account into HealthKit.
Once the data is in Apple Health, HealthSave takes over the export problem properly:
- Per-metric CSV or JSON — heart rate, resting HR, HRV, sleep with stages, steps, and more, each as a clean table instead of a folder of JSON.
- Pick metrics and a date range — not an all-or-nothing dump.
- On-device — HealthSave reads HealthKit on your iPhone; your health data doesn't leave the phone unless you export the file somewhere.
And if you already have Apple's own export.zip from the Health app, our free browser converter turns that XML into per-metric CSV without installing anything — it runs entirely in your browser.
Honest limits
- HealthSave does not read Fitbit accounts or Google servers. It reads Apple Health on an iPhone. Your Fitbit data has to land in HealthKit first, via a sync app — that step is a third party's, not ours.
- Google Takeout is the only complete archive. Nothing else, ours included, gets you the full raw history in one shot. Start there; keep the zip.
- The Google Health transition is recent and still moving. Menu paths in this guide match July 2026; Google's roadmap promises further changes, so if a screen has drifted, the Takeout route is the stable fallback.
- Accuracy is your tracker's. Exports faithfully reflect what the device recorded — they don't validate or correct it.
- HealthSave and Keltek AI are not affiliated with Google or Fitbit.
Frequently asked questions
Can I still export Fitbit data from the fitbit.com dashboard?
No. The web dashboard is retired and the app is now Google Health. Migrated accounts use Google Takeout or the in-app export; legacy Fitbit-login accounts still have a Data Export settings page, but that data is scheduled for deletion — export now.
How do I export Fitbit heart rate data?
Google Takeout with "Fitbit" selected gives you per-day JSON files of intraday heart rate (a reading roughly every 5 seconds during activity) plus resting heart rate summaries. For a recent window, the in-app export with a date range is quicker.
How do I export Fitbit sleep data?
Sleep arrives as one JSON file per night — start time, end time, and seconds in each stage (Awake, Light, Deep, REM) — in the same Takeout archive, or via the in-app export for a chosen range.
Is exporting free, or do I need Premium?
Free. Takeout and the in-app export don't require Premium. Subscriptions gate insights inside the app, not your raw data.
What happens on July 15, 2026?
Unmigrated legacy Fitbit accounts start being permanently deleted, and removed-feature data (badges, groups, community posts, Sleep Profile history) is deleted for everyone. Neither is recoverable.
Does Fitbit sync with Apple Health?
Not natively in the write direction — use a third-party sync app to copy Fitbit data into Apple Health. Once it's there, HealthSave exports it as per-metric CSV/JSON like any other HealthKit data.
How do I open the Fitbit JSON in Excel?
Convert it first — the in-app CSV export covers recent data, and a short script (example above) flattens the Takeout JSON. Or route the data through Apple Health and export CSV from there.
Related
- Export heart rate data from Apple Health to CSV, JSON, or PDF
- Export sleep data (with stages) from Apple Watch
- Apple Health's export is an unusable XML file — how to get real CSV
- Back up Apple Health data before switching platforms
Get HealthSave
If your data lives in (or lands in) Apple Health, HealthSave gets it out as clean per-metric CSV/JSON, on-device, no account.
Download HealthSave on the App Store