Move 800 students from Excel to live in 20 minutes.

The migration nightmare we removed

When a school switches to a new system, the question is always: how do we move our students? The standard answer — manually re-enter every record — kills adoption. Even a 300-student school is a week of typing, with errors.

Edunile’s bulk upload accepts your existing Excel or CSV. Download our template (which mirrors how most Nigerian schools already keep their student lists), paste your data, and upload. The system validates every row server-side, shows you which rows have problems (missing class, duplicate ID, malformed date of birth), and lets you fix only those rows in-line. Once everything is green, click Import and the records flow into your live database via Cloud Tasks — typically under five minutes for 1,000 students.

Validation that catches problems early

Every common data issue is checked before commit: duplicate admission numbers, parents linked to multiple students with conflicting phone numbers, class names that don’t exist in your academic structure, malformed dates, missing required fields. You see exactly which row, which column, which problem — fix in place, revalidate, import.

For schools with siblings, the import recognises shared parent contact information and creates a single guardian record linked to all the right students.

Same workflow for staff and report card imports

The bulk upload framework powers more than student imports. Staff onboarding (teachers, non-teaching), assessment grade upload, and end-of-term promotion confirmation all use the same validate-then-commit pattern — so once you’ve done it once, you know how every bulk operation in Edunile behaves.