Excel to School ERP: Complete Migration Guide (Without Losing Data)
A practical, step-by-step guide for Indian schools migrating from Excel sheets to a modern school ERP — what to clean, what to keep, what to throw away, and how to get live in 48 hours without losing a single fee record.
Asiful Hoque
Founder, WEBNIFY
The Excel problem
Most Indian schools under 1,000 students still run on Excel. A student roster sheet, a fees sheet linked to admission numbers, a marks sheet per class per term, a staff roster, a separate teacher attendance log book, and a Word document for the report card template. It works — until it does not. The sheets diverge over time, formulas break, two staff edit the same workbook, the August fee receipts get mis-categorised under July, and the report card template breaks when the gradebook column count changes. Most schools do not abandon Excel for technical reasons — they abandon it for trust reasons.
Before you migrate: clean, do not move
The single biggest mistake schools make is migrating their Excel exactly as it is into a new ERP. The mess in the spreadsheet becomes the mess in the database. Before migration, run a four-step clean: (1) deduplicate students — same name, slightly different spelling, two admission numbers; (2) standardise class names — "Class 8A" vs "VIII A" vs "8-A" needs to be one canonical form; (3) reconcile fee records against bank statements for the current academic year; (4) archive graduated students — they should not migrate as active. Most schools find this clean takes 6-12 hours over 2 days. It saves 60+ hours of post-migration cleanup.
What to keep
Keep: current academic year student roster (active enrolments only), staff roster with roles and salaries, fee structure (component-wise rates, instalment patterns, sibling discounts), current academic year fee transactions (date, student, component, amount, mode), current academic year marks (term-wise, subject-wise), parent contact details (phone, email, alternate phone, address), exam schedule for the current term, and the list of approved holidays.
What to leave behind
Leave behind (or archive separately, do not migrate): historical fee transactions older than 24 months (regulatory requirement is typically 7 years but they sit in cold storage, not the live system); graduated students; staff who left in past 12 months; old report card templates from previous boards or formats; cached photocopies of marksheets you no longer reference; the Excel file with the macro that breaks on every save. Archive these to a backup drive — they are still your records, just not your live data.
Step 1 — Student roster import
WEBNIFY accepts a CSV or Excel student roster with required columns: admission_number, full_name, class_name, section, gender, date_of_birth, parent_name, parent_phone, parent_email, address. Optional but recommended: alternate_phone, blood_group, transport_route, fee_category. Run the import, review the preview, accept. 500 students typically import in under 30 seconds. Failures (missing required field, duplicate admission number, invalid date format) are flagged inline for fix-and-retry.
Step 2 — Staff roster import
Same pattern with staff. Required columns: employee_id, full_name, role, designation, mobile, email, joining_date, salary_basic. Optional: photo, qualifications, subjects_taught, classes_assigned. Roles should match WEBNIFY's role taxonomy — Owner, Principal, Vice-Principal, Teacher, Accountant, Librarian, Lab-Assistant, Transport, Support. Custom roles can be added during migration.
Step 3 — Fee structure import
This is where most schools mis-step. The fee structure is not the fee transactions — it is the rate card. Import the structure first: which classes pay what components, monthly vs quarterly vs annual cycle, sibling discount rules, late fee rules, scholarship adjustments. Once the structure is locked, import the current academic year transactions against the structure. The system will reconcile — every transaction must map to a structure component, exposing any orphan or mis-categorised entries from the Excel.
Step 4 — Fee transaction import
Required columns: transaction_date, admission_number, fee_component, amount, payment_mode, receipt_number_old, remarks. WEBNIFY assigns new internal receipt IDs but preserves your old receipt numbers in a searchable field for parent queries about historical receipts. Anomalies (transaction without matching student, component not in fee structure, amount mismatch with structure rate) are flagged for review. Most schools find 1-3% of transactions need manual review at this step — and these are usually the ones that were ambiguous in Excel anyway.
Step 5 — Marks import
Marks import is per-class-per-term. Required columns: admission_number, subject, exam_type (FA1/SA1/etc), marks_obtained, max_marks. Optional: remarks, grade_override. The system will compute term grades using the school's grading rules (configured during onboarding) and cross-check against any historical marksheet PDFs you upload. This catches data entry errors from the original Excel where a 95 was entered as 9.5.
Step 6 — Verification round
After all imports, run a verification: pick 10 random students, compare their WEBNIFY profile against the original Excel rows. Pick 5 random fee transactions, verify the receipt regenerates with the same amount and date. Pick 3 mark sheets, compare with the original. This 30-minute round catches 95% of migration anomalies before go-live. It is mandatory in WEBNIFY onboarding.
Step 7 — Cutover and go-live
On go-live day, the school stops using Excel for any new transaction. The Excel files are archived to a read-only folder for the rest of the academic year (regulatory record). All new fee receipts, marks, attendance and communications happen in WEBNIFY. The first day usually has a few staff questions, the second day has fewer, by the end of week 1 the staff is operating natively in the new system. We provide a dedicated WhatsApp / chat support line for the first 30 days post-go-live.
Common migration anxieties, addressed
"What if I lose data?" — original Excel files are preserved unchanged; migration is a copy not a move. "What if the staff cannot adapt?" — most staff is faster on the WEBNIFY mobile app within 3 days than they were in Excel after years; modern UI compounds. "What if the parents are confused?" — the parent app onboarding ships with WhatsApp invite messages that work for parents who never used a school app before. "What if the report card format breaks?" — we configure the format during onboarding and you sign off on a sample before go-live.
How long does migration actually take
For a 500-student school: cleanup (6-12 hours over 2 days) + import (4-6 hours) + verification (3-4 hours) + branding setup (2-3 hours) + staff training session (90 minutes) = roughly 20-25 working hours of school-side effort over a 5-7 day window. WEBNIFY-side: the operations team is pair-working with you across this window. Total elapsed: 48-72 hours of clock time when working actively, fits inside the free first month with a comfortable buffer.
Final word: Excel was not wrong, just done
Excel is a remarkable tool — most schools that ran on it for a decade did so because nothing better was approachable. The 2026 reality is different. Cloud school ERPs are now flat-priced (~₹3 / student / month all-in), mobile-first, and onboardable in days. The migration is the hardest part, and it is hard for one week, after which it is over. Schools that finish the migration almost universally wonder why they waited.