Eight suites that run the whole school

Teacher first: 10+ AI tools with CBSE and ICSE content
Explore Assist →
From the first doubt to the chapter exam, one connected path
For Class 3 to 12, CBSE and ICSE, with JEE and NEET for Class 11 and 12. Every chapter in four steps.
Where would you like to sign in?
School login
For staff and admins · app.schoolcanvas.com
Student login
For students · student.schoolcanvas.com
Popular with schools
Popular with students and parents
One database for every campus: running a multi-school group
When every campus keeps its own spreadsheets, the group office spends its week reconciling numbers. Here is how one shared database changes the work, and what to set up first.
On this page
A school group usually grows one campus at a time. The first branch has its own office, its own fee registers and its own way of naming classes. The second copies some of that and invents the rest. By the third campus, the group office is collecting spreadsheets every Monday, fixing totals that don't match and asking each principal for the same figures in a slightly different format.
A multi-school ERP replaces that with one database that every campus works in. Each school keeps running its own day, but the records sit in one place, in one format, so the group sees the whole picture without anyone retyping it.
Why separate records cause errors
Take Green Valley Public School, a fictional group of 1,284 students across three campuses: Anna Nagar, Velachery and Tambaram. Before moving to one system, each campus kept its own student list and fee file. A few problems showed up every term:
- The same child, typed three times. A student's details were entered at admission, again in the fee file and again for the bus list. One spelling change at the front office never reached the other two.
- Totals that never matched. The group office added up three fee reports with different column orders and different fee heads. Half a day went on finding why the numbers were off.
- Slow answers to simple questions. "How many seats are left in Class 6 across the group?" meant three phone calls and an email.
- No common view of enquiries. A parent who enquired at Velachery and then visited Tambaram was two separate leads, followed up twice.
None of this is anyone's fault. It is what happens when information lives in several places. One central database, with no repeated data entry, removes most of it.
What one database means in practice
With Schoolcanvas, every campus works in the same system. A student is created once, at admission, and that one record carries through attendance, fees, transport, exams and certificates. The Multi-School view in the Student Management suite lets the group office move between campuses or see them together.
| Area | Each campus does | The group office sees |
|---|---|---|
| Admissions | Records enquiries and follow-ups, runs entrance tests, converts the lead into a student without retyping | Enquiries from every branch in one list, class-wise seat availability, conversion analysis |
| Fees | Collects at the counter, kiosk, POS or through the parent app | One control panel for every collection centre; collected, overdue and upcoming fees |
| Students | Marks attendance in the teacher app, issues certificates and TCs | Strength, absences and admissions against withdrawals, by campus or for the group |
| Transport | Runs its own routes and pickup points | Transport that works across branches, with fees linked to routes and stops |
| Staff | Records biometric attendance and leave | Staff numbers, attendance and payroll across the group |
Group-level reports, without the Monday spreadsheet
Schoolcanvas has 500+ ready reports, including a wide range of multi-school reports. For a group, the useful ones are usually the comparisons: fee collection by campus this month, attendance trends by campus, admissions against last year, or the sections that are over or under strength.
When a trustee asks a question the ready reports don't answer, the custom report builder and dashboard builder let the group office build its own view, without waiting for a developer. A dashboard for the chairman can show the three campuses side by side, while each principal's dashboard shows only their own school.
Because the figures come from the same records the campuses work in every day, there is nothing to reconcile. The fee total on the group dashboard is the sum of the receipts the counters issued, not a number someone typed into a summary sheet.
Fees under more than one trust
Many groups run campuses under different trusts or societies, each with its own bank account. The Finance suite handles this: fees under multiple trusts can be collected in one click, and gateway payments settle straight into the school's account. The group office sees one collection picture, while the accounts stay separate where they need to be. End-to-end Tally integration keeps the books for each entity in step.
Who sees what: role and permission based access
One database does not mean everyone sees everything. Access is set by role and permission. A typical set-up looks like this:
- Chairman and trustees: group dashboards and reports across all campuses.
- Group office (accounts, HR, academics): their own area across all campuses, for example fees for the accounts head or payroll for HR.
- Principal: everything for their own campus.
- Campus office staff: only the modules they work in, such as admissions or the fee counter.
- Teachers: their own classes, attendance, homework and marks entry.
- Parents: their own child's information in the parent app.
Logins can use biometric or access-code verification, and the data is hosted in a tier-IV data centre in India with four-copy backup. Whatever the set-up, the data belongs to the school group, not to us.
Bringing an existing group onto one system
Moving several campuses at once sounds like a large project. In practice it goes better in a clear order:
- Agree common masters first. Class and section names, fee heads, staff categories and academic year settings. This is the step that makes group reports possible later, so it is worth an hour with every principal in the room.
- Send each campus's data as it is. Excel files or exports from another ERP are fine. Data migration is free, and our team maps each campus's columns to the shared format.
- Go live campus by campus, or all together. When the data is ready, go-live takes 7 days. Some groups start with one campus and add the others once staff are comfortable.
- Train by role. Fee counter staff, class teachers and the group office each need a different hour of training. It can be onsite or online, and a dedicated account manager stays with the group afterwards.
- Set up the group dashboard last. Once a month of real data is in, decide which comparisons the trustees want to see every week.
When the group grows again
The real test comes with the next campus. With one database and agreed masters, a new branch starts with the group's class structure, fee heads and report formats already in place. It can still have its own fee amounts, timetable and certificate designs, since certificates and report cards are fully customisable, but its numbers appear in the group reports from the first day.
Our hostel and multi-school modules (see also ERP for school groups) include franchise and multi-school management for exactly this, so the group office can run many schools remotely from the web or the mobile app.
If you run more than one campus and would like to see how your own group would look in one system, book a free demo and bring your trickiest group report question with you.
Common questions.
Can each campus keep its own fee structure?
Yes. Campuses share common fee heads so group reports add up, but each campus can have its own amounts, concessions, instalments and late fines. Fees under different trusts can also be collected in one click.
Will a principal see other campuses' data?
Only if you allow it. Access is set by role and permission, so a principal usually sees their own campus, while the chairman and group office see all of them.
Can we move all campuses at once?
Yes, or one at a time. Data migration from Excel or another ERP is free, and go-live takes 7 days once the data is ready.
Who owns the group's data?
The school group does. It is hosted in a tier-IV data centre in India with role-based access and four-copy backup.
Where this lives in the product.
Talk to us about your school.
A 45-minute walkthrough with a school software specialist, tailored to your board, size and processes. We’ll call you within 4 working hours to fix a time.
Your free demo can cover
- Your own data, formats and processes
- The modules you need, from admissions to fees
- The apps for parents, teachers and staff
- Assist, the AI LMS for your teachers
- A setup plan and a quote for your school
- Call back in 4 working hours
- Free data migration
- 1-month free trial
Book my free demo
Takes 30 seconds. No commitment.
