Google Health vs Google Fit: differences and how to migrate

Google Fit has been the default Android fitness hub for years. In 2026, Google is officially retiring it. The replacement is not another version of Google Fit, but a completely new product called Google Health, built on the same infrastructure as Fitbit and powered by Gemini AI. If you used Google Fit to view your steps, workouts, and sleep, here is what you need to do to keep everything working.

What is Google Health and what changed

Google Health (available at healthapp.google) is the unified consumer health platform that replaces both Google Fit and the standalone Fitbit app. It works on iOS and Android and consolidates data from wearables, apps, and medical records into one view.

• •Google Health Coach: an AI assistant built with Gemini that creates personalized workout plans, sleep advice, and recovery guidance. Requires a premium subscription.
• •Fitbit integration: Fitbit devices now report into Google Health directly. Separate Fitbit app login is no longer required.
• •iOS and Android: unlike Google Fit which was Android-only, Google Health is available on iPhone too.
• •Medical records: import health data from compatible providers for a unified view alongside fitness metrics.
• •Free base tier: steps, sleep, heart rate, and activity history are free. Gemini coaching requires a paid subscription.

Google Fit vs Google Health: what changed

The problem Google Health doesn't solve: seeing multiple wearables together

Google Fit had REST APIs that many apps used to read and write workout data. Google Health is a consumer app, not an open API platform, and it mainly integrates well with Fitbit and Pixel Watch. If you also use Garmin, Samsung Health, or other wearables, the common thread connecting them all is still Health Connect, the local data layer built into Android.

• •Health Connect is the hub: every major Android wearable app (Garmin Connect, Samsung Health, Polar Flow, Withings, Fitbit) writes data to Health Connect.
• •Google Health reads Health Connect: the new app reads from Health Connect, not the other way round.
• •FitMesh reads Health Connect and multiple wearables: it aggregates data from Health Connect and from providers like Garmin and Fitbit (today via Health Connect) into one dashboard. Syncing with Strava is already live with OAuth read access; write-back of workouts is still in development. A TrainingPeaks integration (TCX export via a Personal Access Token) is also in development and not yet available.

How to migrate: step by step

1. Check Health Connect is active: open the Health Connect app on your Android device. If it is not installed, download it from the Play Store. Your most recent data from other apps may already be visible here; for your full history see the Google Takeout step below.
2. Download Google Health: install the new Google Health app from the Play Store or App Store and sign in with your Google account.
3. Connect your wearables to Health Connect: if you use Garmin, Samsung Health, Polar Flow, or other apps, make sure they have Health Connect write permissions enabled. This is how they will continue writing data after Google Fit is gone.
4. Set up FitMesh: if you use wearables beyond what Google Health covers (like Garmin), install FitMesh and grant it Health Connect read permissions. FitMesh brings all your data together in one dashboard.
5. Don't rush to remove Google Fit: export your data with Google Takeout first, then wait for Google's official invitation to migrate (expected later this year, 2026). Only remove Google Fit after verifying Google Health shows your data correctly.