> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getbased.health/llms.txt
> Use this file to discover all available pages before exploring further.

# Export and import your data in getbased

> Download your health data as JSON or PDF, import it on any device, and migrate between profiles — no AI provider needed for any import.

getbased gives you full control over your data. You can export everything as JSON at any time, import it on a new device or browser, create a password-protected profile share link, and share structured exports with a healthcare provider as a PDF report. No account or AI provider is needed to import data.

## Export your data as JSON

A JSON export contains the current profile's portable health record: all lab entries, reviewed meal records and small thumbnails, nutrition targets, context cards, notes, structured supplement and medication records, biometrics, genetics, cycle data, custom markers, and marker category placements. Full-size meal photos are not saved and therefore cannot be exported. Chat is included only when you choose **Export with Chat** or export the full database bundle.

### Single-profile export

<Steps>
  <Step title="Open data settings">
    Open **Settings → Data**.
  </Step>

  <Step title="Export">
    Click **Export JSON**. A `.json` file downloads to your device immediately.
  </Step>
</Steps>

### What the export includes

* All lab entries — every date, every marker, every value
* All 9 lifestyle context cards (diet, sleep, exercise, environment, and more)
* Notes, health goals, and context card change history
* Complete supplement and medication records, including lifecycle periods, schedules, product ingredients, quality evidence, and reviewed-import provenance
* Reviewed meal records, nutrient values, targets, response check-ins, and small thumbnails
* Biometrics — height, weight history, blood pressure history, pulse history. Height is stored in cm and weight in kg; your display-unit preference controls how the app shows them after import.
* Menstrual cycle data (if entered)
* Genetics data — SNP results from DNA raw data import (if imported)
* Custom marker definitions
* Per-profile marker category placements and display customizations
* Chat history, conversation threads, custom personas, and persona deletion records when **Export with Chat** is selected
* Interpretive lens settings
* Saved Biology Score summaries, explanations and comparison variants, plus reviewed context state

### Export a single client profile

Open the profile switcher from the header, then click the three-dot menu (⋮) next to any profile. Choose **Export** for health/profile data or **Export with Chat** to add sent threads and custom-persona state. Both create a standalone file for that profile.

## Share one profile with a link

If you want someone to load one profile without handling a JSON file, use **Share Profile**. getbased creates a temporary password-protected link for the selected profile. Send the link and password separately, and stop sharing when the other person has imported it.

See [Profile sharing](/guides/profile-sharing) for the full workflow and privacy details.

### Export all profiles (database bundle)

To back up everything across all profiles at once:

<Steps>
  <Step title="Open the profile switcher">
    Open the profile switcher from the header.
  </Step>

  <Step title="Export all">
    Click **Export All** in the header. Or go to **Settings → Data → Export All Clients**.
  </Step>
</Steps>

A database bundle downloads containing every profile's complete stored data, chat history, threads, custom personas, and settings. This includes device-local AI model-test history that is not present in a curated single-profile export. Unsent chat drafts are intentionally excluded. Use the bundle for a complete backup or when migrating your entire getbased setup to a new browser or device.

<Tip>
  Export a JSON backup before doing a large batch import or clearing data — it's your safety net if something doesn't go as expected.
</Tip>

## Import a JSON file

You import a JSON file the same way you import a lab PDF: use the header import button or drop it onto the app. No AI provider is needed.

<Steps>
  <Step title="Open getbased on the target device or browser">
    Navigate to `app.getbased.health` (or your self-hosted URL) and open the profile where you want to import.
  </Step>

  <Step title="Drop or select the file">
    Drag and drop your `.json` export file onto the app, or use the header import button. getbased detects JSON files automatically.
  </Step>

  <Step title="Review the merge">
    getbased merges the imported data into your current profile:

    * **Lab entries** are merged by date — values for the same date are combined, not overwritten.
    * **Notes** are deduplicated — the same note will not appear twice.
    * **Context cards** are overwritten by the imported values.
    * **Health goals** are merged and deduplicated by text content.
    * **Supplements and medications** are deduplicated by name and first start date.
    * **Meals** merge by stable meal ID and update time; deletion tombstones prevent an older copy from reviving a deleted meal.
    * **Sent conversations** with new IDs are added without deleting existing ones, up to 50 conversations in the destination profile. Use **Export All** and import the database bundle when migrating a larger chat archive.
    * **Custom personas** are restored when the destination does not already have custom-persona state.
    * **Marker category placements** are merged with the profile and continue to point to the same markers; no lab values are re-keyed or moved.
  </Step>
</Steps>

<Warning>
  If you import a JSON file from a different profile or device, the lifestyle context cards in your current profile will be overwritten by the imported values. Your lab entry data is safe — it merges rather than overwrites.
</Warning>

Older exports that do not contain marker placements remain compatible. Their markers simply appear in their original categories until you organize them in the current profile; no migration or re-import is required.

<Note>
  For a full-fidelity restore of structured supplement and medication product facts, schedules, quality evidence, and import provenance, use an **Export All** database bundle or folder backup. The curated single-profile compatibility importer deduplicates therapies by name and first start date but currently restores only the legacy core fields, ingredients, multi-period history, note, and safe source URL.
</Note>

### Import a database bundle

Drop a database bundle exported with **Export All** onto the app, or select it with the header import button. getbased detects it automatically and handles multi-profile merging:

* New profiles are created
* Existing profiles are merged (lab entries by date, notes deduplicated)
* Structured supplement and medication records are carried over without flattening product facts, quality evidence, or lifecycle periods
* Reviewed meals, thumbnails, nutrition targets, and their deletion state are carried over
* Chat threads, custom personas, and their deletion records are carried over

## Export a PDF health report

The report builder offers **Health summary**, **Full health report**, **Nutrition and lifestyle**, and **Lab results only** templates. Choose the date window, sections, lab categories, report-specific ranges, context, notes and Genome findings. Start with a concise summary or add selected detailed records as an appendix.

**Include AI overview** starts selected when a compatible AI connection is available. The button clearly indicates when previewing will generate an overview. Turn it off to build the preview without a new AI request. Required approvals appear before AI processing, and generated text remains labeled and editable.

See [Create a health report](/guides/health-reports) for the full workflow, range meanings and sharing controls.

## Common use cases

| Use case | Recommended approach |
| - | - |
| Regular backup | [Folder backup](/guides/backup) (automatic) or JSON export (manual) |
| Move to a new device | Export database bundle → import on new device, or use [cross-device sync](/guides/cross-device-sync) |
| Share one profile temporarily | [Profile sharing](/guides/profile-sharing) |
| Share with a healthcare provider | PDF report export |
| Migrate to a new browser | Export database bundle → import in the new browser |
| Restore after an accidental change | [Restore from an automatic snapshot](/guides/backup#restore-from-a-snapshot) |

## Transfer to a new device or browser

<Steps>
  <Step title="Export on the old device">
    Export a JSON database bundle from the profile switcher or **Settings → Data → Export All Clients**.
  </Step>

  <Step title="Open getbased on the new device">
    Navigate to `app.getbased.health` in any browser on the new device.
  </Step>

  <Step title="Import">
    Drop the bundle file onto the app or use the header import button. Your historical labs, reviewed meals, charts, context cards, and settings are restored. Reconnect device-local wearable OAuth providers separately.
  </Step>
</Steps>

<Note>
  Cross-device sync via your 24-word mnemonic is an alternative to manual export and import. Sync keeps devices in continuous sync without requiring you to export and transfer files. See [Sync across devices](/guides/cross-device-sync).
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.