> 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.