Most advice on changing school ERP focuses on the new system: plan the migration, train staff, run parallel, go live. That is the easy half. Your incoming vendor is motivated to help and will do much of the work.
The hard half happens earlier, with a vendor who has no incentive to make it smooth. This page is about that part.
The order that matters
Schools commonly do this in the wrong sequence: choose a new vendor, sign, give the incumbent notice, then request data.
By that point you have lost your leverage. You have already committed, the incumbent knows it, and your data request goes to the bottom of their queue.
Do it the other way round.
Step 1: Extract before you announce anything
Before selecting a new vendor, before mentioning that you are evaluating alternatives, request a complete data export from your current system.
You do not need a reason, and if asked, “annual backup for our own records” is entirely true — it is good practice regardless of whether you ever switch. Any school should hold its own copy of its own records.
Request, specifically:
- Student master — including inactive students and alumni, not just currently enrolled
- Fee ledgers — full payment history, receipt numbers, concessions, outstanding balances, refunds
- Attendance history — for every year you intend to retain
- Marks and results — all assessments and terms, all retained years
- Staff records and payroll history
- Documents — certificates, photographs, uploaded files
- Fee structure configuration — heads, slabs, transport distance slabs, concession rules
Ask for structured formats — CSV, Excel or database dump. A PDF export is a picture of your data, not your data.
Step 2: Verify the export before doing anything else
An export you have not opened is not an export. Check:
- Row counts. Does the student file contain the number of students you actually have, including alumni? Compare against a figure you trust independently.
- A hard case. Pick a student who changed sections mid-year, took a concession, or paid in unusual instalments. Is that history intact and legible?
- Date ranges. Does attendance genuinely go back as far as you asked, or does it quietly stop two years ago?
- Financial totals. Do fee ledger totals reconcile against your accounts? A mismatch found now is a question for a cooperative vendor; found later it is your problem alone.
- Encoding. Open a record with a name in your regional script. Names rendered as question marks or boxes indicate an encoding problem that will corrupt every such record on import.
If anything is missing, request it now — while your relationship is normal and you are still a paying customer with a renewal they want.
Step 3: Only now, evaluate new vendors
With a verified export in hand, your position changes entirely. You know exactly what data you have, you can hand real sample files to prospective vendors and ask them to demonstrate import, and you are no longer dependent on the incumbent’s goodwill.
Ask every candidate to import your actual export — not a clean sample they prepared. How they handle your real, messy data is the most informative thing you will learn during evaluation.
Step 4: Time it against your academic calendar
Timing determines difficulty more than any technical factor.
Best window: after the academic session closes and before the next begins. The fee cycle has completed, results are published, and next year’s sections are not yet allocated. Records are at their most stable.
Workable: immediately after a term’s fee collection closes, giving a full quiet term before the next cycle.
Avoid: during fee collection, during board examination submissions, and during admission season. If a system problem coincides with any of these, the cost is not inconvenience — it is money uncollected and statutory deadlines missed.
Step 5: Run parallel, and budget for it
Run both systems for at least one full fee cycle. Collect fees in the new system and reconcile against the old one until totals match on real transactions.
This means paying two vendors for a period. Budget for it explicitly — it is the line schools most often forget, and it sits outside the new vendor’s quote entirely. Ask your outgoing vendor early what a short extension costs, because that conversation is much easier before you give notice.
Step 6: Give notice, and take one final export
When you do give notice, take a final full export on your last day of access, and verify it the same way as the first.
Data continued accumulating after your original extraction — a term of fees, attendance and results. Once access ends, retrieving anything overlooked becomes a request to a company you no longer pay.
Store that final export somewhere durable and separate. You may need it years later for an alumni transfer certificate, an audit or a legal query, long after the relationship has ended.
What to ask your next vendor before you sign
Everything above is a lesson in exit costs. Apply it forward, and ask any prospective vendor — us included:
- Can we export our complete data, in structured format, on demand, without a fee?
- Is that right in the contract, or is it goodwill?
- What is the format, and can we see a sample export from a real account now?
- If we leave, how long do we retain access to extract final records?
A vendor who answers these plainly is telling you they expect to keep you by being worth keeping. A vendor who becomes vague is describing your next migration.
We answer all four in writing, and we would encourage you to require the same from anyone else you are considering — including whoever you choose instead of us.
- Book a demo: Request a demo
- Portal login: https://in1.edunodex.in/