Why did some rows in my import fail?
Reading the "Check file" results before you commit an import.
- 1
Importing always runs in two steps: "Check file" reads every row and shows you what would happen, without saving anything; "Import" only then writes exactly what the check showed you.
- 2
A row with a problem is skipped whole — it never half-imports a student. Every other good row in the file still goes through.
- 3
The most common cause is a class name that doesn't match your school's structure exactly. If it's close, the check tells you which existing class it might be.
- 4
Other common causes: a missing student first or last name, a duplicate admission number already used earlier in the same file, or a guardian row with no valid email address.
- 5
A row with no guardian at all isn't an error, just a warning — the student is still created, but nobody will see that child's updates until a guardian is linked.
Still stuck?
WhatsApp usWe'll walk you through the fix, not a sales pitch.
Tell us a little about your school and we will walk you through ScholarBell using a demo school that looks like yours.
See one message reach every parent, with proof it landed.
No pressure, no jargon. Thirty minutes, with a demo school that looks like yours.