7min read
Most school leaders who switch their MIS don’t plan to do it the way they end up doing it. They plan it carefully and without realising it, the timeline compresses. A contract takes longer to negotiate. Data migration gets deprioritised. Staff training gets pushed to the first week of term. And what should have been a clean September launch becomes a stressful September recovery.
This guide exists to prevent that.
Here is exactly what a well-run MIS switch looks like, and how far back the decision needs to be made to make it work.
Working backwards from September
September 1st is the fixed point. Everything else works backwards from it. If you want your staff walking into the new academic year on a new system — confident, trained, with parents already connected. Here is the timeline that makes that possible.
| When | What’s happening | Status |
| January – March | Budget planning. Headteachers and bursars define spend for the coming academic year. MIS frustrations surface in leadership discussions. | Awareness |
| April – May | Budgets signed off. Active vendor evaluation begins. Demos, references, pricing conversations. | Decision time ✓ |
| May – June | Contract signed. Customer Success team begins data migration and platform configuration in the background. | Implementation begins |
| July | Staff training. Platform fully configured. Parent activation links prepared. | Training & setup |
| August | Soft launch. Parent app activation sent out. Final testing before term starts. | Go live |
| September | New academic year begins on the new system. Every module live, every parent connected. | Day one ✓ |
The honest answer If you haven’t made your decision by the end of May, a clean September launch becomes very difficult. Not impossible but the margin for error disappears, and something always slips.
Why April and May are the real decision window
Schools that sign in April have roughly 18 weeks before the first day of the new academic year. That sounds like a lot. In practice, it breaks down like this: two to three weeks to finalise and sign a contract, two to four weeks for data migration and platform configuration, two weeks for staff training and testing, two weeks for parent app activation and soft launch, and a buffer, which you will need. That is 12 to 15 weeks of active work, with 18 weeks available. The buffer is real, but it is not large.
Schools that delay the decision to June or July are compressing 12 weeks of work into 8 or fewer. Something has to give and it is usually either staff training (rushed), parent onboarding (skipped), or data migration (incomplete). Any one of those failures makes September harder than it needed to be.
The decision to switch doesn’t need to be fully researched by April. It needs to be made. Evaluation should happen in March. April is when you commit.
What the switching process actually involves
The reason MIS switches feel daunting is that schools imagine them as a big bang. One day on the old system, next day on a new one, everything broken in between. That is not how a well-run migration works. Here is what each phase actually looks like when done properly.
- Data migration
Your existing MIS holds student records, attendance history, parent contacts, timetables, and financial data. The first task is extracting that data cleanly from your old system and importing it into the new one. With Schooly, this is handled by your dedicated Customer Manager. Your admin team doesn’t touch a spreadsheet. The old system stays live throughout, so there is no gap in operation. Most migrations are complete within two to three weeks, depending on the volume and condition of the source data.
- Platform configuration
While data is being migrated, the platform itself is being configured for your school. This means setting up your year groups, class structures, term dates, report card templates, and communication preferences. By the end of this stage, you should have a fully configured platform populated with your school’s data, ready for staff to log into.
- Staff training
Staff training is where many schools over-invest time and under-invest preparation. The goal is not to make every teacher an expert on the system. It is to make them independently capable of the tasks they will do daily: taking attendance, viewing their timetable, sending a message to a parent, entering grades. For Schooly, that takes between 30 and 90 minutes per staff member. Admin staff, who use more of the system, typically need a half-day. We recommend scheduling training in July, when teaching staff have more mental bandwidth and the school is quieter.
- Parent app activation
Parent onboarding is the step most schools leave too late. The instinct is to launch the parent app on the first day of term, but that means your staff are simultaneously managing new students, new timetables, and hundreds of parents trying to activate an app they’ve never seen before. The better approach is to send activation links in late August, before term begins. Parents activate over the summer at their own pace. By September 1st, most are already using the app. Schools that follow this pattern typically reach 85–95% parent adoption before the first day back.
- Go LIVE
With the platform configured, staff trained, and parents activated, the new academic year begins on the new system. There is no cutover drama. It is simply the first morning where everything runs on Schooly. Attendance is taken digitally. Parents receive real-time notifications. The admin team has a single dashboard. The old system is switched off in the first week, once everyone is settled.
How soon is soon enough?
If you are reading this in April, you are on time. The decision should be made this month.
If you are reading this in May, you are in the last viable window. Commit quickly! The implementation timeline is tight but achievable with a responsive vendor.
If you are reading this in June or later, a September launch is still possible with Schooly’s fast implementation model, but it requires an immediate start and close coordination with your Customer Manager. You will have less room for error, and parent activation will need to be prioritised from day one.
Schooly in practice Schools switching to Schooly from legacy MIS platforms are typically fully live (including parent app adoption) within one week of the new academic year starting. The average time from contract signing to go-live is four weeks – that’s 30 days.
The switching process is not as complex as it feels from the outside. The complexity comes from doing it too late, with the wrong partner, or without a clear plan. If you would like to walk through what a September cutover would look like for your school specifically. How long your migration would take, what training would look like, when to send parent activation. We are happy to map it out with you. No pressure, just a clear picture of what is possible.
