Migrating from spreadsheets to a school SIS
A phased migration playbook from Excel-based school ops to a connected SIS — data import, training, parallel running, and go-live without losing audit history.
“We will move to proper software next year” is the most repeated sentence in school admin. Spreadsheets survive because migration feels risky: What if we lose history? What if staff revolt? What if fees go wrong mid-term?
Migration is risky when it is a big bang. It is manageable when it is sequenced — people first, academics next, money with guardrails, portals last.
Why schools postpone migration (and what it costs)
Registrars say they are “too busy this term.” Finance says “after audit.” Leadership waits for a cheaper quote. Meanwhile:
- Duplicate guardian records multiply every admissions cycle
- Fee disputes lack receipt proof parents trust
- Teachers maintain private mark books “just in case”
- Group WhatsApp becomes the shadow SIS (parent portal vs WhatsApp)
Postponement has a price measured in overtime, leakage, and reputational dents — rarely in licence fees alone.
Inventory what you actually have
Before any import, list sources of truth:
| Domain | Common spreadsheet tabs | Owner |
|---|---|---|
| Students & guardians | Master list, class lists | Registrar |
| Staff | HR list, timetable assignments | HR |
| Fees | Invoices, receipts, balances | Finance |
| Attendance | Monthly registers | Pastoral |
| Results | Grade books | Academics |
Identify which file is authoritative when two disagree. Migration exposes contradictions you have been living with — that is a feature, not a bug.
Choose cutover waves
Recommended order for most K-12 and international schools:
- People — students, guardians, staff, classes
- Academics — attendance, timetable, exams setup
- Finance — opening balances, new invoices only in SIS
- Communication — WhatsApp/email notices from SIS rows
- Portals — parent and student login after data stabilises
Our /migration page mirrors this sequencing for Edument OS imports. Skipping steps creates the worst outcome: portals go live with wrong balances.
Clean data beats clever mapping
Spend time on:
- Consistent student IDs (do not rely on name spelling)
- Guardian mobile with country code
- Class naming (
Year 7Avs7-A— pick one) - Fee head vocabulary aligned to new system
Run validation reports on import staging. Fix at source CSV, not with manual edits inside production.
Parallel running without double truth forever
Parallel running means both old sheet and new SIS for a defined window — usually one billing cycle or four weeks of attendance. Rules:
- New events happen only in SIS after cutover date (enrolments, payments, marks)
- Legacy sheet is read-only archive
- Weekly reconciliation meeting with finance and registrar
If parallel running exceeds six weeks, you do not have parallel running — you have two systems of record.
Compare Edument vs spreadsheets for honest trade-offs.
Training that respects busyness
Teachers need 30-minute sessions on their tasks: mark attendance, enter marks, not admin theory. Finance needs invoice and receipt drills. Registrars need admissions and guardian updates.
Record short screen captures for substitutes. Punitive training slides nobody reads.
Preserve audit history
Export legacy spreadsheets to read-only PDF or locked files stored with retention policy. Regulators may ask for 2019 fees even if 2026 runs in the SIS. Historical results may import as archived PDFs per student if granular marks migration is too costly.
Risk controls for fee cutover
- Import opening balances with signed totals
- First receipts in SIS numbered sequentially from a defined start
- No deletion permissions for casual staff
- Principal approves first bulk invoice run
Read fee collection without spreadsheets for operational detail.
When to delay migration
Delay if:
- Leadership has not assigned a single migration owner
- Fee policy is unsettled (you will encode chaos)
- Major ERP vendor change mid-term without backup registrar
Do not delay because the spreadsheet is comfortable. Delay until governance is ready.
After go-live: kill shadows
Shadow spreadsheets return unless leadership forbids them. Communicate: “If it is not in the SIS, it did not happen.” Exception queue goes to migration owner for two weeks, then closes.
Evaluate vendors with migration in mind
Choosing a school management system and international school SIS checklist include import support questions. Pricing and trial with demo data let you rehearse import before production.
Change management for reluctant staff
Name champions in each department — not only IT. Celebrate small wins publicly: “First week with all receipts in SIS.” Address saboteurs privately; if someone re-exports to Excel for personal control, that is a management issue, not a training gap.
Parents notice less chaos at fee counters before they praise software. Lead with registrar calm, not feature lists.
Sample week-by-week timeline
| Week | Focus | Success signal |
|---|---|---|
| 1 | Data inventory and owner assignment | One CSV template agreed per domain |
| 2 | Clean people data; dry-run import | Duplicate guardian count drops below 2% |
| 3 | Classes and timetable live | Teachers see correct rosters |
| 4 | Opening fee balances imported | Finance signs totals vs bank |
| 5 | Attendance only in SIS | No new paper registers |
| 6 | Portal invites to pilot parents | Login success rate above 70% |
| 7–8 | WhatsApp notices from invoices | Delivery failures have email fallback |
Adjust pace for your term calendar — never cut over fees the week before exams if you can avoid it.
Questions leadership should ask weekly
- Where is the parallel sheet still being edited?
- Which department has the most open import errors?
- What parent-facing process still references the old file?
- Do we have a rollback plan if opening balances are wrong?
Honest answers beat optimistic Gantt charts.
Common import pitfalls
- Dates as Excel serial numbers breaking DOB
- Leading zeros stripped from student IDs
- Duplicate guardians because “Ahmed Khan” appears twice
- Fee balances rounded to whole currency units
- Class names with trailing spaces breaking roster match
Run validation reports; fix CSV; re-import staging until clean. One dirty import poisons trust for a year.
How Edument OS fits the playbook
Edument OS trial tenants ship with demo students, fees, and attendance so you can rehearse workflows before touching production CSVs. Import paths follow the sequencing on /migration. Features map to modules in this guide; compare/spreadsheets documents trade-offs without pretending Excel disappears overnight.
Migration from spreadsheets is not a technology project. It is a discipline project software makes visible. Sequence it, reconcile weekly, and close the parallel window — your future registrar will thank you.
Summary
Successful migration inventories truth, sequences people → academics → finance → portals, runs a bounded parallel period, kills shadow sheets, and trains by role. Book the parallel-window end date in leadership calendars as immovable — extensions teach staff that the spreadsheet always wins. Import cleanliness and leadership enforcement matter more than vendor slide decks — but the right SIS makes enforcement possible because there is finally one place to enforce. Celebrate the day someone asks “where is the sheet?” and the answer is genuinely “nowhere.”
