A Clean Start: Prepare School Data Before You Import

Importing school data is easy to describe and surprisingly easy to misunderstand. A file can contain all the expected columns and still disagree with the way the school operates. Duplicate students, old class names and unclear staff assignments become much more visible once people start using the system.

Skoolia includes a school data-import workflow. The best preparation is to agree what the data means before moving it. Use this guide to make the first import a reviewed step toward a useful school workflow.

Choose the authoritative source

Identify who owns each dataset and which version is approved. The newest filename is not always the most reliable source. Ask the owner to confirm the academic period, the records included and any known gaps.

Keep the original source unchanged and prepare a working copy. This gives the team a reference when a mapping or value is questioned later. Record who approved the working copy and when.

Use consistent identifiers and names

Check the fields your workflow uses to distinguish records. Two students can share a name, and a teacher’s name can appear in more than one spelling. Follow the import requirements for identifiers rather than assuming that a display name is unique.

Review class, subject and academic-period labels together. The same class should not appear under different names in the student and teacher files. Resolve differences with the school’s data owner before attempting to map them.

Prepare only what the first workflow needs

For an attendance pilot, focus on accurate students, classes and relevant staff assignments. For a timetable evaluation, focus on the scheduling inputs. Bringing every historical file into the first step can create work that does not help the pilot succeed.

• Confirm the source owner and academic period.
• Check required fields against the import instructions.
• Review duplicate or ambiguous records.
• Standardise class and subject labels.
• Remove irrelevant material from the pilot working copy.
• Agree how the team will verify the imported result.

Validate relationships as well as rows

A student record can look correct on its own while belonging to the wrong class. A staff record can be accurate while lacking the assignment the pilot requires. After import, verify a representative set of connected records in the workflow where staff will use them.

Include ordinary edge cases in that review: a recent class transfer, a part-time teacher or a student with an updated guardian contact. Use fictional examples for public demonstrations and protect actual school information during internal checks.

Resolve the cause before repeating the import

If something is wrong, establish whether the issue comes from the source file, the mapping or the subsequent setup. Avoid repeatedly importing the same file without understanding the result. The aim is an accurate operational record, not simply a successful upload.

Explore Skoolia data import and prepare a small, approved dataset your team can confidently verify.