Data movement and reporting
CSV and Excel import and export
Bulk import for students, guardians, staff, classes, and subjects, and Excel or CSV export across roster, fees, grades, payroll, timetable, and reports.
Available today
Every school migration begins and ends in a spreadsheet, and pretending otherwise is how migrations go wrong. Schoolyi treats bulk import as a first-class workflow rather than a support ticket: students, guardians, teachers, staff, users, classes, and subjects all have templated Excel import, with validation before anything is written.
Export is equally deliberate. Roster, fee defaulters and refunds, grades, timetable, payroll statutory formats, and generated reports all export to Excel or CSV. That is what makes the data yours in practice rather than in principle — a claim about data portability means very little if the export is a support request.
For an evaluating school this is worth testing early with your own file. Import validation is where you discover that your existing data has three spellings of the same guardian, and it is much better to discover that during evaluation than during go-live week.
How it works
- Templated Excel import per entity, validated before write, so a malformed file is rejected with the rows identified rather than half-applied.
- Guardian and student records are matched during import, which is where duplicates are caught.
- Exports are available from the relevant module rather than centralised, so the export carries the filters you were already looking at.
- Payroll statutory exports follow Indian PF, TDS, and professional tax formats.
Who configures it
Nothing to configure. Import and export are available to roles with the relevant permission.
What it does not do
Worth reading before a procurement decision rather than after.
- This is file movement, not a connector. There is no scheduled sync to or from an external system, and no API key model for a third party to pull data on a timer.
- Payroll statutory exports produce the statutory file formats. They do not post entries into Tally, QuickBooks, or Xero.
- Import validation catches malformed data, not wrong data. A guardian entered under two spellings in your source file is two guardians unless you deduplicate before import.
Related
CSV and Excel import and export: common questions
Including the questions where the answer is no.
Can we get our data out if we leave?+
Yes, through the same exports you use day to day — roster, fees, grades, payroll, timetable, and reports, in Excel or CSV. We would rather you never want to, but a platform that makes leaving difficult is telling you something about its confidence.
How much data cleaning should we expect before import?+
More than you think, and it is the highest-return work in the project. Duplicate students, guardians recorded under different spellings, and unclear payer-of-record are the three that cause the most trouble later. Run a trial import during evaluation to find out which of these you have.
Is there an API instead?+
There is an authenticated application API that the product itself uses, documented in the OpenAPI specification, but there is no third-party API key model for external systems to integrate against. If your requirement is programmatic integration by another vendor, say so during evaluation rather than assuming.
Everything else
Other integrations, and the ones we do not have
The hub lists what is available and names what is not.
Bring your stack to a walkthrough
Tell us what you already run and which handoffs cost your team time. That is a more useful conversation than a compatibility list.
Already using Schoolyi? Sign in