If you are one of the Fitbit loyalists who kept the original app alive by refusing to update, your run just ended.
Over the weekend, holdouts started seeing a prompt that has no real escape hatch: "A newer Fitbit app is available. Updating is recommended." The word is doing a lot of work there. The only button is Update, and users report they cannot tap past it. Nearly five months after Google renamed the Fitbit app to Google Health, the last door is closing.
And there is a second, quieter deadline that matters more than the prompt: Google's own developer documentation confirms the legacy Fitbit Web API will be turned off on October 30, 2026.
What Google's Docs Actually Say
This is not a rumor or a leak. It is published in Google's migration guide for developers, and it draws a hard line.
"On October 30, 2026, the Fitbit Web API will be turned off and will no longer function or sync data to or from Fitbit users."
The Fitbit Web API is the plumbing that lets outside apps read your Fitbit data. When it goes dark, every third-party service that never migrated to the new Google Health API stops syncing. That is the part most users will actually feel.
The migration is not a simple swap, either. Google notes that because the new system uses a different login technology, existing access tokens cannot be transferred, which forces users to re-authorize their integrations. Apps have to support both systems while the old one winds down, and the guide walks developers through mapping old Fitbit user IDs to new Google Health IDs. In short, the apps you rely on have real work to do, and anything that has not done it will break at the end of the month.
The App Switch That Started in May
Google began turning Fitbit into Google Health on May 19, 2026, with the rollout finishing by May 26. The new app rebuilt everything around four tabs (Today, Fitness, Sleep and Health) and added a Gemini-powered coach.
We laid the whole transition out back in Fitbit Is Dead: The Google Health App Transition Explained. What has changed is enforcement. Users who held on by keeping older app versions installed have been coasting for nearly five months. That is now over. Some can still dismiss the prompt for a moment, but others report the old app is already struggling to sync certain health metrics.
There is more unannounced cleanup on the way. Google Health version 5.08 removed support for signing in with legacy Fitbit accounts back in September, quietly following the earlier account migration deadline. Between that and the Web API shutdown, Google is methodically tearing down the old Fitbit infrastructure in public view.
Why Users Are Upset
The reaction has been loud, and it is really about features people lost in the switch. Badges, the old Sleep Profile animals, the Community Feed and direct messages were all removed. Food logging, stress tracking and the way some health metrics display also changed.
"I hate the new Google Health app," one user wrote. "I routinely swiped back to view my workout and sleep data from previous days and that ability is now gone. I'm a Premium member so I'm paying for this new garbage."
Another was blunter: "Google health app is so baaad. I also want my Fitbit app back." When asked what made the original so good, a third said the food tracking was "next level" and its HRV-based illness detection was the feature they would miss most.
Google has not ignored all of it. Custom food logging came back in July, and later updates improved sleep displays, dashboard customization and activity tracking. Some users say they have come around to the new app. But the core complaint, that Google Health does not feel like the product people chose, has not gone away.
The Upside, If You Want It
It is not all loss. Google Health added Apple Health sync on iOS, which the old Fitbit app never offered, so your data finally talks to Apple's ecosystem. We covered that shift when it landed in Your Fitbit Finally Talks to Apple Health.
The bigger question is whether you stay at all. Plenty of Pixel Watch and Fitbit owners have already been shopping around, and cheap Amazfit watches have been the beneficiary. We wrote about that migration wave in Pixel Watch Owners Are Ditching Google Health for $170 Amazfit Watches.
What This Means for You
If you use the Fitbit app directly, the choice is made for you: update to Google Health and re-learn the layout, or leave. There is no third option coming.
If you use third-party apps that sync your Fitbit data, check them this month. Anything still clinging to the legacy Fitbit Web API has until October 30 to move to the Google Health API, and you may need to log back in and re-authorize once it does. If an app goes quiet on November 1, you will know why.
Bottom Line
Google has been signaling this for years, and now the infrastructure is actually going away. The forced app update closes the loophole for holdouts, and the October 30 Web API shutdown closes it for the apps that kept the old experience alive on the side.
The smart play in the next two weeks is simple. Update the app, then open every health and fitness service you have connected to Fitbit and confirm it still syncs. Anyone who has not migrated by the end of the month will not get a warning when their data stops flowing, they will just notice the gap.
If you are ready to move on entirely, the Fitbit Charge 6 is still widely available, and the Google Pixel Watch 3 is the natural upgrade if you want to stay inside Google's ecosystem.
Sources: Google for Developers Google Health API migration guide (states the Fitbit Web API is turned off October 30, 2026); Google Health Help Center; TechRadar; Gadgets & Wearables; MyFitnessPal support documentation; user reports on social media. The October 30 cutoff comes from Google's own developer documentation. The forced update prompts are from user reports and media coverage; Google has not published a separate consumer-facing notice for the app update itself.
