Google plans to let Fit users move their historical data into the rebranded Fitbit app, Google Health, with the Google Fit to Google Health data migration option expected sometime before the end of this year, Android Authority reported. The tool does not exist yet, Google has not set a specific launch date, and the company has not specified which data types will transfer or how the process will work. Google has indicated Fit will be phased out later in 2026, but has not announced an exact shutdown date.
For users who have spent years accumulating step counts, workout logs, and health trends inside Fit, that last point is the one that matters.
What Google has confirmed
The confirmed facts are limited: Fit users will have the option to move historical data to Google Health, and that option is planned for sometime this year. Google did not provide a specific date. There is no support page, no user-facing tool, and no documented process. This is an early announcement rather than a launch with a confirmed shipping date.
Google's existing health infrastructure offers a sliver of context. Health Connect, the underlying platform powering Google Health, operates on a permission-based model: connected apps can access health records only with explicit user authorization. That architecture suggests the migration may require users to actively initiate the transfer rather than having it happen automatically in the background, though Google has not confirmed how the feature will plug into that framework.
What the Google Fit to Google Health migration still doesn't include
Google has not confirmed which data types are included, whether records will carry their original timestamps and associated metadata, whether the process is reversible, or how users will be notified when the option becomes available. Those are not minor technical footnotes. They are the questions that determine whether this migration is genuinely useful or just nominally complete.
Health data compounds in a way that most app data does not. A workout logged four years ago is not just a number. It carries a date, a duration, a distance, a heart rate trace, and connections to other metrics recorded at the same time. That full record is what allows someone to compare where they are now against where they were, notice a resting heart rate creeping up over six months, or see how sleep quality correlated with training load across a full year. Remove the timestamps, and the trend disappears. Flatten detailed records into daily totals, and the signal you actually wanted to keep is gone.
A migration that brings across a user's complete Fit history with every record and original timestamp intact is a different product than one that imports aggregate summaries or limits transfers to a rolling window of recent data. Both could technically be called a historical data migration. Only one solves the problem that makes users reluctant to switch in the first place.
Google has not said which of those it is building.
This is not an unusual situation for health platform migrations. Approaches vary considerably across the industry. Some platforms carry full record sets with original timestamps across every supported data type; others import summary data, apply a cutoff date to how far back the transfer reaches, or require users to confirm each data category manually. Some migrations are one-way; others allow reversal if something looks wrong after the fact. Without knowing Google's approach, it is not possible to judge whether this tool will fully reconstitute a Fit user's history inside Google Health or deliver something more partial.
The users most affected by that uncertainty are those with the longest continuous records. A few months of step counts are easy to rebuild or simply leave behind. Several years of consistent data spanning weight history, sleep patterns, resting heart rate trends, and exercise logs are not. For that group, a migration that silently drops older records or strips out metadata is not a meaningful solution, and there is currently no way to know whether Google's eventual tool will fall into that category.
There is also a process question that hasn't been addressed: what happens if the transfer fails partway through, or if some record types migrate cleanly while others do not? A well-designed migration tool provides a clear record of what was transferred and what was not. Whether Google will do that is unknown.
What Fit users should do now
Because the tool does not exist and its scope has not been published, there is nothing actionable here today. Exporting data from Fit manually or deleting the app would be premature. Pre-empting a process that has not been defined carries real risks, including ending up with an export format that turns out to be incompatible with how Google eventually structures the import.
The announcement that will actually be worth acting on is the one where Google specifies which record types transfer, whether original timestamps survive the move, and what the experience looks like, start to finish. "Later this year" is a planning horizon, not a decision point. Fit users are best served by staying put until the specifics arrive.
Google has not confirmed where migration documentation will be published when the feature gets closer to release. The Health Connect support page currently covers the permission framework that governs how apps access health records; it does not address Fit migration. That is the most likely place official guidance will surface when the feature is ready, and it is worth checking periodically as the year progresses.
What changes today, and what doesn't
One thing has shifted as of this reporting: Fit users now know a migration path is planned, which removes the uncertainty of whether one would ever be built. That matters for anyone who delayed engaging with Google Health specifically because they did not want to abandon their Fit history.
What has not changed is the more consequential question. A transfer that preserves years of detailed records with full timestamps is a different product from one that imports a partial set with the granularity stripped out, and there is still no way to tell which Google is building. The next announcement to watch for is the one where Google explains exactly what transfers and what does not. When that answer exists, Fit users will have enough information to decide whether switching is worth it. Until then, the right move is to hold on to what you have.
Comments
Be the first, drop a comment!