Editorial reference · Public Apple, Garmin and Oura documentation checked November 17, 2026
“You can export your data” is a weak answer to a strong question. The question is whether you can keep using the information that matters after you change a device, leave an app or stop paying for a service.
A successful download answers only the first part. It does not establish that another app can import the file, recognize its units, retain its detail or recreate the original charts.
Ask what leaves, what arrives and what survives the trip. That is a more useful standard for portability than the presence of an Export button.
We reviewed current public instructions from Apple, Garmin and Oura and separated export routes that are often discussed as if they were one feature. This is a documentation audit. We did not request anyone's private archive, inspect member records, perform an account migration or test an importer. Every route below remains untested by us.
An export is a route, not a brand-level promise
| Route | Documented output or scope | What it does not establish |
|---|---|---|
| Apple Health, Export All Health Data | Health and fitness data from Health in XML | That another app accepts the archive or that every device-specific field ever reached Health |
| Garmin Connect, activity-list Export CSV | Activity summary spreadsheet | That the spreadsheet contains the full detail of individual activity files |
| Garmin Connect, individual activity export | Original format, typically FIT; other options include TCX, GPX and splits CSV | That every format preserves identical fields |
| Garmin, account data export | Associated account data; activity FIT files are documented within the archive | That a new service can restore the whole account |
| Oura, Shareable Reports | Printable PDF summaries; report availability depends on generation and membership | That a PDF is a record-level migration file |
| Oura, Membership Hub export | Personal-data download available with or without active membership | Exact schema and import fidelity in an archive we have not opened |
Primary instructions: Apple's iOS 27 Health guide, Garmin's export reference, and Oura's export and sharing reference, updated October 14, 2026. The Garmin page was viewed with an Edge 520 support context; its described routes concern Garmin Connect.
A spreadsheet can be the wrong kind of detail
Suppose a hypothetical export has one row per workout: date, duration, distance and average heart rate. That can support useful monthly comparisons. It cannot reconstruct the sequence of heart-rate samples during each workout because those samples are not in the hypothetical file.
Changing the file extension does not recover them. Converting that summary CSV to JSON produces the same information in another syntax. It does not turn an average into a time series.
This is why the route distinctions matter. Garmin explicitly describes its activity-list CSV as a summary. A reader looking for individual activity records should inspect the individual-file route or the activity files in the account archive, then check what their intended destination accepts. The format name is a starting point, not a completeness certificate.
Our export worksheet therefore asks two separate questions: what resolution does the source provide, and what resolution does the destination retain? “Workout,” “daily summary” and “timestamped sample” should not share one unchecked box labeled data.
“All” has a boundary
Apple describes its XML export as covering health and fitness data from Health. That last phrase matters. It is not a statement that every proprietary field from every connected wearable has been transferred into Health.
Think of a hypothetical device that records a raw measurement and also displays its own derived readiness score. If the integration sends only the measurement, exporting the receiving system cannot recover the score from nowhere. This is an illustration of scope, not a claim about a particular device's current integration.
A useful migration inventory starts with the original service, the intermediate store and the destination. Write down which of those actually contains the field you care about. Do not assume that a familiar chart title proves the same underlying records exist in all three.
The same discipline applies to history. A connection that works today does not, by itself, prove that it transfers five years of prior records. Our review has not tested historical transfer limits for these routes, so the downloadable reference marks destination coverage and preserved history as unknown.
Old export advice can become wrong quietly
Oura's current instructions offer reports, an API route and a Membership Hub download. The Hub route is available without an active membership, and the page says a requested archive may take up to ten days. It also specifies seconds for downloaded duration values. Older cached descriptions we encountered emphasized a CSV export; the current page does not supply enough detail to certify the exact file inventory we would receive.
We have retained that uncertainty instead of turning an old search snippet into a fresh test result. To verify the current inventory, the next step is to request a consented test-account archive and inspect it. Until then, “documented download route” is the claim we can support.
This is a good general rule for portability guides: date the route, state the source, distinguish a visible instruction from an observed export, and identify the next missing check. A list that erases those distinctions can look more decisive while being less useful.
What a real portability check should record
We built a blank audit sheet around a specific question: could someone independently verify the transfer without trusting a screenshot of a success message?
Start with the source platform, route, request date and software version. Record the archive's file names, formats, earliest and latest timestamps, time zone conventions, units and record counts by type. Keep the original archive unchanged and make a separate working copy for any conversions. Store health exports privately; a public converter is not a necessary step in this process.
Then select a few records you can recognize in the source: a particular workout, a particular night, a day with two sessions. After an authorized import, compare identities, timestamps, durations and fields in the destination. Check whether repeated import creates duplicates and whether summaries have replaced finer detail. Those are proposed checks, not results we obtained.
Even an exact record count is insufficient by itself. Two files can have 100 rows each while containing different days. One imported workout can appear twice under different identifiers. A total distance can match while the underlying timestamps shift. The audit sheet includes space for matched examples and unresolved discrepancies because a single aggregate can conceal them.
Keep an archive; prove a migration
Download the dated route reference, JSON with evidence levels and unknowns, and blank portability audit sheet. All six route records are marked documentation-only and import-untested. We do not supply a fictitious successful migration.
Our editorial recommendation is to retain the original account and archive until the transfer you actually need has been verified. A readable report, a recoverable archive and a successful migration are three useful achievements. Calling all three “export support” makes it harder to know which one you have.
Vora brings wearable context together with workouts, nutrition and existing proactive AI. That does not mean it imports every file listed here or recreates another manufacturer's scores. Check the current integration information for supported connections, and use this reference to ask precise questions of any health app, including ours.