On this page
An export button is useful only if the resulting file contains the information you need and can be used where you need it. A health app may offer a machine-readable archive, a selected report, or a sharing connection. Those options serve different purposes.
Before changing phones, closing an account, or moving to another service, define what continuity means for you. You may want a personal archive, a readable summary for a conversation, or data that another application can import. One file may not satisfy all three needs. Keep the original service available until the required checks are complete.
Choose the purpose before the file format
A personal archive aims to preserve information for later use. A report aims to communicate selected information in a readable form. An import aims to create usable records inside a destination application. These are separate outcomes, even when they begin with the same source data.
For example, a large XML archive may be appropriate for structured storage but inconvenient for a clinician expecting a short report. A PDF may be easy to read but unsuitable for importing individual observations. A sharing feature may provide current access without creating a permanent copy under your control.
Ask the intended recipient what they can accept and what they actually need. Do not send a complete health archive when a selected date range or summary would answer the question.
Inventory the information you rely on
List the categories that matter: activity records, manually entered notes, device measurements, medication lists, or documents from another service. Record which application or device supplied them and whether the information is stored locally, synchronized, or accessed through a connection.
An app showing a category does not prove that every item in that category is included in its export. Review the provider's documentation and the export options. Some information may be represented differently, excluded, or retained by a connected service that has its own export process.
Keep clinical records and consumer app observations distinct. A wearable estimate or manually entered note does not become a professionally verified medical record because it appears in the same archive as other information.
Make a sample export before the deadline
Use the provider's supported process and save the result in an appropriate private location. Note the export date, chosen date range, application version where useful, and any selected categories. Preserve the original downloaded archive before experimenting with copies.
Apple Health, for example, supports exporting health and fitness information in XML. That establishes an available format, not a guarantee that another product can reconstruct the same views or meaning from it. Check the destination's explicit import support.
If the file is compressed, use trusted software to inspect it. Avoid uploading an entire archive to an unfamiliar online converter merely because the file is difficult to open. A format problem should not become an unnecessary disclosure of health information.
Inspect coverage and meaning
Choose several records you can recognize in the original app. Include a recent entry, an older entry, and an item from each important source. Compare the exported representation with the original while you still have access.
Look beyond whether a value exists. Dates, time zones, units, source names, and manually entered versus device-generated origins can affect interpretation. A number without its unit or time context may be misleading. A missing interval should remain a gap rather than being silently filled.
| Check | Example question | Why it matters |
|---|---|---|
| Coverage | Are the required dates and categories present? | A successful download can still be incomplete for your purpose |
| Units | Is the value's unit preserved? | Similar-looking numbers can represent different quantities |
| Time | Is the time zone or date convention clear? | Travel or device settings can complicate comparisons |
| Origin | Can you identify the app, device, or manual entry? | Different sources may measure or estimate differently |
| Corrections | Are revised or deleted entries represented clearly? | An archive may not resemble the current on-screen view |
| Readability | Can the intended recipient use the format? | Storage and communication are different tasks |
These checks establish whether the export serves your purpose. They do not validate the clinical accuracy of every observation.
Test importing without risking the only copy
If another app supports importing the format, read how it handles duplicates, unsupported categories, and repeated imports. Where the provider offers a safe preview or test process, use it. Keep the source archive unchanged so you can return to it if the result is confusing.
Do not assume that a completed import means every record was accepted. Compare the destination's counts, date range, and representative entries. Review any skipped-item report. Some applications may convert units or summarize records; understand the transformation before comparing charts.
Be careful with repeated attempts. Importing the same archive twice may create duplicates in some systems. Ask the provider how to recognize and reverse a mistaken import rather than deleting records indiscriminately.
Keep a readable summary separate from raw data
For a conversation with a health professional, ask what information would be useful. A concise summary can state the question, date range, source device, and known gaps, with the relevant report attached through an accepted channel.
Avoid interpreting a trend as a diagnosis. If a chart concerns you, describe the observation and ask what assessment is appropriate. A consumer app's display or export is not a substitute for clinical context.
For medication information, distinguish the current list, the planned schedule, and records of actual use. The medication reminder guide explains why these cannot be treated as identical merely because an app groups them together.
Protect the exported copy as a new data location
Once exported, the file may no longer be governed by the app's usual access controls. Consider the folder, backup, sharing link, recipient, and devices that can access it. A link that is easy to forward may reach more people than intended.
Use the minimum necessary sharing scope and an appropriate transfer method. Confirm the recipient before sending. Keep account credentials and recovery codes out of accompanying notes. If another person is helping, agree what they are allowed to access and what happens to working copies afterward.
The shared care calendar guide applies the same principle to coordination: share what the task requires, with permission, while keeping unnecessary details private.
Close the old service only after the handover works
Before deleting an account or surrendering a device, confirm that the required archive exists, a sample can be opened, any intended import is usable, and you understand what remains unavailable. Keep an appropriate independent copy if that fits your needs and the service's terms.
Account closure, revoking sharing, and deleting a local application are different actions. Read the provider's current explanation of each. Removing an icon may not delete cloud data, and deleting an account may remove access needed to resolve an incomplete export.
When changing devices, use the phone transfer checklist alongside this health-specific review. The successful outcome is a record whose purpose, coverage, and limits you can explain, with access preserved where it is still needed.
Sources and further reading
Primary and contextual sources used to verify definitions or give readers a relevant next resource.
- Apple: Share data in Health Health can export health and fitness data in XML, while sharing features have their own supported workflows.
- Apple: Health app and privacy Health data permissions and sharing arrangements should be reviewed for the specific feature and recipient.