> 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/faq/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?

For the Fitbit-to-Google account migration, **keep using the Fitbit connection for both new and existing users**. The integration path is unchanged.

* **New users** authenticate through the same Fitbit OAuth flow.
* **Existing users** keep flowing until their account is migrated. At that point their token is invalidated and they must reauthenticate through the Fitbit flow. If their `user_id` changes, a `user_reauth` event with `old_user` and `new_user` is emitted so you can reconcile records.

Users should complete the in-app 'Move now' step before the Fitbit deletion deadline to preserve their account and history.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/data-api-sdk/account-config-environments-and-going-live/fitbit-to-google-migration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.