School ERP Data Migration: Moving From Excel or Your Old System Without Losing Data
The decision is usually made months before anyone acts on it. The school has compared vendors, seen the demos, agreed the price — and then nothing happens for a term, because someone asks the question nobody has a confident answer to: what happens to fourteen years of our data?
It is a fair question, and most vendor answers are unhelpfully breezy. "We'll handle the migration" is not an answer. It is a promise with no shape to it, and schools are right to be suspicious of it.
So here is the shape. This post covers what genuinely moves from a spreadsheet or an older system into a school ERP, what does not move and should not, how to prepare your files so the import does not fail, when in the year to do it, and who does the work. It is written for the person who will actually be holding the files — usually the office administrator, sometimes the principal, occasionally a computer teacher who has been volunteered.
The Honest Starting Point: You Are Not Moving Everything
The most common migration mistake is treating it as an archival project. Schools try to bring across every record they have ever held, and the migration collapses under its own weight somewhere around the 2017 attendance registers.
A school ERP is an operating system for the current session. It is not a document archive. The data that needs to be inside it is the data that something in the system will act on — raise an invoice against, mark attendance for, put on a report card, send a message to.
That distinction cuts the job down enormously. In practice, the list looks like this.
Moves, and must be accurate:
- Current students: every child enrolled right now, with class and section
- Parent contact details, specifically the mobile number that will receive messages
- Staff: teaching and non-teaching, with designation
- Your fee structure: heads, amounts, classes they apply to, frequency
- Outstanding fee balances as on the date you switch
- Current session's class and section structure, and subjects per class
Usually moves, with less urgency:
- Last session's results, if you want report card history in one place
- Student documents — birth certificates, Aadhaar copies, transfer certificates — which are usually uploaded gradually rather than in a single batch
- Transport routes and stop assignments, if you run buses
Does not move, and should not:
- Attendance registers from previous sessions. Nothing in the system acts on them. Keep the files.
- Old receipts from a closed, reconciled financial year. Your audited books are the record of those, not your ERP.
- Alumni from before your current records are reliable
- Spreadsheets whose purpose nobody in the room can explain, which every school has more of than it admits
Write that list down for your own school before you speak to any vendor, because it converts an open-ended fear into a finite task. In most schools of 500 to 1,500 students, the "must be accurate" column is a few thousand rows — not fourteen years of anything.
What Actually Happens in a Bulk Import
Mechanically, migration into a modern school ERP is a CSV import. You download a template whose columns match the system's own form, fill one row per record, upload it, and the system creates the records in the background.
In Campus 24x7 specifically, so you can judge the shape of it: students come in through Bulk Admission, with a downloadable CSV template, files up to 5 MB, processed in the background while you keep working. Student IDs and passwords are assigned automatically, the parent ID follows the child's, and you download a credentials file afterwards to share logins with families. Staff come in through a separate bulk upload of up to 100 teachers per file, which checks the file before it creates anyone — it shows you which rows will be created, which will be skipped, what it corrected automatically and what needs your attention, and lets you download that report, fix the file and try again.
That validation step is the one to ask every vendor about. The difference between a migration that goes smoothly and one that becomes a three-week cleanup is whether the system tells you what is wrong with your file before it writes 900 student records, or after.
A 5 MB CSV is far larger than most schools need. A 1,200-student file with twenty columns is well under a megabyte. The limit is not usually the constraint; the state of the file is.
Preparing Your Excel Files: Where Imports Actually Fail
Almost every failed school data migration fails for the same six reasons, and all of them are visible in the spreadsheet before you upload anything.
1. Dates in more than one format. This is the single biggest cause. Indian school spreadsheets accumulate 12/03/2014, 12-03-2014, 12 March 2014 and 2014-03-12 in the same column, because different people typed them in different years. Worse, Excel silently reinterprets some of them when the file is opened on a machine with different regional settings. Fix the whole column to one format before export — DD-MM-YYYY or YYYY-MM-DD, whichever your template asks for — and verify by sorting the column and looking at the top and bottom.
2. Phone numbers that are not phone numbers. Excel treats a mobile number as a number, which means it strips leading zeros and, for longer strings, converts to scientific notation. A column that reads 9.07692E+09 is a column of destroyed data. Format the column as Text before you type or paste anything into it. Also decide now whether you are storing +91 prefixes, and make it consistent — because this column is what your WhatsApp and SMS messages will go to, and a wrong number here means a parent silently stops receiving everything.
3. Merged cells and header rows that are not headers. Office spreadsheets are built to be printed and read, so they carry school names across merged cells in row 1, a logo, a blank row, and the real headers in row 4. An import expects row 1 to be headers and every row after it to be data. Strip the decoration.
4. Names split inconsistently. Some rows have "Full Name", some have first and last in separate columns, some have the father's name appended. Decide the structure the template wants and conform to it. This matters more than it sounds, because student names end up on report cards and transfer certificates.
5. Duplicate students. Every school has them — a child entered twice with a slightly different spelling, a student who left and rejoined, siblings whose records got crossed. Sort by name and scan before you import. Duplicates created at migration are much harder to remove later than to catch now, because by then each copy has attendance and invoices hanging off it.
6. Class and section naming that does not match. Your sheet says "VIII-A", the system expects "8" and "A" as separate values, and your transport sheet says "Class 8 Sec A". Pick one convention across every file.
None of this is difficult work. It is just work, and it belongs to the school rather than the vendor, because only your office knows which of two similar records is the real one.
Fee Balances: The Part Everyone Underestimates
Students and staff are the easy half. Fees are where migrations actually go wrong, because you are not moving a list — you are moving a financial position on a specific date.
The principle that keeps this clean: pick a cut-over date, reconcile to it, and bring across balances rather than history.
Concretely:
- Choose the date you will go live, ideally at the start of a billing cycle.
- Close your old books to that date. Every payment received up to it is recorded in the old system or sheet.
- For each student, calculate one number: what they owe as on that date.
- Set up your fee structure in the new system — heads, amounts, classes, frequency, billing and due days.
- Enter the outstanding balance per student as the opening position.
- From the cut-over date, every new invoice and receipt happens only in the new system.
What you do not do is try to replay three years of receipts into the new system so the history looks complete. It will not reconcile, it will take weeks, and it will leave you with two sets of books that disagree — which is a genuine audit problem. Your old receipts are already evidenced by your old receipt books and your audited accounts. Keep them. The ERP's job starts at the cut-over date.
The one rule nobody should break: do not run both systems in parallel for fees. Two people collecting fees in two systems for "just a couple of weeks" produces a reconciliation problem that outlasts the migration by a term. Attendance can overlap harmlessly for a week. Money cannot.
Timing: When in the Session to Switch
The best time to migrate is between sessions — after results are out and before the new session's admissions and fee cycle begin. For most Indian schools that means roughly February to April, with the configuration work happening in December and January. Everything aligns: a new fee cycle, a new class structure, a clean cut-over date, and an office that is not simultaneously running exams.
The second-best time is the start of a term or quarter, which still gives you a clean billing boundary even if the class structure carries over.
The worst time is mid-cycle, three weeks into a quarter, with half the fees collected against invoices that exist only in the old system. If you must do this — and sometimes a school must, because the old contract has expired — then migrate students and staff first, run attendance and communication on the new system, and leave fees on the old system until the cycle closes. Splitting the migration by module is a legitimate strategy. Splitting a single fee cycle across two systems is not.
One more timing note: do not schedule go-live for a week when your senior administrator is on leave. The migration itself is a few days of work, but the fortnight after it is when the questions arrive, and they need someone who knows both the old data and the new system.
Who Does What
A realistic division of labour, because "we'll handle it" obscures the fact that about half this work can only be done by the school.
The school owns:
- Deciding what moves (that list in section one)
- Cleaning the files — only your office knows which duplicate is real
- Confirming the fee structure is correct, head by head
- Signing off the outstanding balances before go-live
- Telling parents their logins are coming, and from which number
The vendor owns:
- The templates, and telling you exactly what each column expects
- Running the import and reporting what succeeded, failed or was auto-corrected
- Configuring the fee structure, classes, sections and subjects
- Training your staff on the screens they will actually use
- Being available in the first fee cycle, which is when real problems surface
Ask before you sign: who specifically from the vendor is on the migration, how many working days it takes, whether a validation report is produced before records are created, and what happens if the import is wrong — can it be reversed, or does someone delete 900 records by hand?
A Realistic Timeline
For a single-campus school of 500 to 1,500 students with data in Excel, assuming the school does its part promptly:
| Stage | Who | Typical duration |
|---|---|---|
| Decide scope, pick cut-over date | School + vendor | 1–2 days |
| Clean student, parent and staff files | School | 3–7 working days |
| Configure classes, sections, subjects, fee heads | Vendor | 2–3 days |
| Import students and staff, review validation report | Both | 1 day |
| Fix flagged rows, re-import | School | 1–2 days |
| Enter opening fee balances, verify totals | Both | 2–3 days |
| Train office staff and teachers | Vendor | 2 days |
| Go live, parallel-run attendance only | Both | 1 week |
Call it three to four weeks end to end, of which the vendor's actual working time is a handful of days. The file cleaning is the long pole, and it is the part schools consistently underestimate — which is why the honest version of "how long does migration take" is "about a week of our work and two to three weeks of yours."
If your data is in an older ERP rather than Excel, the shape is the same but the first step changes: you export from the old system to CSV, and you should do that while your contract is still active. Schools that let a contract lapse before exporting have discovered that read-only access is not always included in the wind-down. Export first, verify the export opens and is complete, then cancel.
Verifying the Migration Before You Trust It
Do not declare a migration finished because the import said "success". Run these checks, which take under an hour and catch almost everything:
- Counts. Total students in the system versus your sheet. Then per class. A class that is short by four students is the cheapest problem you will ever find.
- The edges. Open the first and last student alphabetically, and one from each class. Check name spelling, date of birth, class, section, parent mobile.
- Phone numbers. Scan the mobile column for anything that is not ten digits. Send one real test message to a staff member's own number before anything goes to parents.
- Fee totals. Sum the outstanding balances in the new system and compare against your reconciled figure from the cut-over date. These must match to the rupee. If they do not, stop and find out why before you raise a single invoice.
- A full dry run on one class. Mark attendance, raise an invoice, record a payment, generate a receipt. End to end on thirty students, before you do it on nine hundred.
- Logins. Hand credentials to two or three friendly parents first and confirm they can sign in and see the right child. Then roll out to everyone.
That last point matters for a reason that is not technical. The migration your parents experience is the day they receive a login and either it works or it does not. Everything above is invisible to them; that one moment is not.
What to Ask a Vendor, in Plain Words
Six questions, worth more than any feature list during a demo:
- Will you show me the import template today, with the exact columns?
- Does your system validate the file and show me errors before creating records?
- What is the per-file limit, and how many files will my school need?
- How do opening fee balances get in — and can I see that screen now?
- Can we import students and staff first, and move fees at the next cycle?
- If our data ends up wrong, what is the correction path?
A vendor who can answer all six on the call, with screens rather than reassurance, is telling you they have done this before.
The Short Version
Migration is less frightening than it looks, and more work than vendors imply. The fear — "we will lose fourteen years of data" — is misplaced, because you should not be moving fourteen years of data. The real work is narrower and more mundane: clean the current session's files properly, reconcile fees to a single cut-over date, verify counts and totals before you trust anything, and do it between sessions if you possibly can.
Schools that treat it as a data-entry project done by whoever is free tend to have a difficult term. Schools that treat it as a short, owned project with a named person, a cut-over date and a verification checklist tend to find the whole thing anticlimactic — which is exactly what a migration should be.
If you are weighing the switch itself rather than the mechanics of it, school ERP vs Excel covers the cost comparison, and the implementation checklist covers everything that happens after the data is in. If you are still choosing between vendors, the guide to choosing school ERP software is worth reading before each demo.
We set demos up with your own data rather than samples, which is the fastest way to find out what your files will actually do in an import — and the first two months cost ₹0, so your migration happens before you pay anything. If you want to talk the sequence through for your school, book a demo and bring one class's spreadsheet.
Product details above — CSV template, 5 MB bulk admission files, up to 100 teachers per staff upload with a pre-import validation report, and automatically assigned student and parent logins — describe Campus 24x7 as at the date of this post. Timelines are typical ranges for a single-campus school and will vary with the state of your data. Plan prices and module limits are current at the date of this post; see the pricing page for live figures.



