Clean your student, fee and staff data, load it through an Excel template, and check the first challans against your old records before switching fully. During EDUBase onboarding, the EDUBase team loads your student data for you.
What should a school prepare before leaving registers or Excel?
Most migration problems are data problems, not software problems. Registers and spreadsheets often hold the same child under two spellings, siblings without a shared family number, or fee amounts that were changed by hand and never written down.
Spend your preparation time on the records the software will depend on every month. Decide who owns each list, and agree one correct version before anything is loaded.
- Student list: name, class, section, campus, guardian details and fee details in one sheet.
- Family links: decide which siblings belong under one family number, so vouchers and reminders can work per family.
- Fee policy: the fee heads you charge, the amount per class, and your late fee rule.
- Old dues: the balance each family owes at the cut-off date, and any payments already made against the current session.
- Staff list: designations, shifts and salary details if you also want payroll to move across.
How does your existing data get into the new system?
EDUBase onboarding is built around an Excel template. The school fills in a student data Excel, with campus and fee details included. The EDUBase team uploads it, confirms with a screenshot, and then shares the login URL, institute code and admin credentials with a how-to video.
Old dues and past payments can be loaded as well, so the first challan is right. This matters more than it sounds, because a wrong opening balance on the first voucher is the quickest way to lose parents' trust in the new system.
- Upload Students: add or update students in bulk from Excel.
- Upload Fee Plans: assign fee plans to students in bulk.
- Upload First Time Arrears: bring old dues from your previous system onto the first challan.
- Upload Challan Payments: load past payments so history is complete.
- Large files run in the background, and you are notified in the portal when they finish.
What should be set up before the student list is loaded?
Students need somewhere to sit. Before the upload, set up your campuses, the classes each campus runs, sections and sessions. These are set once and reused by fees, attendance and exams.
Also decide who will use the system. Staff sign in with the school code, a username and a password, and you can grant screens and actions per user and limit each person to their own campuses. Give the people who handle money or marks only what they need.
- Campuses, classes, sections and sessions in School Setup.
- The Holiday Calendar, which fee automation uses later.
- Admission Capacity and Roll Number Series if you want seat limits and automatic roll numbers.
- Users and privileges, including which payments, discounts or admissions need a second person to approve.
Should you run the old and new systems side by side?
Yes, for a short, defined period, and with a clear test. The best test is simple: generate the first challans and compare a sample of families against your register. Check the opening dues, the monthly fee, and any concession the family was promised.
For the accounts, EDUBase offers an old versus new ledger comparison, so a school can run the new ledger alongside the old one and compare account by account before switching.
Set an end date for the parallel run. Without one, staff keep writing in both places and neither record can be trusted.
- Compare a sample from every class, not only the easy ones.
- Correct errors in the system, not on paper, so the system becomes the record.
- Record the day the paper register stops being the official record.
How do you bring teachers, parents and the front office along?
Staff adoption decides whether the move succeeds. EDUBase offers live online training sessions on Google Meet, scheduled on request, plus module-wise YouTube playlists and an in-app Docs page and AI assistant for self-service. The assistant understands Roman Urdu and English.
For parents, the free Android Parents App lets them follow attendance, fees, marks, diary and notices, and they log in with a one-time code. The portal's Parent App Analytics shows adoption by class and section, so you know which classes to push.
- Train the fee counter and the class teachers first, because they use the system daily.
- Tell parents the date from which vouchers and attendance messages come from the new system.
- Use support by WhatsApp group or phone during live working hours in the first weeks.
When should automation and bank collection be switched on?
Switch these on after the first manual cycle is correct. Every fee automation in EDUBase ships switched off and has a preview that shows which children would be affected and by how much, charging nothing. That makes it safe to test your policy before it acts.
Bank collection needs its own setup. EDUBase configures the routing with the school's bank, shares test vouchers and confirms the bank's inquiry and payment tests before vouchers go live. The school keeps counter payments alongside.
- Start with manual challan generation, then move to scheduled generation.
- Preview late fee and defaulter reminders before enabling them.
- Go live with bank vouchers only after the bank tests are confirmed.
Ways to move from registers or Excel to school software
| Approach | What it involves | Best suited to | Main risk |
|---|---|---|---|
| Full cut-over | Load all data, then stop using registers and sheets on a set date | Small schools with clean, current records | Errors found only after parents receive vouchers |
| Parallel run | Use old and new side by side for a defined period and compare results | Most schools, especially with fee dues involved | Double entry continues if no end date is set |
| Module by module | Begin with students and fees, then add exams, payroll and finance | Larger schools or groups with limited staff time | Modules stay disconnected for longer |
| Campus by campus | Move one campus first, then repeat for the others | Multi-campus schools and school groups | Inconsistent practice between campuses |
| Self-managed data load | Staff prepare and upload the Excel files themselves | Schools with a capable IT or admin person | Template mistakes that need re-uploading |
Related modules
- Bulk Data Import & Onboarding Tools — Move from registers or another system by Excel: students, fee plans, old dues and past payments.
- Student Management & Admissions — Every student record, from first enquiry to leaving certificate, in one place.
- Fee Management & Challans — Fee plans, monthly challans, discounts, family payments and receipts, without spreadsheets.
- Fee Automation — Let the system generate challans, apply late fees and chase defaulters on schedule.
- School Setup & Multi-Campus — Campuses, classes, sections, sessions, academic year and reference lists, set once and reused everywhere.
- Users, Privileges & Activity Log — Give each staff member exactly the screens and actions they need, and see who changed what.
- Finance & Accounting — Chart of accounts, journals, ledgers, trial balance, P&L and balance sheet, fed by fees and payroll.
- Bank Fee Collection — Parents pay at the bank, in their banking app or at a kiosk; EDUBase posts it automatically.
- AI Assistant & Automation — Ask the built-in assistant in English or Roman Urdu, speak instead of type, and let it fill forms.