Custom ESIS integration development
Appfront builds custom integrations with ESIS, Rovict's student administration and student monitoring system for primary education. We connect ESIS to your own application, portal or dashboard, so that student data, results, classes and the OSO transfer file synchronise reliably. You keep control of your education data, demonstrably comply with the GDPR and no longer have to enter anything twice.
What is an ESIS integration?
ESIS is the student administration and student monitoring system (SIS/SMS) from Rovict, used by more than 1,500 primary schools. In ESIS, a school enrols students, handles the data exchange with the government for funding, and tracks each student's development through test results, files and group plans.
In practice, a custom integration means: making student data, classes and staff from ESIS available to your own environment, bringing together results and test data for management reporting, supporting the OSO transfer file when students move on to secondary education, and exchanging test results via the UWLR standard. This prevents double entry and gives you one reliable source for your student data.
Appfront connects to the interfaces and national education standards that ESIS supports and builds to the OWASP ASVS security standard. We tailor the data flows, synchronisation frequency and error handling to your actual education process, so the integration remains maintainable and keeps running reliably even at peak moments such as the annual rollover.
One source for student data
Student data, classes and staff remain authoritative in ESIS and flow automatically to your own application or portal. No double entry and no separate exports, just one current and reliable source for the whole school.
Results and progress
You combine test results and progress from the student monitoring system in your own dashboard or management report. Teachers, coordinators and the board see development at the right level, without retyping data by hand.
OSO and UWLR in one flow
We process the OSO transfer file and the UWLR exchange of student data and results in a single continuous flow. Handover to secondary education and exchange with test environments follow the agreed education standards.
Our development process for ESIS integrations
We work to a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your education process, data flows and the desired ESIS exchange through to go-live and ongoing maintenance, every step is aimed at an integration your own team can understand and trust.
We map out which student data, results or files you want to exchange, which systems ESIS needs to connect with, which education standards are involved and how often the data needs to synchronise.
We design the integration architecture, choose the right exchange method and authentication, and draw up an error-handling and data-minimisation strategy.
Implementation with automated tests, structured logging and monitoring on a safe test set. You'll see working builds along the way.
A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development of the integration.
What an ESIS integration delivers in practice
Every ESIS integration is set up specifically for your educational process, data flows and adjacent systems. Below are the features we deliver most often for schools, school boards and partnerships that use ESIS as the source for their student data.
Student data synchronisation
Student data from ESIS, such as contact details, enrolment and class allocation, flows automatically to your own application or portal. Changes in ESIS are passed on at the agreed frequency, so your environment always stays in step with the current records.
Results & student monitoring system
You bring together test results and progress from the student monitoring system in your own dashboard or board-level report. This gives you a view of progress per student, class or school at the right level, without data having to be copied over by hand.
OSO transfer file
Support for the OSO transfer file (overstapdossier) when students move from primary to secondary education. We help compile the files and make them available in line with the OSO agreements, using data minimisation so that only relevant and necessary fields are transferred.
UWLR exchange
Exchange of student data and results via the UWLR standard between ESIS and, for example, an assessment platform or teaching method. Students, classes, staff and results are exchanged according to the agreements, so double entry and typing errors disappear.
Classes & staff
You pass class allocations and staff data from ESIS on to timetables, learning environments or parent portals. Changes to classes or staff are carried through automatically, so the right teacher stays linked to the right class.
Interfaces & custom API
A reliable integration layer between ESIS and your own systems, with structured logging, monitoring and clear error handling. We connect to available interfaces and education standards instead of building fragile workarounds.
Who we build ESIS integrations for
An ESIS integration works out differently for each educational organisation. We see a number of situations come up often, and for each of them we have a proven approach that pays attention to the right data flows, education standards and privacy.
Primary schools
Primary schools that want to display student data and results from ESIS in their own environment, parent portal or student dashboard, without double entry. We make the data available securely and up to date. See also our smart API integrations.
School boards
School boards that want to bring together the student data and results of multiple schools for board-level reporting and steering. We connect ESIS to your analytics environment or custom software, so you get insight across all your schools without manual work.
Partnerships
Inclusive education partnerships (samenwerkingsverbanden passend onderwijs) that support the OSO transfer file and the handover between schools. We help set up the data flows around registration, transfer and placement securely and in line with education standards, with data minimisation as the starting point.
Education service providers
Education service providers and edtech vendors that want their product connected to ESIS, such as an assessment platform, teaching method or parent portal. We build the UWLR or interface integration as manageable middleware between ESIS and your application.
Technology we use
We build ESIS integrations on the available interfaces and national education standards, combined with the backend stack that suits you. The exact choice depends on the exchange method and your own systems, so your team can manage or further develop the integration.
If you want test results to flow back into the student monitoring system automatically, see our page on a UWLR integration.
Why Appfront for your ESIS integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes. An integration has to be technically sound, but it also has to add practical value to the work of teachers, administrative staff and school boards.
For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.
You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.
Also take a look at our broader services around API integrations, middleware, custom software and web app development, or see all the integrations we build.
- Experience with education data and integrations around student administration
- Familiar with UWLR, OSO and national education standards
- Data minimisation and privacy by design as the starting point
- Secure by default, with scoped permissions and secrets kept in secure vaults
- Structured error handling and retry mechanisms
- Extensive logging and monitoring from day one
- Clear documentation that your team can read and maintain
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
- An approach tailored to your existing IT landscape
Security and privacy in ESIS integrations
An ESIS integration works with pupil data, which is personal data, largely of minors, and calls for extra care. Appfront builds in line with the OWASP ASVS: secrets in secure vaults, scoped permissions, encrypted connections and data minimisation, so that only the fields necessary for your process are exchanged.
We align with the Privacy Covenant for Education and the Edu-K agreements that apply in the sector, and we document data flows and processing so that your record of processing activities is complete and you can demonstrably comply with the GDPR. Audit logs make every exchange traceable, so you can always account for which data was shared and when.
You can read more about our approach to security in our information security policy and coordinated vulnerability disclosure policy.
- GDPR-compliant data processing and minimisation
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable data flows
- Automatic retry and dead-letter queues
- Monitoring and alerting for anomalies
- Alignment with the Privacy Covenant for Education and Edu-K
- Documentation for your record of processing activities
Frequently asked questions about ESIS integrations
Answers to the questions we get asked most often about ESIS integrations.
An ESIS integration is a technical connection between ESIS — Rovict's pupil administration and pupil monitoring system — and another system, such as a custom education application, parent portal, dashboard, or an assessment or learning-method environment. Through the available interfaces and national education standards, pupil data, groups, staff and results are exchanged reliably. An integration can be simple, such as periodically synchronising pupil data, or extensive, with results, OSO transfer files and UWLR exchange in a continuous flow.
Depending on the purpose, you exchange student data such as name and address details, enrolment and class allocation, alongside results and test data from the student tracking system, class and staff data, and transfer files. For the transition to secondary education you use the OSO transfer file, and for test results the UWLR standard. We set up the data flows in line with data minimisation, so that only the fields your process needs are exchanged.
Yes. We work with the education standards that are common in primary education, such as UWLR for exchanging student data and results, and OSO for the transfer file to secondary education. Where ESIS offers interfaces or other available ways to exchange data, we build on those rather than creating fragile workarounds. This keeps the integration maintainable and in line with the agreements in the sector.
A simple integration, for example periodically synchronising pupil data and groups to a portal, can be up and running within a few weeks. More extensive scenarios with results, OSO transfer files, UWLR exchange and integration with multiple systems generally take longer. After an intake meeting in which we map out your situation and data flows, we give you a realistic estimate.
The cost depends on the number of data flows, the systems to be integrated, the required synchronisation frequency and the amount of custom business logic. Ongoing maintenance, monitoring and support also factor into the total investment. We always provide a clear quote after a no-obligation analysis of your situation and requirements.
Yes. Student data is personal data relating to minors and calls for extra care. We build in line with OWASP ASVS, with encrypted connections, secrets in secure vaults, scoped permissions and data minimisation, so that only the necessary fields are exchanged. We align with the Privacy Covenant for Education and the Edu-K agreements and document the data flows, so your record of processing activities stays complete and you can demonstrably comply with the GDPR.
Yes. Appfront regularly takes over the management of existing integrations, even if they were originally set up by another party. We review the data flows, error handling and logging, document the current setup and draw up improvement proposals. From that point on we can handle changes, extensions and monitoring, so the integration keeps growing reliably with your education process.
An ESIS integration suits primary schools, school boards, partnerships and education service providers who use ESIS and want to open up the data to their own applications, portals or analytics dashboards. Typical situations include showing pupil data in your own environment, combining results for management reporting, supporting OSO transfers or exchanging test results via UWLR. We always first check with you whether an integration is the right solution.
Ready to build your ESIS integration?
Tell us which student data, results or records you want to unlock from ESIS and which systems it needs to connect to. We're happy to think along on the data flows, education standards and privacy. A no-obligation first conversation gives you a clear picture of the possibilities within half an hour.