What Fitbit files should I upload?
Upload individual files named weight-YYYY-MM-DD.json from the Global Export Data folder. Extract the Google Takeout ZIP first; do not upload the ZIP itself.
Convert your Fitbit data from Google Takeout to Garmin-compatible .fit files and Fitbit CSV imports for steps
Best-effort conversion — Fitbit's export data is messy, so test with one file first. Here's what can go wrong.
Convert Fitbit weight JSON files from Google Takeout into FIT files for Garmin Connect—no scripts or command line.
Open Google Takeout, select Fitbit, and request a ZIP archive. Download and extract it when Google says it is ready.
Open the Fitbit Global Export Data folder and select up to 3 files named weight-YYYY-MM-DD.json. Do not upload the ZIP.
Download the generated FIT files, then use Garmin Connect's Import Data feature. Test one file before importing the rest.
Google sign-in identifies your TrackerSync account and helps apply fair usage limits.
TrackerSync receives your name and email only.
It does not access Google Drive, Fitbit, or your Google Takeout archive.
Sign in with GoogleStart with one small file. Once you have checked the result, you can convert up to 3 files per batch.
TrackerSync turns Fitbit weight JSON exports into Garmin FIT weight files. Sign in, upload up to 3 weight-YYYY-MM-DD.json files, and download the converted files. TrackerSync carries across the recorded date, time, weight, and valid body-fat value. Garmin Connect decides whether each file is accepted.
See product troubleshooting and import behavior in the homepage FAQ hub.
Use the original weight-YYYY-MM-DD.json files from the Global Export Data folder in your extracted Fitbit archive.
TrackerSync automatically estimates whether the exported values use kilograms or pounds. Because some weight ranges are ambiguous, check a small sample in Garmin Connect before converting more files.
The converter reads the recorded weight, date, time, and valid body-fat percentage. It does not invent BMI, muscle mass, or other body-composition measurements that are missing from the Fitbit export.
TrackerSync creates a valid FIT weight file, but Garmin Connect controls the final import and may handle optional body-composition fields differently.
Still need the archive? Start with how to export Fitbit weight data with Google Takeout, then come back with the weight-YYYY-MM-DD.json files.
Upload individual files named weight-YYYY-MM-DD.json from the Global Export Data folder. Extract the Google Takeout ZIP first; do not upload the ZIP itself.
Open Google Takeout with the Google account connected to Fitbit, select Fitbit, and request a one-time ZIP export. Download and extract the archive when Google notifies you that it is ready.
Preparation time varies with the size of the archive and Google's processing. Wait for Google's notification rather than requesting multiple duplicate exports.
Yes. TrackerSync automatically estimates whether the source values use kg or lb and writes the weight into the FIT format. Check one converted file first because some value ranges can be ambiguous.
Valid body-fat percentages are included when they are present in the Fitbit record. TrackerSync does not create body-fat or other measurements that are missing.
Confirm that you selected a weight-YYYY-MM-DD.json file and use Garmin Connect's Import Data feature rather than its activity-upload screen. Test one converted file at a time.
Yes. TrackerSync is free to try. Google sign-in is required, and usage limits help keep the service available.