Guide News Free Tool Already have a key?
Google Health → CSV

Google Health
data,
as CSV.

After the 19 May 2026 rebrand, the Fitbit app became Google Health. The export format didn't change, but your search query did. Same Takeout ZIP, same JSON files inside, same problem. Wearable Converter turns it into CSV in your browser.

Choose Your Path ↓ How it works
Overview

What this
page covers.

If the Fitbit logo on your phone disappeared and you now see the Google Health icon, you're in the same boat as before. The app is rebranded, but the export structure is identical. Google Takeout still spits out a folder of JSON files, and you still need them as CSV before anything useful can happen.

This page covers both reasonable destinations for that data, since "Google Health to CSV" can mean a few different things depending on what you actually want next.

Choose your path

Where do
you actually need it?

Two paths, same source data, same browser-based conversion.

Path A

I want it in Garmin Connect

Google Health is fine, but you want a real device. Or you've already bought a Garmin and just need your history moved across. The converter outputs Garmin Connect's required CSV format directly.

Garmin migration →
Path B

I want spreadsheets

You're not switching to Garmin, you just want your data outside Google's walls. Year-split CSV files plus a branded XLSX workbook with monthly and yearly summaries already calculated.

Spreadsheet export →
The rebrand context

Same data,
different app name.

On 19 May 2026, Google rebranded the Fitbit app to Google Health. Same servers, same accounts, mostly the same UI. A handful of features got removed or moved behind a $9.99/month AI Coach paywall, but the data export pipeline is unchanged.

That means if you used the Fitbit app before the rebrand and Google Health after, your Takeout export looks the same in both cases. The folder is still called Fitbit/. The JSON files are still named the same way. Same daily activity, sleep, heart rate, body composition records.

If you were on the original Fitbit app and never migrated your account to Google, the 15 July 2026 data deletion deadline has now passed and the export window for those accounts has closed. A Takeout ZIP saved before the deadline still converts. If your app says Google Health, you can export fresh any time.

FAQ

Common
questions.

My app shows Google Health, not Fitbit. Does this still apply?
Yes. The 19 May 2026 rebrand changed the app name and some features, but not the export format. Your Takeout export still produces the same JSON structure inside a folder still called "Fitbit". The converter processes either identically.
Was my data deleted on 15 July 2026?
Only if you were on the original Fitbit app and never migrated your account to Google. If your app is now showing as Google Health, your account migrated and your data is safe; the deadline never applied to you. Either way, exporting is a good move, a Takeout ZIP is a permanent offline copy of your history.
What features did Google remove in the rebrand?
Badges, Sleep Profile, Stress Score, social features, the Fitbit Community forum, daily goal customisation, and a few smaller things. Most premium features now sit behind the new AI Coach paywall. If any of these mattered to you, the data you logged while using them is still in your export.
Will the CSV include my sleep and heart rate data too?
The Garmin migration path focuses on what Garmin Connect can actually import (daily activity, body composition). The spreadsheet path includes activity and body data in clean tables. Detailed intraday heart rate and sleep stage data is in your Takeout export but isn't included in the CSV output yet.
Was the data deletion deadline real?
Yes. Google confirmed it in official communications and began deleting unmigrated Fitbit account data on 15 July 2026. If you're unsure which type of account you had, open the app: if it launches into Google Health and you're signed in with a Google account, your account migrated and your data is safe.
Related

Other
angles on this.

Same problem, different framings. Helpful if your specific search query isn't quite this one.

Google Takeout to CSV→

Starting from the Takeout export itself

Fitbit to CSV→

For users still calling it Fitbit

JSON to CSV (Fitness Data)→

The technical framing of the same problem

JSON to Garmin→

If your destination is specifically Garmin Connect