Most private schools in India still run critical data in Excel. Migrating to a school ERP like Pathshala is less about software and more about discipline with data. Use this checklist to reduce risk and shorten go-live.
Before You Import Anything
- Freeze a master sheet — One workbook per domain (students, fees). No more “final_v2_really_final.xlsx”.
- Standardise columns — Admission number, student name, class, section, guardian phone, and fee heads should match what your ERP expects. Our student import flow validates duplicates and required fields.
- Clean phone numbers — Use a single country code format (e.g. +91) so SMS templates work on day one.
Pilot, Then Scale
Run one academic section (e.g. Class 6) for two weeks: attendance, fees, and at least one broadcast SMS. Fix process issues before the whole school moves. Schools that skip this step usually overload the helpdesk in week three.
Go-Live Week
- Day 1–2: Classes, sections, and academic year configured
- Day 3: Bulk student import + spot-check 20 random records
- Day 4: Teachers trained on attendance (15 minutes each)
- Day 5: Accountants trained on invoices and receipts
After Go-Live
Export a roster weekly for the first month and compare against your old Excel — discrepancies should trend to zero. For fee workflows, pair this guide with our post on reducing fee defaulters.
When you are ready, request a demo and we will map your sheets to Pathshala’s import templates.