Switching Your School ERP Mid-Session: A 2026–27 Migration Playbook
You don't have to wait for next April. Here is how to move schools to a new platform mid-session without losing data, disrupting fee collection, or confusing parents — step by step.
The Myth That You Must Wait for April
The most common reason schools stay on software they have outgrown is a belief that you can only switch at the start of a new academic year. It is not true. Schools migrate mid-session all the time — the key is sequencing the cutover so that fee collection, attendance, and parent communication never go dark. This playbook is the exact order to do it in.
A mid-session switch actually has one advantage over an April migration: there is no rollover chaos competing for your office's attention. You are moving a known, stable dataset rather than one that is changing under you.
Phase 1: Prepare Before You Touch Anything
Export Everything from the Old System
Before signing with anyone, confirm you can get your data out of the current platform. You need students, parents, fee ledgers (paid and outstanding), staff records, and transport assignments — ideally as CSV or Excel. If your current vendor makes this hard, that friction is itself a reason to leave, and a lesson for choosing the next one. Our data ownership guide explains what a clean export should contain.
Reconcile the Fee Ledger First
The single highest-risk data in any migration is money owed. Before importing, reconcile the old system's outstanding balances against your bank records so the opening balances in the new platform are correct to the rupee. A wrong opening balance becomes a parent dispute in week one. Get this right and the rest of the migration is low-stakes.
Map Your Structure
Document your class-section structure, fee heads, and concession rules. The new platform will import cleanly only if it knows how your school is organised. This is also the moment to clean up — drop dead fee heads and merge duplicate parent records before they migrate.
Phase 2: Import and Parallel-Run
Import Master Data
Load students, parents, and staff into the new system. Verify counts match the old system exactly — same number of students per class, same parent links. A good onboarding team does this import for you and hands back a reconciliation report. Confirm attendance and fees show the right students before going further.
Run Both Systems in Parallel for One Cycle
Do not flip the switch overnight. For one to two weeks, run daily attendance and a small fee batch in the new system while the old one is still live as a fallback. This catches mapping errors — a missing section, a mis-assigned transport fee — while the stakes are low. Once a full fee cycle reconciles cleanly in the new platform, you are ready to cut over.
Train the Office in the Real Tasks
Training fails when it is a generic tour. It works when staff complete their actual daily jobs — marking attendance, collecting a fee, sending a notice — in the new system, with their own data, supervised. Two focused sessions usually suffice. Lean on the platform's AI assistant for the long tail of "how do I…" questions so staff are not blocked waiting for support.
Phase 3: Cut Over and Communicate
Announce the Change to Parents Clearly
Parents do not care which ERP you run — they care that fee links keep working and notices keep arriving. Send one clear WhatsApp announcement: from this date, reminders and receipts come from the new system, here is what changes for you (usually nothing). Routing this through WhatsApp-first communication means it reaches parents in an app they already check.
Decommission the Old System on Your Terms
Keep the old system in read-only access for one term as an archive, then export a final backup and close the account. Do not delete anything until you have a verified full export stored safely. Cancel the old contract only after the new platform has run a complete, reconciled fee cycle on its own.
Migration Risk Checklist
| Risk | Mitigation |
|---|---|
| Wrong fee opening balances | Reconcile against bank before import; verify per-student |
| Missing students or sections | Match counts old vs new before parallel run |
| Parents confused by the change | Single clear WhatsApp announcement at cutover |
| Staff revert to old habits | Task-based training on real data, not a generic tour |
| Data trapped in old system | Confirm full export works before signing anything |
Frequently Asked Questions
Will parents have to re-register or download anything?
No, if the new platform is WhatsApp-first. Parents keep receiving messages on the same number; nothing changes on their side.
How long does a mid-session migration take end to end?
Typically two to four weeks including the parallel-run period. The parallel run is what makes it safe, so do not skip it to save a few days.
What if we collect fees through the old system this month?
That is fine — reconcile those payments into the new system's opening balances before cutover. The parallel-run phase is designed exactly for this overlap.
The Practical Next Step
If you have already decided your current platform is holding you back, do not wait nine months for April. Confirm you can export your data, reconcile your fee ledger, and start a parallel run. For choosing where to move, use our buying framework to score the shortlist.