The Honest Problem with Excel
Excel is not a bad tool. It is a brilliant tool — for the job it was designed for. School management is not that job. When your fee ledger is a 12,000-row spreadsheet that only one person knows how to update without breaking the formulas, you have a single point of failure, not a system. When load-shedding hits and the auto-save didn't run, you lose a morning's work. When the principal asks for a cross-campus report, someone spends a weekend manually compiling tabs.
The migration from Excel to ERP is not about abandoning what you know. It is about replacing fragile manual processes with something that works for the school even when the person who built the spreadsheet is on leave.
Phase 1: Assessment (Week 1)
Before moving any data, understand what you have:
- List every Excel file the school uses — fees, attendance, salaries, timetables, results
- Identify the owner of each file — who built it, who uses it, who depends on it
- Map the gaps — which data is duplicated across files, which is missing entirely
- Note the workarounds — manual processes that exist because Excel can not do something
Most schools discover they have 15–20 separate files doing the job one integrated system should do.
Phase 2: Data Cleaning and Import (Week 2–3)
Skoo provides an Excel import template for student data. Before importing:
- Standardise names — "Muhammad" vs "M." vs "Mohammad" should resolve to one format
- Verify class/section mapping — ensure grade labels match Skoo's structure
- Clean contact numbers — remove spaces, dashes, and country codes so WhatsApp automation works
- Prepare fee structures — list all fee heads (tuition, transport, lab, late fine) with amounts by class
Skoo's onboarding team reviews the import file before it goes live. You get one chance to start clean — use it.
Phase 3: Parallel Running (Week 3–4)
Do not switch off Excel the day Skoo goes live. Run both systems simultaneously for 2–4 weeks:
- Enter new fee payments in Skoo; verify totals match your Excel ledger
- Mark attendance in Skoo; cross-check against the class register
- Run payroll in Skoo; compare output to the salary sheet
When the two systems agree consistently for two weeks, you have confidence the migration is clean. This phase catches 90% of data issues before they matter.
Phase 4: Staff Training (Week 2–4, overlapping)
Training is where migrations succeed or fail. The key insight: train role by role, not department by department.
- Accountant first — fee collection and reconciliation; they see the biggest immediate gain
- Teachers second — attendance marking and result entry; quick wins build confidence
- Admin staff third — admission forms, certificates, communication
- Principal last — reports and dashboards; by now the data is real and the value is obvious
Phase 5: Go-Live (Month 2)
Pick a clean date to cut over — the start of a new month or the start of a new term. Archive the old Excel files (do not delete them). Announce to parents that receipts and communications will now come from Skoo. Update the bank account references in fee challans.
Most schools are fully comfortable within 60 days of go-live. The Excel files become reference documents and are never opened again.
What Schools Wish They Had Known Earlier
- Start with clean data. Bad data in Excel becomes bad data in ERP. Take an extra week to clean it.
- Get buy-in from the accountant first. If the finance team resists, the migration stalls everywhere.
- Set a hard cutover date. Open-ended timelines become permanent parallel operation.
- Trust the system to do the maths. The urge to double-check everything in Excel fades within a month.