Two common approaches
Two patterns are planned. An institution can keep its SIS for records and results and use Acadlytic for CRM, communication, engagement and analytics, or adopt Acadlytic’s planned student management and migrate away from the SIS over time. The integration pattern differs for each.
Planned data flows
| Data | Direction when SIS is the record | Frequency |
|---|---|---|
| New students from admissions | Acadlytic → SIS | On enrolment |
| Student profiles & status | SIS → Acadlytic | Near real time or scheduled |
| Programme & section enrolment | SIS → Acadlytic | Scheduled |
| Results | SIS → Acadlytic | On publication |
| Contact detail updates | Either, with agreed ownership | Near real time |
Planned integration safeguards
- Clear ownership of each field to prevent overwrite conflicts
- Matching rules and identifiers agreed up front
- Error queues with alerts rather than silent failures
- Reconciliation reports during rollout
Frequently asked questions
Do we have to replace our SIS?
No. Keeping an existing SIS as the system of record and integrating it with Acadlytic is one planned pattern; migrating over time is another. We will help you choose.
How are students matched between systems?
By an agreed unique identifier, typically the institution’s student ID, with fallback matching rules reviewed during setup.