---
title: "Moving a Fitbit user to a Google Account"
canonical: "https://help.validic.com/space/VCS/3755213034/Moving%20a%20Fitbit%20user%20to%20a%20Google%20Account"
format: markdown
---
###### **This article pertains to:** ​[INFORM (V2)]

---

Google is requiring all Fitbit user accounts to move to a Google Account by **May 19, 2026**. After this date, users who have not migrated will lose access to their Fitbit data and integrations.

**"Does this mean all of our Fitbit users will have to re-authorize the sharing of their data via the Validic Marketplace after they make this move?"**

**Short answer:** No — *as long as they complete the migration before the deadline*.

**Longer answer:** Fitbit has confirmed that users will NOT be disconnected from any 3rd party sources when moving to a Google Account. The Validic Marketplace does not require any changes, and all existing Fitbit user tokens will remain valid. There is no action required for you or your users related to the migration itself.

## Important: What Happens If Users Don't Migrate

If a user does NOT complete the migration by May 19, 2026:

1. **Their Fitbit login will stop working**
2. **Historical health data will no longer be accessible** (and may be deleted)
3. **They will need to re-authorize in Inform** once they complete the move
4. **New data will not sync** until re-authorization is complete

This is a critical distinction: tokens remain valid *through* the migration, but users who miss the deadline will face a disruption requiring re-authorization.

## How a user can move from the Fitbit login to GoogleAuth

As part of the process to move a user from Fitbit to Google, the Fitbit app presents users with a screen that shows them all of their current 3rd party app connections along with the ability to disconnect any they want.

![FB-Google-disconnect-screen.PNG](media://c3c79ea3-0616-4fdf-b739-b360c47bd554)

Users have actually always had this ability via the Fitbit app and web portal. The page was just rather well hidden and a Fitbit user had to actively seek it out if they wanted to manage their 3rd party connections.

Now, Fitbit is directly walking each user through this page.

Fitbit has their own FAQ on this change here: [https://support.google.com/fitbit/answer/14237024?hl=en](https://support.google.com/fitbit/answer/14237024?hl=en) 

### Best Practice

**Encourage your users NOT to disconnect your app/program when they see it on this screen.**

If they disconnect your app during migration, they WILL have to go back to the Validic Marketplace and re-authorize your access to their Fitbit data.

---

### For Clients Managing Their Own Developer Accounts

If you manage your own Fitbit developer credentials on [http://dev.fitbit.com](http://dev.fitbit.com)  (rather than using Validic-managed credentials), you must also migrate your developer account to a Google Account before the deadline. Failure to do so will result in loss of API access.

Validic manages credentials for many clients and will handle transitions automatically for those accounts.