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 — profile height, weight, blood pressure, pulse, and supported explicit manual body readings, including method-specific waist/hip and abdominal-depth history. Canonical values and display units remain distinct; raw wearable daily rows are not portable client data.
- 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 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.
Choose the right file
Restore Backup recognizes both full backups and current multi-client exports. For a client export it asks to merge clients without replacing app settings; for a full backup it asks to restore the backed-up state. Cancelling the confirmation leaves it unapplied.
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
A current single-client export with profile metadata creates a profile for that client. Older files without that metadata can merge into the active profile. Check the destination; relevant merge rules include:
- Lab entries are merged by date; a conflicting imported result for the same marker/date can replace its saved value.
- 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 retain their structured records. Matching IDs with different contents prompt Keep saved or Use imported; choosing the imported record can replace its dose history and omitted fields. Other data can still import if you keep the saved regimen.
- 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.
Supported single-client and multi-client imports preserve structured supplement and medication product facts, schedules, quality evidence, periods, and import provenance. Conflicting matching records require a native keep/replace decision. Use Download Backup for app settings and backup-supported device-local stores, which client exports do not include.
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 for the full workflow, range meanings and sharing controls.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.