> 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/google-fit-2026-deprecation.md).

# How does the 2026 Google Fit deprecation affect me?

Terra's 'Google Fit' SDK provider reads Health Connect on the device and needs no migration, but users on the web Google connection should move to Google Health.

Terra's **'Google Fit' SDK provider** (`GOOGLEFIT`) reads **Health Connect on the device**, not the Google Fit REST API, so it **requires no migration**.

The piece affected is the **web 'Google' connection** (`GOOGLE`), which reads the Google Fit REST API. Google says [the Google Fit APIs are only supported until the end of 2026](https://developer.android.com/health-and-fitness/health-connect/migration/fit) and recommends the Google Health API for cloud integrations.

**Move web Google users to the Google Health connection (`GOOGLE_HEALTH`).** It is a separate provider, so nothing carries over and each user connects once through it. Apple Health and Health Connect users are not affected.

See the [mobile SDK docs](https://docs.tryterra.co/health-and-fitness-api/mobile-only-sources) for the SDK route.