Changing autodata source: best practice?

I have been beeminding my daily steps using Fitbit as my autodata source. Now I’m contemplating switching to Garmin.

This from 2015 and this from 2016 as well as this much more recent advice all suggest that it’s something that has to be done behind the scenes with an emailed request to support. All good.

But to that end, what is the recommended procedure for setting things up and making such a change – from the user’s end – so as to ensure everything runs smoothly. Anything in particular to do or to avoid?

1 Like

I wouldn’t overthink it! :slight_smile: My only suggestion would be that it’s
easier and less stressful as a user if you aren’t right at a
beemergency when ask support to switch you over.

Hi! Support here to weigh in. :grin: It’s pretty much just as I described in the recent thread:

Anyway, what you’ll need to do is create a new goal with the integration settings you want (the graph doesn’t matter and will be deleted), and then send an email to to ask us to switch it over. You’ll need to include the link to the old goal and the new goal – naming it something like “temp-run” will make it easy for us to tell which one is which. :slight_smile: We’ll switch the new autodata info into the goal, and then delete the temporary one.

In some cases there might be an issue with the new data source overwriting recent data from the other data source. In those cases, we’ll need to fix up the graph for you… but it usually isn’t a problem, and we can easily do that.

If you wanted to be absolutely iron-clad sure there was no gap in your data, you’d want to record everything in both services (Fitbit and Garmin, in your case) for a week so if any data gets overwritten, it just gets overwritten with the same info… but I honestly wouldn’t recommend it and I don’t think I’ve seen any problems with this kind of thing lately!

1 Like