Moving a school group off spreadsheets without losing a term
Sequence the migration so fee collection lands first. That is where parents notice, where money is at stake, and where trust is either won or lost in the first month.
Most school groups do not run on one system. They run on a registrar’s admission register, an accountant’s fee tracker, a set of marks sheets maintained by class teachers, and the institutional memory of two or three people who know where the real numbers live. Replacing all of that at once is what turns a migration into a lost term.
The order matters more than the speed. What follows is the sequence that keeps the office running while the ground moves underneath it.
Why a term boundary is the only safe cutover
A term boundary is the one moment when the three heaviest processes are all quiet at once. Admissions for the coming term have closed, so the student list is stable. Fees for the term have been billed but the next cycle has not opened. Marks for the previous term are published and the new term’s assessments have not started.
Cut over mid-term and you inherit a half-finished fee cycle in one system and a half-finished mark sheet in another. Reconciling those by hand costs more staff hours than the migration saves in its first year.
Pick the cutover date before you pick the modules. Every decision that follows, including how much historical data you carry, is governed by how many weeks sit between now and that date.
The five phases, in order
Each phase has to finish before the next one starts, because each one depends on the record the previous phase established.
{{ p.d }}
{{ p.doNow }}
{{ p.notYet }}
Three spreadsheets to never migrate as-is
Importing these directly carries the workaround into the new system, where it becomes permanent and much harder to see.
It exists because the old system could not express a rule. Find the rule, configure it, and let the new system generate the demand. Importing the tracker’s totals hides whatever the rule was.
Sibling discounts, staff wards and principal-approved waivers usually live in a column of notes. Each one needs a category and an approver before it moves, or every future audit asks the same unanswerable question.
The weighting logic sits in cell formulas that nobody has reviewed in years. Migrate the marks, not the arithmetic, and rebuild the weighting as an assessment scheme you can point at.
A ten-week window
Ten weeks before the cutover is enough for a group of three to six institutions, provided the audit starts on day one.
| Week | What happens |
|---|---|
| {{ w.k }} | {{ w.v }} |
What breaks if you skip deduplication
Deduplication feels like the phase you can defer. It is the one that costs most to defer, because every later record attaches itself to whichever duplicate happened to be open at the time.
Resolve duplicates while the total is still counted in hundreds. After a term of transactions, every merge has to reconcile money as well as identity, and each one needs an approval trail of its own.
Bring us your term dates and your fee policy.
A consultant maps this sequence onto your own calendar, with your registrar and accounts team in the room.