Custom ESIS integration development
Appfront builds custom integrations with ESIS, the pupil administration and pupil monitoring system from Rovict for primary education. We connect ESIS to your own application, portal or dashboard, so that pupil data, results, groups and the OSO transfer file stay reliably in sync. 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 pupil administration and pupil monitoring system (LAS/LVS) from Rovict, used by over 1,500 primary schools. In ESIS a school enrols pupils, handles the exchange with the government for funding purposes, and tracks each pupil's development through test results, records and group plans.
A custom integration means, in practice: making pupil data, groups and staff from ESIS available to your own environment, bringing together results and test data for management reporting, supporting the OSO transfer file during the move to secondary education, and exchanging test results via the UWLR standard. This prevents duplicate data entry and gives you one reliable source for your pupil data.
Appfront aligns with 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 educational processes, so the integration stays maintainable and continues to run reliably, even during peak moments such as the start of the new school year.
One source for pupil data
Pupil data, groups and staff remain authoritative in ESIS and flow automatically into your own application or portal. No duplicate entry and no loose exports, just one current and reliable source for the entire school.
Results and progress
You bring test results and progress from the pupil monitoring system together in your own dashboard or board-level reporting. Teachers, coordinators and the board see development at the right level, without manually re-keying data.
OSO and UWLR in one flow
We handle the OSO transfer file and the UWLR exchange of pupil data and results in a continuous flow. Transfers to secondary education and exchanges with assessment environments run according to 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 educational processes, data flows and the ESIS exchange you need, through to going live and ongoing management, every step is designed to give your team an integration they can understand and trust.
We map out which pupil data, results or files you want to exchange, which systems ESIS needs to connect with, which education standards apply and how often the data needs to synchronise.
We design the integration architecture, choose the right exchange method and authentication, and define an error-handling and data-minimisation strategy.
Implementation with automated tests, structured logging and monitoring on a secure test set. You see working builds along the way.
Controlled go-live with data validation and safeguards, followed by ongoing management and further development of the integration.
What an ESIS integration delivers in practice
Every ESIS integration is set up specifically for your educational processes, data flows and adjacent systems. Below are the features we most often deliver for schools, boards and collaborative partnerships that use ESIS as the source for their pupil data.
Pupil data synchronisation
Pupil data from ESIS, such as personal details, enrolment and group allocation, flows automatically into your own application or portal. Changes in ESIS are passed on at the agreed frequency, so your environment always keeps pace with the current administration.
Results and pupil monitoring system
You bring test results and progress from the pupil monitoring system together in your own dashboard or board-level reporting. This lets you see development per pupil, group or school at the right level, without data having to be transferred by hand.
OSO transfer file
Support for the OSO transfer file when pupils move from primary to secondary education. We help compile and make the files available in line with OSO agreements, with data minimisation so that only relevant and necessary fields are transferred.
UWLR exchange
Exchange of pupil data and results via the UWLR standard between ESIS and, for example, an assessment environment or teaching method. Pupils, groups, staff and results are exchanged according to the agreements, so duplicate entry and typing errors disappear.
Groups and staff
Group allocations and staff details from ESIS are passed on to timetables, learning environments or parent portals. Changes to groups or staff flow through automatically, so the right teacher stays linked to the right group.
Interfaces & custom API
A reliable integration layer between ESIS and your own systems, with structured logging, monitoring and clear error handling. We connect to the available interfaces and education standards rather than building fragile workarounds.
Who we build ESIS integrations for
An ESIS integration looks different for each education organisation. We regularly see a number of recurring situations, and for each we have a proven approach that pays close attention to the right data flows, education standards and privacy.
Primary schools
Primary schools that want to display pupil data and results from ESIS in their own environment, parent portal or pupil 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 pupil data and results from multiple schools for management reporting and steering. We connect ESIS to your analytics environment or custom software, so you gain whole-board insight without manual work.
Partnerships
SEN partnerships (samenwerkingsverbanden passend onderwijs) that support the OSO transfer file and 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 suppliers who want their product to connect to ESIS, for example a testing environment, curriculum method or parent portal. We build the UWLR or interface integration as a manageable middleware layer 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 precise 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 automatically back into your pupil tracking system, see our page on a UWLR integration.
Why choose 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 must not only work technically, but also add practical value to the work of teachers, administrative staff and management.
For every integration, we write clear documentation and make sure your own team, or any future supplier, can understand and manage it. No black box, just 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. This keeps communication short, prevents misunderstandings and speeds up decisions when choices need to be made during development.
See also our broader services around API integrations, middleware, custom software and web app development, or browse all the integrations we build.
- Experience with education data and integrations around pupil 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 held in secure vaults
- Structured error handling and retry mechanisms
- Comprehensive logging and monitoring from day one
- Clear documentation your team can read and manage
- A fixed point of contact, no account managers passed around
- Ongoing maintenance and proactive further development
- A way of working aligned with 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 document the data flows and processing so that your record of processing activities is complete and you can demonstrate compliance 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 vulnerability disclosure policy.
- GDPR-compliant data processing and data minimisation
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable data flows
- Automatic retries 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 receive 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 your purpose, you exchange pupil data such as personal details, enrolment and group allocation, alongside results and assessment data from the pupil tracking system, group and staff data, and transfer records. For the transition to secondary education you use the OSO transfer file, and for assessment results the UWLR standard. We set up the data flows according to data minimisation, so that only the fields needed for your process are exchanged.
Yes. We work with the education standards commonly used in primary education, such as UWLR for exchanging pupil data and results, and OSO for the transfer file to secondary education. Where ESIS offers interfaces or other exchange options, we build on those rather than fragile workarounds. This keeps the integration maintainable and aligned with sector agreements.
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 connected, the desired synchronisation frequency and the amount of custom business logic required. Ongoing management, monitoring and support also contribute to the total investment. We always provide a clear quote following a no-obligation analysis of your situation and requirements.
Yes. Pupil data is personal data of minors and requires particular care. We build to the OWASP ASVS, with encrypted connections, secrets held in secure vaults, scoped permissions and data minimisation, so that only necessary fields are exchanged. We align with the Privacy Covenant for Education and the Edu-K agreements, and document the data flows so that your record of processing activities remains complete and you can demonstrate GDPR compliance.
Yes. Appfront regularly takes over existing integrations, even those originally set up by another party. We review the data flows, error handling and logging, document the current setup and propose improvements. From that point on, we can handle adjustments, extensions and monitoring, so the integration stays reliable as your education processes grow.
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 pupil data, results or records you want to make available from ESIS and which systems it needs to connect with. We are happy to think along about data flows, education standards and privacy. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.