Moving school records from spreadsheets without losing control

Decide what should move

A migration is a chance to remove duplicates and retire old columns, not a reason to copy every file unchanged. List the records the school actively needs: student and guardian details, class membership, staff accounts, fee structures and the academic information required for the current term.

Make one clean source for each list

1. Choose an owner for each spreadsheet and confirm which version is current.
2. Standardise names, dates, class labels and contact formats; remove duplicate rows.
3. Separate sensitive fields from data that every staff member can see.
4. Keep an untouched, access-controlled backup before any edits.

Test the import with a small sample

Map each spreadsheet column to the matching field before importing. Start with a small sample and check for missing required values, duplicates, incorrect dates and guardian links. Review every error report and fix the source before running the complete import.

Compare a few saved records with the original source after the test. Check both the data itself and the relationships between students, guardians, classes and fee plans.

Set access before inviting everyone

Create roles around real responsibilities. A class teacher may need their class register, while fee collection belongs to a smaller authorised group. Test each role with a sample account and remove temporary access when setup ends.

Choose a cutover and a fallback

Agree when the new system becomes the source of truth, who handles corrections and how the school will keep working if a step fails. Keep the original export until the institution has checked the imported records and approved the new process.

A measured rollout makes it easier to spot gaps while changes are still small. Document the decisions so the next term starts from a process the whole team understands.