Many schools run well on Excel and WhatsApp for years. Spreadsheets are flexible, everyone knows them, and a parents' group answers questions in minutes. The trouble starts with growth: the fee sheet has five versions, nobody is sure which attendance file is current, a message about a bus delay is buried under forty replies, and a staff member leaves with the only copy of a list. This article is a practical plan for moving to one platform without stopping the school.
Admit what the old way does well
Be honest about why the current tools survived. Excel gives you freedom to build any report in an afternoon. WhatsApp reaches parents where they already are, with no new app to install. A good migration keeps those strengths: reports should be easy to get out of the new system, and parents should still receive messages quickly. If you ignore this, people drift back to their old files "just for now".
Step 1: List what lives where
Before you move anything, make a one-page map of your data and who owns each piece.
- Student records: names, national or residence ID, grade, class, parent contacts.
- Staff records: names, roles, subjects, contracts.
- Money: fee plans, instalments, discounts, payments received, receipts issued.
- Daily records: attendance, behaviour notes, health notes.
- Conversations: parent groups, staff groups, announcements.
Next to each item write who edits it, how often, and which file or chat holds the latest version. Where the answer is "it depends", you have found your first data-quality problem.
Step 2: Clean the data before you import it
Importing messy data into a clean system gives you a messy system. Spend a few days on the basics:
- One row per student and one row per parent, with the relationship between them recorded once.
- Consistent names and spellings, with Arabic and English kept in separate columns when you need both.
- Mobile numbers in one format, including the country code.
- Grades and classes named the same way everywhere.
- Fee plans described as amounts, due dates and discounts, not as notes in a free-text column.
Ask the vendor for their import template and fill it in rather than inventing your own layout. A good vendor reviews the file with you before the real import, which catches duplicates and missing fields while they are still cheap to fix.
Step 3: Migrate in phases
Moving everything on one weekend is the most common way to fail. A safer order:
- Core records first. Students, parents, staff, classes and subjects. This is the foundation the other modules use.
- Attendance next. It is daily, simple and visible to parents, so it builds habit quickly. Run it in parallel with paper for one or two weeks.
- Fees and invoices. Load fee plans and the current balance for each student, agree on a cut-over date and stop updating the old sheet from that day.
- Parent communication. Move announcements and notifications into the system while keeping the existing group for informal chat if you wish.
- Everything else. Timetable, transport, canteen, clinic, e-learning: add them one by one when the first three are stable.
At each phase decide in advance what "done" means, for example "all classes took attendance in the system for ten consecutive school days".
Step 4: Bring people along
Systems fail because of people, not software. Plan for it.
- Teachers need a short, practical session on the two tasks they do every day. Attendance from a phone and entering grades cover most of their use.
- The accountant should be involved from the start, because fee data is the hardest to migrate and the most sensitive.
- Parents need one clear message: what changes, where to download the app, and from which date. Send it through the channels they already read, then follow up in the app.
- A named owner inside the school, usually a deputy principal or the head of administration, decides questions quickly and keeps the plan moving.
Step 5: Switch off the old ways deliberately
Decide a date after which the spreadsheet becomes read-only and the old attendance register is retired. Keep a final archive copy of the old files in a secure location, with access limited to the people who need it. Without a switch-off date, two systems live side by side and the school pays twice.
Common mistakes
- Importing before cleaning the data.
- Starting with the module that is hardest to change, usually finance, instead of the one that builds habit.
- Training everyone once, on day one, and never again. Plan a second short session after two weeks.
- Treating parents as an afterthought. If they do not see value in the first month, they ignore the app.
How Classti supports the move
Classti provides import templates for students and staff, and its team reviews the data with you before go-live. Parents and teachers use dedicated apps that stay in sync with the school dashboard. To see how the two ways of working compare, read Classti vs Excel and WhatsApp, or look at attendance and parent communication. When you are ready, book a demo and bring a sample of your spreadsheet.