
Quick answer
The best time to switch school ERP is between academic years: the summer break for September-start schools and the March to April gap for April-start schools. Decide about two terms before go-live, load next year's fees before the first instalment is invoiced, carry re-enrolment deposits across, and keep last year's history reachable on day one.
The best time to switch school ERP is usually the gap between one academic year and the next, with the decision made two terms earlier. That timing lets a school close its books, promote students and set next year's fees in the old system once, then open the new year in the new one. A mid-year switch is possible, but it costs more effort and carries more risk.
The right date for your school depends on four calendars that rarely line up: the academic year, the fee cycle, re-enrolment and inspections. This guide explains how each one affects timing, compares the main switching windows, and gives a working back-plan from go-live. UAE rules quoted here come from KHDA and ADEK publications linked at the end, and Indian schools on an April session can apply the same logic to their own calendar.
When is the best time to switch school ERP?
For most schools, the best time to switch is at the academic year boundary:
- September-start schools (most British, American, IB and many UAE curriculum schools): go live in the summer break, before term one fee invoices are issued.
- April-start schools (many Indian curriculum schools, in India and the UAE): go live in the March to April gap, before the new session's first fees and timetables.
The reason is simple. At the year boundary, the school has a clean set of opening balances, a fresh timetable, new class lists and a new fee schedule. All of these have to be created anyway, so creating them in the new system avoids doing the work twice.
What are the signs it is time to switch school ERP?
Timing only matters once the decision is made. These signs usually mean the current system is costing more than a switch would:
- Spreadsheets run the real work. Fee schedules, timetables or inclusion registers are kept outside the system because it cannot hold them.
- The same data is typed twice. Admissions details are re-entered for finance, or marks are copied into report card templates.
- Reports need one person. Leaders cannot run their own attendance or progress reports and wait for an export.
- Regulatory changes need workarounds. New fee rules, instalment plans or notice requirements cannot be configured.
- Parents complain about billing. Incorrect invoices, missing receipts or unclear balances recur every term.
- Support is slow or the product has stopped changing. Requests sit for weeks and new features have not arrived in years.
- The contract is ending. A renewal date is a natural point to review, as long as you start early enough.
If three or more apply, start planning now so you can switch at the next year boundary rather than in a rush.
Why does the academic year matter for an ERP switch?
A school ERP carries a year's worth of state: attendance, marks, timetables, fee balances, instalments and staff payroll. Switching mid-year means moving all of that state while it is still changing.
Year-end is different. Attendance and marks for the year are final. Report cards have been issued. Students are promoted to the next grade. Fee balances are known. The school can move closed history as a one-time import and start live work fresh.
Use the academic year boundary unless something forces an earlier date, such as an expiring contract, a failing system or a new campus opening mid-year.
How do fee cycles and re-enrolment affect the switch date?
Fees are the area where a badly timed switch hurts most, because families notice billing errors immediately.
Dubai. Under the KHDA Registration and Refund Policy, tuition is collected in three terms aligned to school breaks, with term one capped at 40% of annual tuition and terms two and three at 30% each, or as ten equal monthly instalments. Re-registration deposits for September schools can be collected only after the end of the spring break, with a deadline no earlier than 1 May, and are deducted from next year's term one fees. For April-start schools, deposits can be collected only after the winter break, with a deadline no earlier than 1 February.
Abu Dhabi. Under the ADEK School Fees Policy, schools must offer at least three equal tuition instalments, may collect the first instalment up to one month before the year starts, and may collect registration fees (including re-registration) up to four months before the year starts, deducted from final tuition.
What this means for timing:
- Re-enrolment deposits collected in the old system must carry across, so they are deducted correctly from term one in the new system. Plan this hand-over explicitly.
- The new fee schedule must be loaded and tested in the new system before the first instalment is invoiced, which can be a month before term in Abu Dhabi.
- Avoid going live in the middle of a deposit window or a term invoicing run.
Our re-enrolment process guide explains the deposit rules in detail.

