Guide
Moving your school from registers to software
What to migrate first, how to run old and new in parallel for a term, and how long the move from paper really takes.
Moving a school off paper registers is a one-term project with three phases: enter the present (students, guardians, fee plans), run one area at a time in parallel with the registers, and retire the paper only when the software has been the truth for a full cycle. Schools that fail at this almost always tried to do everything in week one.
What goes in first?
| Order | Data | Why this order |
|---|---|---|
| 1 | Classes, sections and the session | The structure every record attaches to. |
| 2 | Students, from your existing Excel list | Bulk import with validation turns the list you have into records, and flags the rows that need fixing. |
| 3 | Guardians and phone numbers | Reminders and portals are only as good as these. |
| 4 | Fee plans and concessions | So the first month's invoices are right, not corrected. |
| 5 | Staff records | Needed before payroll, not before attendance. |
Leave history behind: last year's marks and five years of fee history belong in the cupboard, not in the migration. The registers remain the archive for the past; the software becomes the truth for the present.
How does the parallel term work?
- Weeks 1 to 2: structure and students go in; the office fixes what the import validation flagged.
- Weeks 3 to 6: attendance runs in the software, marked by teachers in their own portal; the register continues as backup. One area, one habit.
- Weeks 7 to 10: fees move over: the month's invoices generate from the fee plans, collection is receipted in the system, and the fee register is retired first, because it is the one with the errors.
- End of term: exams and report cards run in the software for the term exam; parents get their portal logins once there is something worth seeing in them.
What decides whether the move sticks?
Three things, none of them technical. A named owner in the office who fixes flagged rows the week they appear. A principal who reads the software's reports, not the register, in the morning meeting, because staff follow what the principal reads. And the rule that once an area has moved, the paper version is backup only: two truths is how migrations die. Our choosing guide helps you pick the system before the move, the implementation page shows how EDUTIG runs this onboarding with you, and the spreadsheets comparison is for the school still deciding whether to move at all.