The questions schools ask before committing
Straight answers on scope, curricula, migration and what happens to your data. If yours is not here, ask us directly.
The platform
What exactly does Sync School 360 cover?
The student side of a school: admissions and enrolment, the student information record, attendance, gradebook and assessment, timetabling, inclusion and SEN, clinic and student health, transport and bus attendance, parent communication, behaviour and wellbeing, and reporting across all of it.
Do we have to take every module?
No. Modules are selected individually and most schools start with the student record plus one or two others. You can add modules later without a migration each time.
How is this different from CampusTrack?
CampusTrack holds the employee record — staff attendance, leave, payroll readiness and compliance. Sync School 360 holds the student record. They are separate products for separate jobs; schools running both get one ecosystem, and schools needing only one are not obliged to take the other.
Does it work for nurseries and universities, or only schools?
The student record is the same idea at every stage, but the assessment and reporting models differ considerably. The platform is configured per institution rather than assuming a single school shape.
Curriculum and assessment
Which curricula are supported?
British, CBSE and Indian, IB across the continuum, and American curriculum schools. Each has its own assessment model configured properly rather than mapped onto a single percentage field.
We run two curricula on one campus. Is that a problem?
No. More than one curriculum can run on a single campus, with reporting configured separately for each while students remain in one directory.
Can we keep our own grading scale?
Yes. Grading scales, assessment points and report cycles are configuration. Schools on the same curriculum still report differently, and being forced onto a template is one of the most common complaints about student systems.
Moving across
How long does migration take?
It depends far more on the condition of your existing data than on the size of your school. A clean export from a modern system moves quickly; fifteen years of spreadsheets with inconsistent spellings takes longer. We tell you which situation you are in early rather than at the end.
Will we lose our historic data?
No. Historic records come across with the current ones, because a student record that starts from the migration date is not much use for tracking progress or answering a records request.
Can we run in parallel with our current system?
Yes, where a clean cutover would be risky. It is more work during the overlap, but for some modules it is the sensible choice.
When in the school year should we switch?
Term boundaries for attendance, ahead of an intake season for admissions, and before a reporting cycle for assessment. The rollout order is agreed against your calendar rather than ours.
Commercial and data
How is it priced?
Per student in bands, plus the modules you select, plus a one-off implementation cost. Staff accounts and parent access are not charged per seat.
Who owns the data?
You do. Export in open formats is available at any time, including if you decide to leave. A student system that makes leaving difficult is holding your records hostage.
Where is our data stored?
In UAE-based infrastructure. Student records are not replicated to other regions.
Still have a question?
Ask it before a demo rather than during one. You will get a more useful answer.