Skip to main content
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

1

Open data settings

Open Settings → Data.
2

Export

Click Export JSON. A .json file downloads to your device immediately.

​
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

​
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. 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 for the full workflow and privacy details.

​
Export all profiles (database bundle)

To back up everything across all profiles at once:
1

Open the profile switcher

Open the profile switcher from the header.
2

Export all

Click Export All in the header. Or go to Settings → Data → Export All Clients.
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.
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.

​
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.
1

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.
2

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.
3

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.
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.
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.
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.

​
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

1

Open the profile

Open the profile you want to export as a report.
2

Open the report builder

Use the PDF export control in the data tools. Choose Clinician, Full, or Personal as a starting template.
3

Choose dates and content

Select Current, 3 months, 6 months, 1 year, or All time. Choose at least one section and one lab category. Category controls show the live number of matching results and include All, Flagged, and Clear shortcuts.
4

Review the local preview

The browser builds the report preview locally. Review the patient details, selected results, display units, and section order before sharing it.
5

Add an optional practitioner overview

If you choose to generate a Practitioner overview, getbased sends only the currently selected report material to your active AI provider. Edit or remove the generated text before export.
6

Print or save

Use Print or Save PDF from the preview.
Available report sections include flagged results, category tables, a summary, trends, supplements and medications, notes, genetics, and context. The chosen template only sets an initial selection; you remain in control of the final content. The preview itself does not call an AI provider. Only the optional Practitioner overview action crosses that boundary, after normal cloud-provider consent where applicable. Height and weight are shown in the profile’s selected display units, while the canonical cm and kg values keep BMI calculations consistent. You can read the practitioner-overview instruction before generating it. The page shows fixed wording with placeholders where your selected report material is inserted.
The report is a snapshot of the sections, categories, and date range you selected. Review it against the source records before relying on it for a clinical conversation.

​
Common use cases

​
Transfer to a new device or browser

1

Export on the old device

Export a JSON database bundle from the profile switcher or Settings → Data → Export All Clients.
2

Open getbased on the new device

Navigate to app.getbased.health in any browser on the new device.
3

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.
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.