Skip to content
BirthTracks Help CenterBirthTracks Help Center

Import from CSV

Import brings records in from another system. Your spreadsheet does not need to match a template — upload it with whatever columns it has, tell us which column holds which field, and import. Valid rows are imported; rows with problems are listed so you can fix and re-upload them.

Import is a write-only surface: it appears in the sidebar as Import (under Registry) only for members who can manage records — Admins and Providers. A Viewer does not see it, and a Scribe is denied at the door.

The wizard, step by step

Section titled “The wizard, step by step”

A progress strip at the top of the page tracks where you are: Upload → Map → Providers → Review → Done.

1 · Upload

Section titled “1 · Upload”
  • Download CSV template — optional. If you’d rather re-shape your export to our column names, this gives you the empty template the capture importer accepts.
  • Choose your CSV file (.csv, up to 5 MB) and select Continue to mapping.

2 · Map

Section titled “2 · Map”

On Map your columns, match each birth-record field to a column from your file. Leave a field blank (— Not in file —) if your file doesn’t have it. One field is required — the birth date & time (marked with a *); until you map it, import refuses with “Map the column that holds each birth date & time before importing.”

There is also an optional Attendant / provider name column — pick the column that names who attended each birth so imported records keep per-attendant attribution. Select Continue.

3 · Providers

Section titled “3 · Providers”

If your provider column holds names we haven’t seen before, Attribute your providers appears: match each provider name from your file to a member of your practice. Leave one — Unattributed — if it doesn’t map to a member. We remember these choices for your next upload. Select Continue.

4 · Review

Section titled “4 · Review”

If any values in a constrained field don’t match the options we record, Translate your values appears: match each one to an option, or — Ignore (leave blank) — to leave that field blank. These choices are remembered too. Then select Import records — this is the one irreversible action in the flow.

5 · Done

Section titled “5 · Done”

The import runs and shows a summary: “:imported imported · :failed need attention”. Possible duplicate births are called out by line. Columns that mapped to no standard field are preserved read-only in Legacy fields on each record rather than dropped, so you always know where every legacy field landed. Any rows with problems are listed in a Line / Problems table so you can correct and re-upload them.

Past imports

Section titled “Past imports”

Below the upload form, Past imports lists your practice’s recent uploads (newest first) with File, Status, Rows (ok / failed), By and When. For a run with failures, Results downloads a CSV of just the rows that need fixing — so days later you can pull the report without re-running the upload. Members who manage records can also Delete a run from the history; this removes only the record of the import, never the births it created.

Next steps

Section titled “Next steps”