Why the SY 2027-2028 Systems Decision Gets Made in October

Most school leaders treat the system questions as a summer problem. The current system strains during enrollment, someone says "we need to look at this," and the conversation picks up again after classes start. By then, it is a year late.

If your school is doing its school year 2027-2028 planning now, the date to work from is when enrollment for SY 2027-2028 opens. Anything that needs to be live for that enrollment, including a new school management system, has to be decided well before it. This post works backwards from that date.

Enrollment opens in May, so the decision closes in December

Enrollment season is the one crucial period that a school cannot move. Guardians arrive when the calendar says they will, and every record, fee and section the school creates in that window runs through whatever system is live on the day.

That makes May 2027 a fixed point. Everything else in a systems change has to fit in front of it: approval, contracting, configuration, migration, testing and training. Count those backwards and the decision lands in the last quarter of 2026.

What leadership is really deciding in October is not which system to buy. It is whether the school is willing to begin the work this year, while there is still time to do it properly. Edusuite’s implementation can range anywhere from 3-6 months depending on school size.

October to December is also when most private schools set next year's budget. If the system's decision is not in the school systems budget approved this quarter, the realistic options narrow to two: delay the change by a full year, or push an implementation into the months when the office is least able to absorb it.

That is why school year 2027-2028 planning belongs on the board or congregation agenda in the budget window, not on the registrar's to-do list in April.

What has to happen between signing and go-live

This is the part of school year 2027-2028 planning that is easiest to underestimate from the outside. Signing is the start of the work, not the end of it. Between signature and the first live enrollment, a school needs to:

• Configure the system to its own model: programmes, fee structures, discounts, grading rules, report card templates and sections.

• Migrate student, academic and financial records from the current system.

• Test with real data, so the registrar and finance office can confirm that grades, balances and records come out the way they should.

• Train the people who will use it every day.

• Run a parallel period, checking the old and new systems against each other.

Every step depends on people who also have a school to run: the registrar, the IT head, finance and, in a multi-unit school, a counterpart at every unit. 

Before signing, ask for a written implementation plan with named owners on both sides and dates tied to your academic calendar, from kick-off to go-live. Being able to lock in a migration window is what really solidifies the plan.

For a group with more than one campus or level, there is a further question: which unit goes first? A phased rollout, one unit or one level at a time, reduces risk but lengthens the school system implementation timeline. That trade-off is far easier to make in October, with the whole year in view, than in March with enrollment six weeks out.

Migration runs against your academic calendar, not your budget calendar

The budget calendar says when money is available. The academic calendar says when records are stable enough to move. They are rarely the same date. School year planning starts with the academic calendar and fits the budget around it, not the other way round.

Records are easiest to migrate at a definite boundary: a term has closed, grades are final and balances are settled. They are hardest to migrate mid-term, when grades are half-encoded and payments are still posting.

For school year 2026-2027, the natural boundaries are the end-of-term blocks. A school that decides in October can plan migration around those boundaries. A school that decides in February has already lost most of them.

Migration is also the step schools most often underestimate. Records built up over years carry workarounds: duplicate student entries, fee codes nobody remembers creating, grades kept in spreadsheets outside the system. 

Tools help. The Import Wizard in Edusuite is built for moving data out of legacy systems, but it does not remove the need for someone at the school to decide what is kept and what is archived. Plan time for those decisions, not only for the transfer itself.

Training the office before peak, not during

The worst time to learn a new system is the week you need it most. If the registrar's office and cashier first use it during May enrollment, every unfamiliar screen becomes a longer queue at the counter.

Training works best in a quieter stretch, with enough time for staff to practise on their own data. Build it into school year 2027-2028 planning from the start rather than scheduling it once the contract is signed. It also needs a second round. The first session lays the foundation. The second, a few weeks later, is where the real questions come out once the system is live.

This is the capacity argument that matters to leadership. A new system is meant to give the office back hours during peak, and it can only do that if the learning curve is behind the team before peak begins. A school that trains during enrollment pays for the change twice: once in the contract, and again in the queue.

It also shapes how the change is seen. Guardians experience a new system through the counter and the portal. A smooth first enrollment is what they remember. So is a rough one.

Working backwards from May 2027

Put together, a school year 2027-2028 planning timeline looks roughly like this. Dates marked for confirmation depend on your school's calendar and the scope of the change.

• October 2026. Registrar and IT head define requirements. Leadership sets the budget envelope.

• November 2026. Shortlist, demonstrations and reference conversations with peer institutions. Board or congregation review.

• December 2026. Decision and contract, inside the budget window. Configuration begins.

• January to February 2027. Configuration and a first migration pass, tested against real records. 

• March to April 2027. Final migration at the end-of-year boundary, training and a parallel run. 

• May 2027. Go-live for SY 2027-2028 enrollment.

Your own school system implementation timeline will differ by size, number of units and the state of your current records. For a multi-campus group, school year 2027-2028 planning means running this sequence per unit and agreeing the order in which units go live. For schools where decisions pass through a board or congregation, make sure to add the time that review actually takes. 

Two things stand out. There is little slack in it, and almost all of the work happens before a single guardian logs in. That is why the decision belongs in this quarter's school systems budget rather than next year's.

If you would like to map your SY 2027-2028 planning against your own school, with your units, your calendar and your current system, talk to our team. You can also read stories from our school partners.

The line for the board is simple: if the new system needs to be live for May 2027 enrollment, the decision has to be in this quarter's budget, because waiting until summer means waiting until 2028.