When to start
The best time to switch is the start of an academic session, when classes and sections are being set up anyway and there is no half-finished year to carry across. Count back six weeks from the first day of term to find the start date for this plan.
A mid-session start is possible. It means importing the attendance, fee payments and marks already recorded this year, which adds work to the first week and makes the period of running both systems side by side more important.
Before week one: decide and collect
Decisions made before anybody opens the software save the most time later. Settle these with the principal and the office:
- The class and section structure for the session, including streams in the senior classes.
- Fee structures for each class, installment dates, and the concession categories you actually use.
- Your board's rules and the marksheet format you issue, with a sample from last year.
- Who owns the system: one named person in the office with authority to make configuration decisions.
Then collect the data: a student list with admission numbers, dates of birth, class and section; guardian names, phone numbers and email addresses; and a staff list showing which subjects and sections each teacher takes.
Week 1: clean and import the records
Spreadsheets kept for years contain duplicates, class names written three ways (“8A”, “VIII-A”, “Class 8 A”), missing dates of birth and phone numbers in several formats. Fix these in the spreadsheet first. An import that validates every row before saving — as AcadiFlow's bulk import does — will show you the errors, but correcting them at the source is faster.
- Create the academic session, classes, sections and subjects.
- Import staff, and assign them to the sections and subjects they teach.
- Import students against their class and section for the session.
- Import or add guardians, and link them to their children.
- Spot-check twenty records against the paper admission register.
Do not move on until the class lists are right. Attendance, fees and results all hang off this record.
Week 2: attendance and the timetable
Attendance makes the best first module. It is used every day, it is simple, and mistakes in the class lists show up in it immediately. Train class teachers in the week they start, in a ten-minute session on the device they will actually use.
If you take attendance period by period, set up the timetable in the same week, since period registers depend on it. Keep the paper register running alongside for one week and compare the totals each afternoon.
Weeks 3 and 4: fees
Fees go live once the student list is trusted, because every invoice is attached to an enrolment. Enter the fee structures, raise invoices for the current installment, and record opening balances for students carrying dues from last year.
- Train the cashier on counter collection, receipt printing and the day-end report first.
- Reconcile each day's collections against the bank and the cash book for the first week.
- Switch on online payment only once counter collection is running cleanly.
The fee management guide covers structures, concessions and receipts in detail.
Week 5: parents and communication
Invite parents once there is something useful for them to see — attendance and fees due — rather than on the first day. Send invitations class by class so the office can handle the questions that follow each batch.
Tell families what the parent portal is for and where notices will arrive. If you are moving notices away from WhatsApp groups, say so, and set a date after which school notices come only through the portal and email.
Week 6: examinations and results
Examinations come last because they are the most rule-heavy and the least frequent. Configure the grading scale and result rules for your board, then run last year's marks for one class through the system and compare the output with the marksheet you actually issued.
Only when that comparison matches should teachers enter this term's marks. A discrepancy found now is a configuration change. One found after results are published is a letter to parents.
Training that sticks
- Train each group in the week they start, on the task they will do, on their own device.
- Give every group one person to ask: the system owner in the office, and one confident teacher per floor or wing.
- Write a one-page instruction sheet for each daily task and pin it where the task is done.
- Expect questions to peak in the second week of each module rather than the first, once people start trying things on their own.
Common mistakes
| Mistake | What happens | What to do instead |
|---|---|---|
| Switching everything on at once | Every problem arrives in the same week and nobody can tell which module caused it | Phase the rollout, one module at a time |
| Importing data without cleaning it | Duplicates and wrong class names spread into fees and results | Clean the spreadsheet first and spot-check after import |
| Training everyone on day one | By the time staff need it, they have forgotten it | Train each group in the week they start |
| Keeping the paper records going indefinitely | Two sources of truth that slowly disagree | Run both for a week or two, then stop the paper |
| No named system owner | Configuration questions wait on the vendor, or on nobody | Name one person in the office with authority to decide |
Common questions
How long does a school ERP implementation take?
Around six weeks for a single-campus school moving from spreadsheets, if the rollout is phased and the data is cleaned first. Larger schools, several campuses, or a move from another ERP with historical data to carry across take longer.
What data do we need before importing into a school ERP?
A student list with admission numbers, dates of birth, class and section; guardian names and contact details; a staff list with the subjects and sections each teacher takes; and your fee structures and concession categories.
Should we run paper records and the new system in parallel?
Yes, briefly. A week or two per module is enough to catch configuration errors by comparing totals. Longer than that creates two records that drift apart, and staff keep trusting whichever one they are used to.
Which module should a school implement first?
Student records, followed by attendance. Attendance is used every day, is simple to learn and exposes errors in the class lists quickly, which makes it the best test of the imported data before fees and examinations depend on it.