Changing school management information system providers worries people for one reason: the fear of losing records mid-year. With a clear migration plan, that fear is manageable. The work splits into three parts: mapping the data, timing the move, and retraining the staff who use it.

Independent schools carry commercial responsibilities that many state schools do not: fee billing, catering accounts, extras and a parent body that expects a smooth, professional experience. When you weigh a school management information system for an independent setting, the finance and day-to-day operational modules deserve as much attention as the admin core.

Spreadsheets are where many multi-academy trusts start, and for a single form entry they can just about cope. Run several schools from them and the cracks show quickly. Versions multiply, formulas break, and no one is quite sure which file is current. For a trust accountable to governors, the Department for Education and parents, that is a real risk rather than a minor annoyance.

Keep a simple checklist through the whole project: data mapped, test import verified, go-live date agreed, old system retained, staff trained, first reports produced and checked. Assign an owner to each item so nothing slips.

Get the full picture at Helping Learning Thrive.

Start with licensing itself. Ask how it is calculated: per pupil, per module, per site, or a flat fee. Confirm what happens as pupil numbers change and how the price behaves at renewal. A figure that looks fine this year can move sharply once a discount lapses, so ask for the standard renewal price in writing, not only the introductory one.