Versioned templates
Defined columns and examples for students, guardians, staff, classes, opening fee balances, and approved setup records.
Import and export
SchoolSync data tools are planned to help schools bring existing spreadsheets in, correct problems before committing, and produce permissioned exports with a clear history.
A useful import separates valid rows, warnings, duplicates, and errors before anything is written.
Planned capabilities
Defined columns and examples for students, guardians, staff, classes, opening fee balances, and approved setup records.
Type, size, malware, headers, values, dates, references, tenant scope, and spreadsheet formula risks.
Valid rows, warnings, duplicates, errors, actions, and a downloadable correction report before commit.
Idempotent processing, import ID, actor, time, counts, policies for partial success, and correction path.
Profiles, attendance, fees, payments, dues, expenses, salary, finance, and audit data limited by role and scope.
Background generation, visible progress, protected download, expiry, failure recovery, and export history.
Import workflow
Use the current template for the exact data type and academic context.
Check the file and every row without mutating school data.
Correct errors, review duplicates, and choose the approved partial-import policy.
Apply valid records under one import ID with a complete outcome report.
First migration
Admission numbers, employee codes, class names, receipt series, and duplicate definitions.
How much past attendance, payment, expense, salary, and academic history should be migrated.
Missing guardian links, inconsistent dates, merged cells, duplicate phones, and free-text categories.
Who verifies, approves, corrects, and signs off each imported or exported dataset.
Its columns and inconsistencies will tell us more than a generic import checklist.