> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/help-center/help-topics/data-api-sdk/account-config-environments-and-going-live/fitbit-to-google-migration.md).

# How do I handle the Fitbit-to-Google migration?

Google turned off the legacy Fitbit Web API on 2 November 2026, so Fitbit connections no longer receive data. Move your users to the Google Health connection.

**Google turned off the Fitbit Web API on 2 November 2026. Fitbit connections no longer receive data, and new users can't connect through Fitbit. Move your users to the Google Health connection (`GOOGLE_HEALTH`).**

* **Enable it:** in the dashboard, open Connections for your environment and add Google Health. Terra manages the credentials, so there's no Google app to register.
* **Each user connects once:** Fitbit authorisations can't be carried over, so every user signs in with their Google account. They keep their Fitbit device and the Google Health app; nothing changes on their side apart from the sign-in. See [Google's migration guide](https://developers.google.com/health/migration).
* **Create the session with the same `reference_id`:** call `POST https://access.tryterra.co/api/widget/session` with `providers` set to `GOOGLE_HEALTH` and the `reference_id` you already use for that user. `providers` is a comma-separated string, not an array.

{% code title="POST <https://access.tryterra.co/api/widget/session>" %}

```json
{
  "reference_id": "<your existing reference_id for this user>",
  "providers": "GOOGLE_HEALTH"
}
```

{% endcode %}

* **Match on `reference_id`:** the Google Health connection has its own `user_id` and sends `auth_success`, not `user_reauth`. Your existing Fitbit connections stay in your user list so you can match them.
* **History:** on connect, Terra fetches up to the last 12 months that Google holds. It's available through the REST API and isn't sent to your destination.
* **Fields differ:** see [What data does Google Health deliver, and how does it differ from Fitbit?](https://docs.tryterra.co/help-center/help-topics/data-api-sdk/provider-coverage-and-per-provider-data-availability/google-health-data-coverage) before switching your app over.

Need a list of your users still connected through Fitbit? Contact <support@terra1314.zendesk.com>.
