Import starting balances from your old system
For school admins: seeding first-year plan selections and opening balances from a CSV, so families don't start at zero when the tracking moves to Lumicura.
Moving to Lumicura mid-stream — or after years of a spreadsheet — shouldn’t zero anyone out. Initial Data Import seeds the active program year from a CSV: each family’s plan selection and, optionally, an opening balance per category. It’s a school-admin tool, one row per family, meant to run once at the start.
Prepare the file
- Open Admin › Service Program › Initial Data Import and grab the template — it’s generated for your school, with one balance column per category you track.
- Each row needs the family’s Lumicura family ID (the
fam_…value from the roster export — this import is deliberately exact, no name matching) and their plan code. - Opening-balance columns are optional — leave them blank for families starting at zero.
The family IDs are the fiddly part: export your roster from Lumicura, match it against your old spreadsheet by family name, and carry the IDs across. Ten minutes of spreadsheet work buys an import that can’t credit the wrong Nguyen family.
Preview, then commit
Upload (or paste) the file and Preview — it validates everything without writing: which rows are clean, which have problems, and what each family would start with. Fix, re-preview, and Commit when it’s all green. There’s also a strict mode that rejects the whole batch if any row fails, for when you’d rather fix everything than land a partial import.
Committed rows create each family’s plan selection and an opening entry per non-zero balance, visible on their dashboard like any other credit.
What this tool is not
It seeds a starting point; it doesn’t move ongoing activity. Once the year is running, credit arrives the normal ways — check-ins, approvals, and Bulk Credit for batches (which happily takes family names, unlike this importer).