How to Export Your Data From Nara Baby (CSV, Step by Step)
Nara Baby has two Export Data buttons that don't export the same profile. Where the CSV lives, which route exports your child's data, what's inside.

Nara Baby can export data as a CSV file from inside the app. The catch is that there are two Export Data buttons in two different places, and they don't export the same thing — one exports the child you picked, the other exports whichever profile happens to be active. Tap the wrong one and the file that lands looks empty, which makes it easy to conclude the export is broken, or that there isn't one.
This is a practical how-to, written at the time of writing (August 2026) — Nara can change its app, so if a screen looks different, the export is still likely in one of the same two places.
There are two Export Data buttons
| Where it lives | What comes out | |
|---|---|---|
| Route A — start from the child | Account → Family → tap the child → scroll down to Export Data | That child's profile |
| Route B — start from the Activity avatar | Activity → tap the profile avatar at the top → Export Data | Whichever profile is currently selected, which may be your own postpartum profile |
Both give you a CSV. The difference is whose data ends up inside it — and only one of the two routes appears in Nara's own FAQ, which is the one that can go wrong.
Export a child's data — the reliable route
Route A starts from the child, so it can't hand you the wrong profile:
- Open Account.
- Go to Family.
- Under Children, tap the child whose history you want.
- Scroll to the bottom of that child's screen.
- Tap Export Data.
The file arrives named after the profile and the date — something like export_narababy_<child>_<date>.csv. If you have more than one child, repeat the steps for each: one export is one profile.
The profile trap — why the documented route can give you the wrong file
Nara's own Tracker FAQ describes exactly one way to export, and it's Route B:
If you would like a copy of the data for a child in CSV (Excel spreadsheet) format, go to the main Activity screen and tap the avatar icon next to the child's name. Then tap Export Data.
The wording promises the data for a child. The problem is that the avatar at the top of the Activity tab is also Nara's profile switcher: Nara can track a parent's own postpartum profile alongside each child's profile, and the same avatar is how you move between them. The Export Data button underneath it follows whichever profile is selected at that moment — not, despite the wording, the child.
So if your own postpartum profile is the one that's active, Route B quietly hands you a CSV of your own tracking, with none of your baby's entries in it. Open the file, see nothing you recognise, and the obvious conclusion is that the export doesn't work — or that the app can't export at all. It can. You were pointed at the wrong profile.
Two ways to avoid it:
- Check the name at the top of the Activity tab before you tap Export Data. If it isn't the child's name, switch profiles first.
- Or skip the question entirely and use Route A, which starts from the child and never depends on what's currently selected.
Either way, open the CSV afterwards and confirm the profile name and the date range match the child you meant to export. It takes ten seconds and it's the difference between having your history and thinking you do.
What's in the CSV
It's a standard CSV you can open in Numbers, Excel, or Google Sheets. It's laid out as one long table rather than one sheet per activity:
- A
Typecolumn says what each row is. - Fields that belong to a particular activity are namespaced into their own columns, written as
[Type] Field name. - Shared columns carry the context every row needs:
Profile Name,Start Date/time,Start Date/time (Epoch),Created By Caregiver,Last Updated By Caregiver,NoteandTime Zone. - A few internal identifier columns (
_familyKey,_profileKey,_activityKey) come along for the ride.
The header row isn't fixed. Nara writes columns only for the types that actually appear in that particular export, so two exports from the same family can have different headers and a different number of columns — we saw one file with 8 columns and another with 16. Which field names show up under each type therefore depends on what you've logged, so read your own header row rather than assuming a layout. If you're scripting anything against the file, key off the Type column and the [Type] prefixes instead of column positions.
Two columns are more useful than they first look. Created By Caregiver and Last Updated By Caregiver preserve who logged what, which matters if two people have been sharing the tracking. And a per-row Time Zone means a holiday or a move doesn't silently shift your timestamps when you read the file somewhere else.
Before you rely on the export, open it and check two things: which profile the rows belong to, and what date range they actually span. That tells you what you're holding while you can still go back and export again.
Is there a Nara Baby API?
No. There's no public Nara Baby API — neither the official FAQ nor the terms page offers developer access or documented endpoints, so there's no supported way to pull your tracking out programmatically.
The CSV export above is the official way to get your data out, and it's the one worth building on. There are unofficial workarounds in circulation that read the app's database out of an Android emulator; we don't recommend them. They're fragile, they depend on app internals that can change without warning, and they mean handing your baby's health data to a tool nobody has audited — for a file you can get in five taps.
Common reasons to export
- Switching to another tracker, and wanting the history to come with you rather than starting from an empty screen.
- Keeping your own backup, independent of any one app or account.
- Sharing with a professional — a doctor, nurse, paediatrician or lactation consultant who'd rather see the actual pattern than a summary from memory.
Moving your history to BabyLog
If BabyLog is where you're heading, that CSV can come across with you, and you don't have to work out the column mapping by hand. CSV import and export are both free in BabyLog, and because every tracker exports a different shape, the Data page gives you a ready-made AI prompt: paste it into ChatGPT or Claude along with your file, let the AI reshape the columns into BabyLog's format, then import the result.

The import and export guide walks through the whole thing — what the import expects, how to use that prompt, and what happens to duplicates. It's a public page, so you can read it end to end before you sign up for anything.
Export first, decide second. Once that CSV is on your phone the history is yours either way — you can sit on it, hand it to a doctor, or bring it into a new tracker whenever you're ready. It's far easier to grab the file in five taps today than to reinstall Nara in six months because you want the newborn weeks back.
If you're still weighing the two apps up, the BabyLog and Nara Baby comparison covers day-to-day logging effort, sharing and offline use. Coming from a different app instead? There's a matching walkthrough for exporting your Huckleberry data.
Ready to start tracking?
BabyLog works on any device — iPhone, Android, tablet, or desktop. Setup takes two minutes.
Keep reading

BabyLog vs Nara Baby: Calm and Minimal vs Calm and Operational
A fair side-by-side comparison of BabyLog and Nara Baby — daily logging effort, reviewing the day, caregiver sharing, offline use, data export and multilingual support — for parenting in Australia, when you want a calm baby tracker.

Huckleberry vs Nara Baby: An Honest Comparison (2026)
Huckleberry and Nara Baby compared on everyday logging, navigation, sleep support, free features and price — and which one we'd actually pick.