Should a school switch ERP during inspection season?
In Dubai, KHDA has said quality assurance visits resume in the first term of 2026-27, with no more than 24 hours' notice. A visit can arrive while a new system is still bedding in.
That is not a reason to delay a switch indefinitely, but it does set two conditions:
- Keep history reachable. Last year's attendance, assessment and inclusion records must be viewable on day one, either imported into the new system or available read-only in the old one.
- Train leaders on reports first. The senior team should be able to run progress and attendance reports in the new system before term starts.
See our guide to KHDA quality assurance visits for what inspectors are focusing on this year.
Which switching windows work, and which are risky?
| Window | Effort | Risk | Best for |
|---|---|---|---|
| Academic year boundary (summer for September schools, March to April for April schools) | Lowest: one clean start | Lowest | Most schools |
| Winter break (mid-year) | Medium: balances and marks for term one must move | Medium | Schools with an urgent reason, a strong data team and clean records |
| Spring break | Medium to high: overlaps re-enrolment deposits and final term planning | Medium to high | Rarely recommended for September schools |
| During term | Highest: live attendance, marks and fees moving at once | Highest | Only when the old system has failed |
A phased approach can also work: switch admissions for next year's intake first, while current students stay in the old system until year end. Admissions for the following year often opens months before the year starts, so this gives staff practice before the main go-live.
How long before go-live should a school decide?
Work backwards from go-live. A typical back-plan for a September-start school going live in August looks like this:
| Months before go-live | Step |
|---|---|
| 8 to 9 | Agree scope, budget and success measures; shortlist vendors |
| 6 to 7 | Demos on your own data; reference calls; contract signed |
| 5 | Project team named; data audit of student, family, fee and staff records |
| 3 to 4 | System configured: grades, sections, fee heads, instalments, templates, roles |
| 2 to 3 | Test migration of master data; admissions for next year's intake goes live |
| 1 to 2 | Final migration of closed-year history and opening balances; staff training |
| Go-live | New year opens in the new system; old system kept read-only |
| First term | Weekly issue review; second training round; switch off old system when signed off |
Exact durations depend on the number of campuses, the quality of existing data and how many integrations are needed. Ask every vendor for a dated plan for your school, not a generic estimate. Our school ERP implementation guide covers each phase in more depth.
What should be migrated when switching school ERP?
Not everything needs to move. A practical split:
- Move: current students and families, staff, next year's classes and timetable, fee schedules, opening balances, deposits paid, current-year and prior-year marks needed for reports and transcripts, health and support records, active documents.
- Archive: older attendance and marks, closed fee history, old message logs. Keep them exportable and searchable in a read-only archive.
- Rebuild: templates, report cards, permissions and workflows, which are better set up fresh than copied.
The school ERP migration guide has a full data checklist.
How does Hudace SchoolOS support a switch at year end?
Hudace SchoolOS includes an academic calendar with a year launch console, promotion rules and bulk CSV import, so a school can open the new year with promoted students, new sections and next year's fee heads in place, then bring closed history across as a one-time import. Its digital adoption tools, such as guided product tours and in-app announcements, help staff learn the new system in the first weeks. Pricing depends on modules, students and campuses; our school ERP cost guide lists the factors to compare.
If you are planning a switch for the next academic year, you can book a SchoolOS demo and ask for a dated plan built around your fee and re-enrolment calendar.
Frequently asked questions
Can a school switch ERP in the middle of the year?
Yes, but it takes more effort and carries more risk, because live attendance, marks and fee balances must move while they are still changing. The winter break is the least disruptive mid-year window, if records are clean.
How far ahead should a school plan an ERP switch?
Start around eight to nine months before go-live for a single campus, and earlier for groups. That leaves time for demos on your own data, a data audit, configuration, test migrations and staff training.
What happens to re-enrolment deposits during an ERP switch?
Deposits collected in the old system must carry across so they are deducted from next year's first tuition invoice. In Dubai, KHDA requires re-registration deposits to be deducted from tuition for the term of enrolment.
Should we switch ERP before a KHDA inspection?
KHDA visits in 2026-27 come with no more than 24 hours notice, so a visit can arrive during a transition. Make sure last year's records are viewable on day one and leaders can run key reports before term starts.
Do we need to migrate all historical data?
No. Move current students, families, staff, fee schedules, opening balances and the marks needed for reports and transcripts. Older history can sit in a searchable read-only archive.
Can we switch admissions before the rest of the system?
Yes. Many schools run admissions for next year's intake in the new system first, while current students stay in the old one until year end. It gives staff practice before the main go-live.
How does Hudace SchoolOS help with a year-end switch?
SchoolOS includes an academic calendar with a year launch console, promotion rules and bulk CSV import, so a school can open the new year with promoted students, sections and fee heads in place, and bring closed history across once.