When you request a data export for a child in Famly, you'll receive a ZIP file containing CSV files and a media/ folder with photos, videos, and documents. This article explains what each file contains so you can find and understand the information you need.
Before You Open the Files
A few things to know upfront:
Each CSV file covers one area of Famly — attendance, observations, finance, and so on. The filename tells you what's inside.
Files are numbered (e.g. 017famly_daycare_child...). The number is just the export order; it doesn't have any meaning. What matters is the name after the number.
💡 File numbers won't always be the same; the same file may have a different number in a different child's export, or in a later export for the same child
Empty files are normal. If a feature hasn't been used for a child, the file will still appear but with no data rows, just column headers.
Deleted records are included. Records removed from Famly's interface still appear in the export. Look for columns called deletedAt, deletedat, or active to identify them.
ID columns are internal references. Long strings of letters and numbers (UUIDs) are used to link records between files; they're not meant to be human-readable.
*By columns contain login IDs, not names. Columns like createdBy or deletedBy store an internal ID for the person who made a change, not their actual name.
Money columns are in your currency, not pence or cents.
Two files contain sensitive personal data in plain text. See the callout boxes in the Profile and identity section.
What's in the Export
The files are grouped below by area. Jump to the section you need:
Profile and Identity
These files contain the child's core information and their connected family members.
Child profile
File: famly_daycare_child_domain_model_child.csv
The most important file in the export. Everything else links back to the childId found here.
Column | What it means |
childId | The child's unique ID in Famly |
siteId | Which nursery they're enrolled at |
groupId | Which room or group they're currently in |
firstname / middlename / lastname | Their name |
birthday | Date of birth |
street / zip / city | Home address |
language | Language(s) spoken at home |
gender | Gender (stored as a number) |
nationality / birthplace | Nationality and place of birth |
startdate | When they started at the nursery |
enddate | When they left (blank if still enrolled) |
status | Enrolment status — 1 = active |
leavingReason | Freeform note on why they left |
extrainfo | Any additional notes on the profile |
Any email on the profile | |
loginId | Their Famly login (usually blank for children) |
isTestChild | Whether this is a demo/test profile |
createdtime / lastUpdatedAt | When the profile was created and last updated |
Reason for leaving
File: child_reason_for_leaving.csv
The structured leaving reason selected from your nursery's configured options — separate from the freeform leavingReason note on the main profile.
Column | What it means |
childReasonForLeavingId | Unique ID |
childId | Which child |
reasonForLeavingId | Which reason was selected |
createdAt / deletedAt / lastUpdatedAt | Timestamps |
Family members and contacts
File: famly_daycare_child_domain_model_relation.csv
Parents, guardians, emergency contacts, and anyone else connected to the child in Famly.
Column | What it means |
relationId | Unique ID for this contact |
childId | Which child they're connected to |
loginId | Their Famly account ID (if they have app access) |
salutation | Title (Mr, Mrs, etc.) |
firstname / middlename / lastname | Their name |
street / zip / city / state / country | Their address |
Their email | |
phone / workphone / homephone | Contact numbers |
placeofwork / occupation | Employer and job title |
extrainfo | Additional notes |
status | Their relationship to the child — e.g. "Mum", "Grandpa" |
childcustody | Whether they have legal custody |
childlivesat | Whether the child lives at their address |
emergencyContact | Whether they're listed as an emergency contact |
hidefromphonelist | Whether to hide their number from the nursery phone list |
protectedaddress | Whether their address is flagged as sensitive |
priority | Display order |
createdtime / updatedat / deletedAt | Timestamps |
Profile photos
File: famly_core_image_domain_model_profileimage.csv
Metadata for the profile photos of family members. The actual image files are in media/profile-images/.
Column | What it means |
imageId | Unique ID (matches the filename in media/profile-images/) |
imagefor | What the photo is for |
id | ID of the person the photo belongs to |
objecturloriginal | Storage URL of the photo |
active | Whether it's the current active photo |
createdtime / deletedat | Timestamps |
Access and roles
File: famly_security2_domain_model_roleassignment.csv
Which access roles have been granted to each person in relation to this child — for example, a parent being given access to the child's profile in the app.
Column | What it means |
roleAssignmentId | Unique ID |
loginId | Who was granted access |
roleId | Which role |
targetid | What the role applies to (usually the child's ID) |
logincreatedaspartofassignment | Whether their Famly login was created at the same time |
createdat / deletedat / lastUpdatedAt | Timestamps |
createdby / deletedby | Who made the changes |
Sensitive identity information
File: famly_securestore_domain_model_entry.csv
‼️ This file may contain national ID numbers or Social Security numbers in plain text. Handle it carefully and in line with your data protection obligations.
Stores sensitive identity data for both the child and their family members. Rows for the child have targettype = Famly.Daycare:Child; rows for family members have targettype = Famly.Daycare:Relation.
Column | What it means |
entryid | Unique ID |
targettype | Whether this belongs to the child or a family member |
targetid | The ID of the child or family member |
entrykey | What kind of information — e.g. SSN |
value | The stored value (e.g. the national ID number) |
createdat / deletedat / lastUpdatedAt | Timestamps |
Collection passwords
File: child_collection_passwords.csv
‼️ Collection passwords are exported in plain text. Handle this file carefully.
The password or PIN required to verify who is authorised to collect the child.
Column | What it means |
collectionPasswordId | Unique ID |
childId | Which child |
collectionPassword | The password or PIN |
active | Whether it's currently active |
createdAt / createdBy | When and who set it up |
deletedAt / deletedBy | If removed |
lastUpdatedAt / lastUpdatedBy | When and who last changed it |
Key worker
File: famly_daycare_child_domain_model_keyworkerrelation.csv
Which staff member is the child's key worker, and for what period.
Column | What it means |
keyWorkerRelationId | Unique ID |
childId | Which child |
employeeId | Which staff member |
status | Whether this is their primary key worker |
validFrom / validTo | The period they held this role |
createdAt / deletedAt / lastUpdatedAt | Timestamps |
Room moves
File: famly_daycare_child_domain_model_groupmove.csv
A log of every time the child moved from one room or group to another.
Column | What it means |
groupMoveId | Unique ID |
childId | Which child |
groupId | Which room they moved into |
date | When the move took effect |
createdAt | When it was recorded |
Care contracts
File: care_contract.csv
Care agreements and contracts signed for the child. The contract document itself is in media/files/.
Column | What it means |
careContractId | Unique ID |
childId | Which child |
fileId | The contract document |
contractName | The name of the contract |
digitallySignedAt | When signed digitally in Famly |
externallySignedAt | If signed outside Famly |
withdrawnAt / withdrawnBy / withdrawalNote | If withdrawn |
sentForSigningAt | When sent for signature |
childFullNameAtSigning | Child's name at the time of signing |
childBirthdayAtSigning | Child's date of birth at the time of signing |
createdAt / createdBy | When and who created it |
updatedAt / updatedBy | Last update |
deletedAt / deletedBy | If deleted |
Sibling links
File: sibling_links.csv
Links the child to any siblings — either other children in Famly, or free-text entries for children not in the system.
Column | What it means |
linkId | Unique ID |
childId | The child |
siblingChildId | The sibling's Famly ID (if they're also in Famly) |
fullName | The sibling's name (if not in Famly) |
birthDate | The sibling's date of birth |
startDate / endDate | When the sibling relationship was active |
createdBy / createdAt | Who added it and when |
deletedBy / deletedAt / lastUpdatedAt | Deletion and update timestamps |
Other profile files
These smaller files contain supporting profile data:
famly_daycare_tag_domain_model_tagassignment.csv — custom nursery tags applied to the child.
famly_core_image_domain_model_imagetag.csv — records which photos the child is tagged in.
child_record.csv — freeform name/value data recorded against the child.
auto_inc_child_ids.csv — the short sequential reference number assigned to the child within your nursery.
famly_daycare_child_domain_model_childcopy.csv — if the child's profile was copied between nursery sites.
foreign_data_mapping.csv — if the child's data is synced with an external system (e.g. a local authority portal), this maps Famly's IDs to the external system's IDs.
headcount_assignment.csv — links the child to headcount snapshots.
famly_api2_kiku_domain_model_kikuchild.csv — extension data for the Kiku integration (used in some markets).
test_child_completed_actions.csv — only relevant for demo/test profiles.
famly_security_domain_model_assignpasswordtoken.csv — this file will always be empty. Password setup tokens are never exported.
Attendance and Check-ins (Sign-ins)
Check-ins
File: famly_daycare_checkin_domain_model_childcheckin.csv
The full attendance log — every time the child was checked in and out of the nursery.
Column | What it means |
childCheckinId | Unique ID |
childId | Which child |
siteId | Which nursery |
groupId | Which room they were in |
checkintime | When they arrived |
checkouttime | When they left (blank if still checked in when recorded) |
pickuptime | Expected or recorded pickup time |
pickuprelationid | Which family member collected them |
checkinloginid / checkoutloginid | Who checked them in and out |
autocheckedout | Whether the system automatically checked them out |
gohomewithchildid | If they left with another child |
deletedat | If this record was deleted |
version | Internal version number |
Check-in history
File: famly_daycare_checkin_domain_model_childcheckinversion.csv
A full history of any edits made to check-in records — useful for audit purposes. Each row is a snapshot of what a check-in looked like before an edit was made. The columns match those in the check-in file above, plus childcheckinversionid (unique ID for this version snapshot) and createdat / createdby (when and who created this version).
Planned pickups
File: famly_daycare_checkin_domain_model_plannedcheckout.csv
Scheduled pickup windows — one-off or recurring. These drive the expected pickup time shown on check-in screens.
Column | What it means |
plannedCheckoutId | Unique ID |
child | The child |
title | The label shown on screen |
startdate / enddate | Start and end of the window |
recurring | Whether it repeats |
checkouttype | The type of planned pickup |
active | Whether it's currently active |
createdat | When it was created |
Cancelled pickups
File: famly_daycare_checkin_domain_model_cancelledcheckout.csv
A record of when a specific occurrence of a recurring planned pickup was cancelled.
Column | What it means |
cancelledCheckoutId | Unique ID |
plannedcheckout | Which planned pickup was cancelled |
on | The specific date that was cancelled |
createdat | When the cancellation was recorded |
active | Active flag |
Absences
File: famly_daycare_leave_domain_model_childleave.csv
Days the child was marked absent or on leave.
Column | What it means |
childLeaveId | Unique ID |
childId | Which child |
siteId | Which nursery |
day | The date of the absence |
leavetype | Type of absence — e.g. sick, holiday |
reason | Freeform reason (often blank) |
vacationId | Links to a holiday plan entry, if applicable |
groupId | The room for this leave |
active | Whether still active |
createdBy / deletedBy / updatedBy | Who made changes |
createdat / deletedat / updatedAt | Timestamps |
Status periods
File: famly_daycare_status_domain_model_statusregistration.csv
Periods during which the child is in a configured status — for example, on a settling-in visit or marked as unwell.
Column | What it means |
statusRegistrationId | Unique ID |
statusConfigId | Which status this is |
siteId | Which nursery |
childId | The child |
startedAt / startedBy | When and who started this status |
endedAt / endedBy | When and who ended it |
active | Whether still active |
createdAt / createdBy | When and who created the record |
deletedAt / deletedBy | If deleted |
Unexpected sign-ins
File: unexpected_child_signin_log.csv
Flags check-ins that happened outside the child's planned sessions — a safeguarding alert.
Column | What it means |
logId | Unique ID |
childName | The child's name at the time (snapshot) |
childId | Which child |
siteName | Which nursery (snapshot) |
siteId | The nursery's ID |
childCheckinId | The check-in that triggered this |
nextPlannedSessionTimestamp | When their next planned session was actually due |
createdAt | When the flag was created |
Other attendance files
checkin_statement_childcheckin.csv — links check-ins to sign-in statements or signatures. Columns: statementId, childCheckinId.
headcount_assignment.csv — links the child to headcount snapshots. Columns: headcountId, childId.
Daily Care Logs
Care activities
File: famly_action_domain_model_action.csv
Every care activity logged for the child — nappy changes, meals, sleep, and so on.
💡 Two columns are intentionally excluded from this file for security reasons (createdaccesstoken and deletedaccesstoken).
Column | What it means |
actionid | Unique ID |
recipient | Identifies the child this action is for |
occuredon | When it actually happened |
actiontype | The type of activity — e.g. DIAPERCHANGE, SLEEP, MEAL |
payload | The details in JSON format — e.g. {"diaperingType":"WET"} |
createdloginid | Who logged it |
deletedloginid | Who deleted it (if applicable) |
createdat / deletedat | Timestamps |
Sleep and naps
File: famly_daycare_sleep_domain_model_nap.csv
Sleep and nap times logged for the child.
Column | What it means |
napId | Unique ID |
childId | Which child |
siteId | Which nursery |
starttime / endtime | When the nap started and ended |
rest | Whether this was a rest rather than a full sleep |
createdBy | Who logged it |
deletedtime | If deleted |
Meals
File: famly_daycare_foodconsumption_domain_model_mealregistration.csv
The header record for each meal logged for the child. Individual food items are in the file below.
Column | What it means |
mealRegistrationId | Unique ID |
childId | Which child |
mealTypeId | Which meal — e.g. breakfast, lunch |
createdBy / lastUpdatedBy | Who logged and last edited it |
createdAt / deletedAt | Timestamps |
Meal items
File: famly_daycare_foodconsumption_domain_model_mealitem.csv
The individual food items within each meal registration.
Column | What it means |
mealItemId | Unique ID |
mealRegistrationId | Which meal this belongs to |
foodItemId | Which food item (links to your food catalogue) |
amount | How much the child had |
unit | Unit of measurement |
lastUpdatedAt | When last updated |
Meal planning
meal_plan_child.csv — links the child to a meal plan. Columns: mealPlanId, childId.
meal_bookings.csv — individual pre-booked meals. Columns: id, childId, mealTypeId, mealDate, selection, isLocked, createdAt, createdBy, deletedAt, deletedBy.
Observations and Learning
Observations
File: cd_observation.csv
The core record for each observation. The actual written content is in cd_observation_remark.csv.
Column | What it means |
observationId | Unique ID |
createdBy | Who wrote it |
status | Current status — e.g. SENT (shared with parents) or PENDING_REVIEW |
observationRemarkId | Links to the written text |
nextStepId | Links to any next steps |
variant | Who wrote it — e.g. REGULAR_OBSERVATION (staff) or PARENT_OBSERVATION (parent) |
version | Which assessment framework version was used |
siteId | Which nursery |
active | Whether still active |
createdAt / deletedAt | Timestamps |
Observation text
File: cd_observation_remark.csv
The actual written content of each observation and any "next steps." This file also includes the body text of draft assessments — so if you see entries you don't recognise as published observations, they may be assessments that were saved but not yet completed.
Column | What it means |
observationRemarkId | Unique ID (linked from cd_observation) for observations and assessments, including drafts |
body | The observation text in plain format |
richTextBody | The formatted version (HTML) |
date | The date the observation covers |
status | Status of the remark |
Learning areas
File: cd_observation_remark_area.csv
The learning areas and developmental goals tagged to an observation, with the assessment judgement for each.
Column | What it means |
observationRemarkId | Which observation remark |
areaId | Which learning area |
title | Full name of the area — e.g. "Understanding the world" |
abbr | Short code — e.g. "UW" |
refinement | Assessment judgement — e.g. Emerging, Developing, Secure |
note | Freeform note for this area |
ageBandSettingId | The age band used |
assessmentOptionSettingId | The assessment option selected |
Other observation files
cd_observation_remark_statement.csv — links observations to specific curriculum statements, including the statement text. Columns: observationRemarkId, statementId, refinement, body.
cd_observation_remark_custom_field.csv — values in custom assessment fields. Columns: observationRemarkId, customFieldId, value, label.
cd_observation_status.csv — a history of status changes for each observation. Columns: statusId, observationId, status, createdBy, createdAt.
cd_observation_assessment_settings.csv — links each observation to the assessment framework used. Columns: observationId, assessmentSettingsId.
cd_observation_child.csv — links observations to the child. Columns: observationId, childId.
cd_observation_image.csv — links photos to observations. Columns: observationId, imageId.
cd_observation_file.csv — links documents to observations. Columns: observationId, fileId.
Child Notes and Newsfeed
Child notes
File: child_note.csv
Staff-written notes on the child — including sensitive and safeguarding notes.
Column | What it means |
noteId | Unique ID |
childId | The child |
type | Note type or category |
body | The note text |
parentVisible | Whether parents can see it |
sensitive | Whether it's marked as sensitive |
safeguardingConcern | Whether it's flagged as a safeguarding concern |
publishedAt | When it became visible |
createdAt / createdBy | Who wrote it and when |
modifiedAt / modifiedBy | When and who last edited it |
deleted | Whether it's been soft-deleted |
child_note_file.csv — links notes to attached documents. Columns: noteId, fileId.
child_note_image.csv — links notes to attached photos. Columns: noteId, imageId.
News feed items
File: famly_feed_domain_model_feeditem.csv
Items in the Famly news feed — shared observations, event invites, notifications, and so on. The content lives in the referenced record; this file just lists what appeared in whose feed.
Column | What it means |
feedItemId | Unique ID |
originatorid | What the item is about — e.g. observation:<uuid> |
loginId | Whose feed it appears in |
seen | Whether the user has seen it |
createddate / expireddate / enableddate / deleteddate | Timestamps |
Feed comments
File: famly_feed_domain_model_comment.csv
Comments posted on news feed items.
Column | What it means |
commentId | Unique ID |
originatorid | Which feed item was commented on |
body | The comment text |
senderloginid | Who commented |
createddate / deleteddate | Timestamps |
Bookmarks
File: famly_feed_domain_model_bookmark.csv
Records of users saving a feed item.
Column | What it means |
bookmarkId | Unique ID |
loginId | Who bookmarked it |
feedItemId | Which item |
createdAt / deletedAt | Timestamps |
famly_feed_domain_model_feeditemrolefilter.csv — controls which audience a feed item is shown to. Columns: feedItemRoleFilterId, feedItemId, siteSetId.
Accident Reports
Accident reports
File: famly_daycare_accident_domain_model_accidentreport.csv
Full accident and incident reports for the child.
Column | What it means |
reportId | Unique ID |
childId | Which child |
siteId | Which nursery |
kind | Type of report — e.g. ACCIDENT |
date / time | When the incident happened |
location | Where it happened |
onArrival | Whether the injury was already present when the child arrived |
description | What happened |
firstAid | What first aid was given |
parentsNotified | How and when parents were informed |
acknowledgedBy / acknowledgedAt | If and when a parent acknowledged the report |
accidentTypeId | The category of accident |
reportTypeNameAtCreation | Report type name at the time it was created |
lado | Whether LADO was notified |
ofsted | Whether Ofsted was notified |
riddor | Whether a RIDDOR report was filed |
status | Report status |
note | Any additional notes |
createdAt / createdBy | When and who created it |
lastUpdatedAt / lastUpdatedBy | Last edit details |
deletedAt / deletedBy | If deleted |
active | Whether still active |
Body map
File: body_map_point.csv
Markers on a body diagram showing where an injury occurred.
Column | What it means |
bodyMapPointId | Unique ID |
reportId | Which accident report |
fileId | Which body map image was used |
x / y | Coordinates of the marker on the image |
radius | Size of the marker |
Other accident report files
accident_report_status.csv — a history of status changes for each report. Columns: statusId, reportId, status, createdBy, createdAt, deletedBy, deletedAt.
famly_daycare_accident_domain_model_witnesses.csv — staff recorded as witnesses. Columns: reportId, employeeId.
famly_daycare_accident_domain_model_staff_present.csv — staff recorded as present. Columns: reportId, employeeId.
famly_daycare_accident_domain_model_accidentreport_file.csv — attached documents. Columns: reportId, fileId.
famly_daycare_accident_domain_model_accidentreport_image.csv — attached photos. Columns: reportId, imageId.
Permissions and Consents
Permission replies
File: famly_permission_domain_model_permissionreply.csv
The family's responses to permission requests — for example, consent for sunscreen, photos, or trips.
Column | What it means |
permissionReplyId | Unique ID |
permissionid | Which permission this replies to |
recipient | The child this applies to |
answer | Their answer — a numeric code (yes/no/not answered) |
createdat / deletedat | Timestamps |
famly_permission_domain_model_permissionreplychange.csv — a log of every time a permission answer was changed. Columns: permissionreplychangeid, permissionReplyId, loginId, answer, createdat.
Holiday and Event Replies
Holiday replies
File: famly_daycare_vacation_domain_model_vacationreply.csv
The family's overall response to a holiday period set by the nursery.
Column | What it means |
vacationReplyId | Unique ID |
vacationId | Which holiday period this replies to |
childId | Which child |
repliedat | When the family replied |
deadline | When they needed to respond by |
lastreminder / noreminders | Reminder history |
lastday | The last day covered by this reply |
deletedat | If removed |
Holiday reply — daily breakdown
File: famly_daycare_vacation_domain_model_vacationreplyday.csv
The day-by-day choices within a holiday reply.
Column | What it means |
persistenceid | Unique ID |
vacationreply | Which reply this belongs to |
day | The specific date |
answer | The family's response for that day |
from / to | Start and end time for that day, if applicable |
Event replies
File: famly_daycare_event_domain_model_eventreply.csv
Whether the child's family responded to a calendar event — for example, a trip or parent meeting.
Column | What it means |
eventReplyId | Unique ID |
eventId | Which event |
repliertype | Who replied — CHILD means on behalf of the child |
replierid | The child's ID |
nochildren / noadults | How many children and adults are attending |
body | Any message with the reply |
repliedat / deletedat | Timestamps |
inviteat / invitedat | When the invite was scheduled and sent |
Health and Medication
Medication forms
File: medication_form.csv
The standing medication instructions for the child — what they take, the dose, and why. All other medication files link back to this.
Column | What it means |
medicationFormId | Unique ID |
childId | Which child |
medicationName | Name of the medication |
dosage / dosageUnit | Dose and unit — e.g. 5ml |
reason | Why the child needs it |
administerTo | End date through which it may be given |
dailyNotifications | Whether staff get daily reminders |
acknowledgedByParent / acknowledgedByStaff | Whether each has acknowledged |
createdBy / createdAt | When and who created it |
lastChangedBy / lastChangedAt | Most recent edit |
deactivatedAt / deactivatedBy | If deactivated |
deletedAt | If deleted |
Medication administered
File: medication_administered.csv
A record of each dose given to the child.
Column | What it means |
administeredMedicationId | Unique ID |
medicationFormId | Which medication form |
doseGiven / doseUnit | What was actually given |
administeredBy | Who gave it |
administeredAt | When |
scheduledAt | Which scheduled time slot this corresponds to |
comment | Any freeform note |
Medication daily updates
File: medication_form_daily_update.csv
A per-day update record for a medication form.
Column | What it means |
dailyUpdateId | Unique ID |
medicationFormId | Which medication form |
day | The day covered |
lastAdministeredAt | When it was last given that day |
note | Freeform daily note |
createdBy / createdAt | Who created it and when |
medication_form_daily_update_time.csv — scheduled times within a daily update. Columns: dailyUpdateId, time.
scheduled_medication_administration.csv — the scheduled times of day for giving medication. Columns: medicationFormId, time.
medication_form_created_signature.csv — links a medication form to its consent signatures. Columns: medicationFormId, signatureId.
medication_administered_signature.csv — links an administration to confirming signatures. Columns: administeredMedicationId, signatureId.
medication_administered_witness.csv — staff who witnessed an administration. Columns: administeredMedicationId, employeeId.
medication_form__gf_field_value.csv — custom field values on a medication form. Columns: medicationFormId, gfFieldValueId.
Signatures
File: signature.csv
Digital signatures on medication forms, administrations, and child notes.
Column | What it means |
signatureId | Unique ID |
signedAt | When signed |
signedBy | Who signed |
signedAs | In what capacity — e.g. Employee or Parent |
signatureType | What was being signed |
withdrawnAt / withdrawnBy | If withdrawn |
Forms and Tasks
Form submissions
File: crf_form_submission.csv
Completed registration or information forms submitted for the child.
Column | What it means |
submissionId | Unique ID |
formId | Which form template |
formVersionNumber | Which version of the form was used |
childId | Which child |
siteId | Which nursery |
createdAt | When submitted |
ipAddress | IP address it was submitted from (often blank) |
Form answers
File: crf_form_submission_value.csv
The individual answers submitted for each field in a form.
Column | What it means |
submissionValueId | Unique ID |
submissionId | Which form submission |
fieldId | Which question was answered |
stringValue | Text answer |
intValue | Numeric answer |
booleanValue | Yes/no answer |
dateValue | Date and time answer |
localDateValue | Date-only answer |
localTimeValue | Time-only answer |
fileIdValue | Reference to an uploaded file answer (binary in media/files/) |
calendarBookingId | Reference to a calendar booking made via the form |
Form access links
File: crf_form_submission_key.csv
One-time links that allow a parent to fill in a form without logging in to Famly.
Column | What it means |
submissionKeyId | Unique ID |
childId | The child the form is for |
relationId | The family member the link was sent to |
formId | Which form |
Email the link was sent to | |
expiresAt | When the link expires |
revokedAt / revokedBy | If revoked |
createdAt / createdBy | When and who created it |
siteId | Which nursery |
Tasks
File: task_log.csv
Tasks assigned to and completed by staff — for example, filling in a form, completing a profile section, or sending a message.
Column | What it means |
taskLogId | Unique ID |
taskType | Type of task |
assignedTo | Who it was assigned to |
siteSetId | Which nursery |
completedAt / completedBy | When and who completed it |
createdAt / createdBy | When and who created it |
deletedAt / deletedBy | If deleted |
notifiedAt | When a notification was sent |
Task detail files
Each type of task has its own detail file:
task_log_form.csv — "complete this form" tasks. Columns: taskLogId, taskType, formId, childId, submissionId.
task_log_child_profile_completion.csv — "complete a profile section" tasks. Columns: taskLogId, taskType, profileSection, childId.
task_log_send_message.csv — "send a message" tasks. Columns: taskLogId, taskType, childId.
task_log_employee_todo.csv — freeform staff to-dos. Columns: taskLogId, taskType, description, targetUrl, dueDate, isEditable, childId.
Enrolment Inquiries
Inquiries
File: famly_daycare_inquiry_domain_model_inquiry.csv
Enrolment inquiry or lead records for the child.
Column | What it means |
inquiryId | Unique ID |
childId | The child |
siteId | Which nursery |
groupId | Room or group for enrolment |
status | Pipeline status — e.g. new, enrolled, lost |
source | Where the inquiry came from |
note | Freeform note |
lostcategory / lostreason | If lost, the category and reason |
bookingnote | Note on an associated booking |
enrolledBy / enrolledAt | Who completed enrolment and when |
priority | Lead priority |
formPaymentTransactionId | Reference to a payment via the registration form |
createdAt / createdBy | When and who created it |
deletedAt / deletedBy | If deleted |
active | Whether active |
Inquiry follow-up actions
File: famly_daycare_inquiry_domain_model_inquiryaction.csv
Follow-up actions logged against an inquiry — calls, emails, tasks, or tours.
Column | What it means |
inquiryActionId | Unique ID |
inquiryId | Which inquiry |
type | Kind of action |
subject | Short title |
note | Freeform details |
due | When it's due |
createdAt / createdBy | When and who created it |
lastUpdatedAt / lastUpdatedBy | Last edit |
deletedAt / deletedBy | If deleted |
Care Plans and Sessions (Bookings)
Care plans
File: famly_daycare_sessions_domain_model_plan.csv
The child's care plans — each covers a period of care and defines sessions, pricing, and billing.
Column | What it means |
id | Unique plan ID |
child | Which child |
from / to | When the plan is active |
note | Freeform note |
pricingGroupId | Which pricing group applies |
ruleGroupId | Which booking rules apply |
version | Version number |
active | Whether currently active |
createdat / createdBy | When and who created it |
deletedAt / deletedBy | If deleted |
lastUpdatedAt | Last update timestamp |
Finance and Billing
Deposits
File: famly_daycare_invoicing_domain_model_deposit.csv
Deposits recorded for the child.
Column | What it means |
depositId | Unique ID |
childId | Which child |
amount | The deposit amount |
status | Whether held, returned, etc. |
date | Deposit date |
note | Freeform note |
billPayerId | Who paid it |
depositReturnId | Links to the return record if refunded |
createdAt / deletedAt / lastUpdatedAt | Timestamps |
famly_daycare_invoicing_domain_model_depositreturn.csv — records a deposit being returned. Columns: depositReturnId, depositId, createdAt, lastUpdatedAt.
Custom invoice lines
File: famly_daycare_invoicing_domain_model_customline.csv
Manual charges, credits, and system-generated lines on the child's invoices — including funding deductions, surcharges, and fees.
Column | What it means |
customLineId | Unique ID |
invoiceId | Which invoice |
childId | Which child |
title | Line title on the invoice |
description | Line description |
amount | Amount |
from / to | Period covered |
targetType / targetId | What this line is linked to — e.g. a funding line or deposit |
active | Whether active |
createdAt | When created |
Bill payers
File: famly_daycare_invoicing_domain_model_billpayershare.csv
Who pays the bill for the child and what percentage they're responsible for.
Column | What it means |
billPayerShareId | Unique ID |
billPayerId | Which bill payer |
childId | Which child |
share | Their share — e.g. 1.0 = 100%, 0.5 = 50% |
ordering | Display order |
active | Whether currently active |
createdAt / lastUpdatedAt | Timestamps |
famly_daycare_invoicing_domain_model_billpayerrelation.csv — links a bill payer account to a family member's profile. Columns: billPayerId, relationId.
Government funding
finance_funding_period.csv — a block of government or childcare funding over a date range. Key columns: fundingPeriodId, fundingTypeId, childId, periodStart, periodEnd, amount.
finance_funding_peritem_line.csv — funding applied to a specific purchased product. Key columns: fundingPerItemLineId, fundingPeriodId, purchaseId, productId, purchaseDate.
finance_funding_flatrate_line.csv — a flat-rate funding line over a date range. Key columns: fundingFlatRateLineId, fundingPeriodId, dateStart, dateEnd.
UK-specific funding
tax_free_childcare_correlation.csv — Tax-Free Childcare payment references. Key columns: correlationId, childId, loginId, outboundChildPaymentRef.
uk_funding_eligibility.csv — government funding eligibility codes and validity windows. Key columns: childId, fundingCode, codeValidityStartDate, codeValidityEndDate.
uk_funding_child_entitlements.csv — UK funding entitlement periods. Key columns: childFundingEntitlementId, childId, startDate, endDate.
Ad-hoc purchases (extra sessions and products)
These files cover sessions and products booked outside of the regular care plan.
famly_daycare_sessions_domain_model_purchase.csv — the parent record for each ad-hoc purchase.
Column | What it means |
purchaseId | Unique ID |
childId | Which child |
siteId | Which nursery |
purchaseDate | The date the purchase is for |
discountAmount | Any discount applied |
type | Whether booked by staff or a parent |
note | Freeform note |
noteVisibleToParents | Whether the note shows to parents |
approvedBy / approvedAt | Who approved and when |
active | Whether still active |
createdAt | When created |
famly_daycare_sessions_domain_model_sessionpurchase.csv — individual purchased sessions.
Column | What it means |
sessionPurchaseId | Unique numeric ID |
id | UUID |
purchaseId | Which purchase |
sessionAvailabilityId | The session slot |
start / end | Session times |
price | Price charged |
purchaseDate | Date booked for |
Session Name | Name of the session — e.g. "Afternoon session" |
createdAt / deletedAt | Timestamps |
famly_daycare_sessions_domain_model_productpurchase.csv — individual purchased products (e.g. meals).
Column | What it means |
productPurchaseId | Unique numeric ID |
id | UUID |
purchaseId | Which purchase |
productAvailability | The product at the nursery |
amount | Quantity |
price | Price charged |
purchaseDate | Date purchased for |
Product Name | Name of the product — e.g. "Lunch" |
createdAt / deletedAt | Timestamps |
purchase_inactive_status.csv — why a purchase was rejected or cancelled.
Column | What it means |
purchaseId | Which purchase |
rejectionMessage | Why it was rejected |
rejectedAt / rejectedBy | When and who rejected it |
deletedAt / deletedBy | If deleted instead |
famly_daycare_invoicing_domain_model_purchaseline.csv — the invoiced amount for a purchase.
Column | What it means |
purchaseLineId | Unique ID |
invoiceId | Which invoice |
purchaseId | Which purchase |
total | What the family pays |
originalTotal | Before any adjustments |
share | Bill payer share applied |
from / to | Date range covered |
active | Whether active |
createdAt | When created |
famly_daycare_invoicing_domain_model_purchaselinecreditnote.csv — links a purchase line to a credit note. Columns: purchaseLineCreditNoteId, purchaseLineId, creditNoteId, active.
Finance linking tables
These files connect invoice sub-lines to the underlying sessions or products. They're internal reference data.
File | What it links |
finance_sub_line_purchase.csv | Sub-line → purchase |
finance_sub_line_purchase_line.csv | Sub-line → purchase invoice line |
finance_sub_line_session.csv | Sub-line → session (includes times and unit price) |
finance_sub_line_product.csv | Sub-line → product (includes quantity and unit price) |
Photos, Files, and Videos
The media/ folder in the ZIP contains the actual image, document, and video files referenced throughout the CSVs. The CSV files below act as an index. Use them to identify which file in media/ belongs to which record.
Images
File: famly_core_image_domain_model_image.csv Folder: media/images/
Photos attached to observations, accident reports, and child notes — plus photos the child is tagged in. Files are named <imageId>-<originalfilename>.
Column | What it means |
imageId | Unique ID (matches the filename in media/images/) |
imagefor | What the photo is attached to |
id | ID of the owning record |
objecturloriginal | Storage URL of the full-size image |
objecturlsmall / objecturlbig | Resized versions |
width / height | Dimensions in pixels |
filesize | File size in bytes |
mime | File type — e.g. image/jpeg |
filename | Original filename |
createdat / deletedat | Timestamps |
Documents and files
File: famly_core_file_domain_model_file.csv Folder: media/files/
Documents attached to observations, accident reports, child notes, and form submissions. Files are named <fileId>-<originalfilename>.
Column | What it means |
fileId | Unique ID (matches the filename in media/files/) |
filename | Original filename |
filesize | File size in bytes |
objecturl | Storage URL |
createdBy | Who uploaded it |
createdat / deletedat | Timestamps |
Videos
File: famly_core_video_domain_model_video.csv Folder: media/videos/
Videos attached to observations. Files are named <videoId>.<extension>.
Column | What it means |
videoId | Unique ID (matches the filename in media/videos/) |
videourl | URL of the processed, playable version |
thumbnailurl | URL of the thumbnail |
duration | Duration in seconds |
width / height | Dimensions in pixels |
filesize | File size in bytes |
status | Processing status |
createdbyloginid | Who uploaded it |
createdat / deletedat | Timestamps |
Profile photos
Folder: media/profile-images/
Profile photos of the child's family members and contacts. See famly_core_image_domain_model_profileimage.csv in the Profile and identity section for the metadata. Files are named <imageId>.<extension>.
Need help?
If you have questions about your child data export, get in touch at support@famly.co.