Weight measurements are in there too, but I didn’t step on the Fitbit scale during this time period. It just saves totals per day, but also inclusive of things like floors and minutes sedentary. Looking first at steps, it’s pretty clear cut. I decided to take a peek at the file, since I was curious how much data could be moved over. It serves me well when at the ice cream sundae bar, so I figured it works fine here too.Ī few seconds later I got the file to download: Mostly because when in doubt, just choose everything. I then checked all the boxes on the right side. So, I just did basically the last month’s worth, since I’ve been wearing the new Fitbit Charge 2 during that time period. Now the really important part here is another limitation that Fitbit has on exporting out data, which is limited to 31 days at a time. On the Fitbit site, you’ll go under Settings and then Data Export: To be clear, that’s Fitbit’s issue for not just having a giant ‘Download everything’ option. Whereas for workout data, you’ve gotta do it one by one (which sucks…every…single…activity). For step data, you can do it all in one giant shot.
Garmin helpfully links to Fitbit’s own support page on how to export your data. Whereas the Fitbit body data is specific to the formatting that Fitbit has created. In the case of the workout files, those three file types cover basically everyone/everything out there. Next you’re given the option to import either specific activity/workout files, in GPX/FIT/TCX format, or Fitbit scale and activity data. Instead, you have to know to click on the bust on the left side, which then shows you an ‘Import Data’ option. I would have thought the very first thing Garmin Connect would have asked upon creation of a new account is “Do you have any previous activity tracker data to import?”. In fact, even the press release doesn’t have a link or anything on how to set this up. Now Garmin doesn’t exactly make it obvious as to where to go. Totally virgin, not a single step walked or night slept (with anyone). So I created a new random account on Garmin Connect. Now in order to test this, I wanted a completely clean slate.
(As to why I have two posts on Garmin updates today instead of one, it’s simply because I broke them apart when I had to wait while Garmin fixed some issues I was having.) Testing it out: Almost like when Garmin trolled Apple during their Apple Watch announcement. Speaking of which, the service is actually named: Fit a Bit. Whereas the rest of this post is all about the Fitbit to Garmin migration piece. I talked about Strava Beacon here, and this essentially allows you to have your Garmin device trigger the Strava Beacon service (*see my 5-second thoughts on this at the end of this post). The first combo-dish one I dove into in a separate post already today, and the second one I’m less interested in.
garmin_connect_fit_to_xlsx.py -e -o garmin.Over the last few days, Garmin made three fitness related software announcements:Ī) They (finally) enabled you to combine activity tracker data from multiple devices into one cohesive pictureī) They enabled Strava Beacon support through Garmin Connect MobileĬ) They took a swipe at Fitbit by enabling you to migrate off Fitbit and onto Garmin Into a Excel XLSX file with worksheets for the file device headers, monitoring info headers, monitoring data, derived hourly stats,ĭerived daily stats, and derived overall stats.
Garmin_connect_fit_to_xlsx - turns a directory of monitoring FIT files, exported from the Garmin Connect daily view (export original), garmin_connect_csv_to_xlsx.py -s -o garmin.xlsx -i 20170314_csv Garmin_connect_csv_to_xlsx - turns a directory of CSV files exported from Garmin Connect Reports pages into an XLSX file with the Garmin - GarminXlsxWriter writes Excel XLSX files suing data extracted from Garmin filesįit - parses FIT files, mostly focused on monitoring FIT files for now Tools for manipulating Garmin files (csv, fit) written in Python. Once you have your data in a DB you can export it to CSV or XLXS using a DB browser. You can achieve all of the same results with the garminDB project.