The short answer
If you searched for a way to sync Google Health Connect to Apple Health, here is the part nobody states plainly: the two platforms do not sync to each other. Apple Health is the on-iPhone store that Apple calls HealthKit. Health Connect is the equivalent hub on Android. Each one is a private vault on its own device, and neither reads the other.
That sounds like a dead end, but it is not. There are three practical paths, and the right one depends on whether you actually need the raw data to live in both places, or whether you just want one view of everything. For most people, the second is what they were really after.
Three real ways to bridge the two
Below are the honest options, from the most manual to the one that sidesteps the problem entirely.
Per-app sync through each platform
Many fitness apps (your running tracker, your scale app, your sleep app) can write to both Apple Health and Health Connect. If the app you already use supports both, grant it permission on each device and it becomes the bridge for its own data. The catch: each app only carries the metrics it owns, so a step app moves steps but not your sleep or heart rate.
A third-party bridge app
A handful of utility apps exist to read from one platform and write to the other. They work, but they add a moving part you have to trust with your full health record, they often run on only one of your two phones, and they can silently stop syncing after an OS update. Treat them as a stopgap, not a foundation.
Connect both to one service that reads each side
Instead of forcing Apple Health and Health Connect to mirror each other, connect each one to a single service that reads both independently. Your iPhone shares Apple Health, your Android phone shares Health Connect, and the service stitches them into one history. Nothing has to be copied from platform to platform, so nothing breaks when an OS updates.
The first two paths try to make one phone hold everything. The third accepts that your data is split across devices and unifies it one level up, where a coach can actually use it. That is the approach Wellness Project takes.
Why the third path is usually the right one
Mirroring two platforms into each other is fragile by design. Every bridge depends on permissions that reset, background limits that kill long-running syncs, and APIs that change. You end up babysitting the pipe instead of using your data.
The reason most people want Google Health in Apple Health in the first place is not the file itself. It is that they want one place that sees the whole picture: the steps from the Android phone in their pocket, the workout from the Apple Watch on their wrist, the sleep from the ring on their finger. Unify at the coach layer and that whole picture exists without a single platform-to-platform copy.
How to set it up
On iPhone, open the app and grant Apple Health permission so it can read steps, workouts, sleep, heart rate, and HRV. On Android, grant the same permissions through Health Connect. If you also use Fitbit or Oura, connect each one from your account settings with a normal OAuth sign-in. From then on, every device writes into the same history, and your coach reads all of it together.
You do not have to pick a single phone or abandon a wearable. The point is to stop fighting the platform divide and let one coach see across it.
Stop mirroring platforms. Unify them.
Connect Apple Health, Health Connect, Fitbit, and Oura to one AI coach that reads your whole history. Free during early access.