How to Back Up Apple Health Data Before Switching iPhones

Before switching iPhones, check that Health is enabled in iCloud, or make an encrypted computer backup if that is your transfer method. An ordinary unencrypted computer backup is insufficient for Health and Activity history. Then keep the old phone until you have checked meaningful examples on the new one. Apple's transfer guidance

An independent Health export adds a useful second kind of protection: a copy you can inspect and analyze outside your phone. But an XML or CSV file is not an Apple device backup, and you should not count on it as a native restore method.

Revised October 8, 2026: this guide follows current Apple backup and transfer documentation and distinguishes restoration from independent exports.

Decide what you want to preserve

There are two different goals. One is getting your existing Health history onto a replacement iPhone. The other is keeping a separate copy of measurements for future analysis, even if your software choices change.

Apple distinguishes iCloud synchronization from iCloud Backup: information already synchronized to iCloud is handled separately from the device data included in a backup. A recent device-backup timestamp is therefore not, by itself, your whole Health checklist. What iCloud backs up

1. Make a small inventory before the move

Pick several records you would notice losing. Write down dates rather than relying on a general impression of the charts:

• One recent workout and one workout from an earlier year.
• A week of sleep you recognize.
• A historical weight or other measurement you care about.
• A recent day of Activity rings, if you use them.
• An older period near the beginning of your recorded history.

This is a spot check, not proof that every record survived. Its value is making the comparison concrete. An app can show today's steps while a year of older history is still absent.

Also note which apps supplied the records. If an important measurement exists only inside a device maker's app, confirm that it is actually visible in Apple Health. A Health transfer cannot be assumed to preserve information that never reached Health in the first place.

Keep this inventory private. A few dates and descriptions are enough; there is no need to send screenshots of your full medical history to anyone.

2. Check Health in iCloud

On the old iPhone, open Settings → your name → iCloud, find Health in the saved-app list, and check that syncing is enabled. Apple changes the list's labels across releases; look for Health and its sync control rather than a particular wording of “Show All.” Devices syncing this information need the same Apple Account and an internet connection. Apple's Health backup guide

Do this before the handover, while you still have time to resolve an account or connection problem. If you are changing Apple Accounts as well as phones, do not treat that as the same procedure: the documented same-account sync path does not establish that history transfers between accounts.

Health data has specific protections in iCloud. Apple says that with iOS 12 or later and two-factor authentication enabled, it cannot read synced Health and Activity information. An exported file you save elsewhere does not automatically retain those protections. Apple's Health privacy explanation

3. Make an encrypted computer backup if you want a local restore path

Connect the iPhone to your computer and select it in Finder on a Mac, or Apple Devices on Windows. Choose Encrypt local backup, create and securely save its password, and complete the backup. If you use iTunes on an older supported setup, Apple documents that path too.

Check the completed backup's date and encryption indicator in the backup list. Merely enabling encryption is not evidence that the backup finished. You need the password to use the encrypted backup; resetting a forgotten password does not unlock older backups. Apple's encrypted-backup instructions

Store the password somewhere you can reach even if the old phone is unavailable. A password recorded only in an inaccessible app on the phone you just erased is a poor recovery plan.

For an especially important migration, leave time between making the backup and trading in the phone. That gives you room to discover a failed backup or a missing password while the original still exists.

4. Save an independent Health export

In Health, tap your profile picture and choose Export All Health Data. Apple's export uses XML, a structured text format intended for other software to read. Save the resulting archive somewhere you control. Apple's export instructions

Give the saved file a date and leave the original archive intact. Work from a copy when converting it. Open the archive to confirm it can be read, then inspect whether it contains the kinds of records and historical dates you expected. A large file size alone says little about completeness.

For spreadsheet work, PulsHealth can instead export selected types and dates as CSV or JSONL directly on the phone. It requires no database for that operation. Check the export's completion status and accompanying manifest, including any reported history limitations. Those details are described in the export reference.

An export is sensitive. It can include source names, timestamps, and information that reveals routines. Keep it in protected storage, and do not upload the entire archive to a converter simply because the website accepts a ZIP file.

Can you import the export back into Apple Health?

Do not plan a phone migration around that assumption. Apple's documented export is a sharing mechanism; its device migration instructions use the Apple transfer, sync, and backup workflows. A third-party importer is a separate product with its own supported types and behavior. It is not evidence that the full archive can be restored with its original meaning.

Use the export for independent access and analysis. Use Apple's supported migration path for the new phone.

5. Check the new phone before erasing the old one

Complete your chosen Apple setup process, then revisit the inventory from step one. Compare the same dates and records on both phones, rather than comparing two charts with different date ranges.

If you have an Apple Watch, follow Apple's pairing instructions for the new iPhone. The guide covers the Health settings to check, the old iPhone backup, and the Watch setup sequence. Follow its troubleshooting path if the Watch does not transfer as expected. Pair an Apple Watch with a new iPhone

Give synchronization time, but do not turn waiting into an assumption of success. If old records remain missing, retain the original phone, record exactly what is absent, and check the account, Health sync setting, and backup method before attempting destructive resets.

Once the historical checks look right, confirm that new measurements appear too. Restored history and ongoing collection are separate things worth verifying.

If you also use PulsHealth

A synced PulsHealth database is useful for checking historical coverage outside the phone. Compare earliest and latest dates for the types that matter, and inspect whether a dataset contains raw samples or only aggregate values. “Connected” does not mean every type and every year has been uploaded.

That database also needs protection. The self-hosted stack's backup service is opt-in; a running Postgres volume is not a separate backup. Follow the backend's backup instructions and test recovery on a scratch stack. Never run a destructive restore drill against your only live database. Backend and backup documentation

After moving phones, reconnect PulsHealth and verify a new record reaches the intended account. Its device-specific connection state should not be assumed to travel with the phone backup. The privacy policy explains what is stored on-device and excluded from backups.

The point at which to erase the old phone is after you have a usable recovery path, recognizable historical records on the new phone, and evidence that new data is arriving. A completed setup screen is only the beginning of that check.